Skip to content

Agency: clarify vehicle endpoint requirements#465

Merged
schnuerle merged 1 commit intoopenmobilityfoundation:devfrom
Retzoh:patch-2
Jun 11, 2020
Merged

Agency: clarify vehicle endpoint requirements#465
schnuerle merged 1 commit intoopenmobilityfoundation:devfrom
Retzoh:patch-2

Conversation

@Retzoh
Copy link
Copy Markdown
Contributor

@Retzoh Retzoh commented Mar 6, 2020

MDS Pull Request

Explain pull request

Some fields from the /vehicle endpoint cannot be provided because the provider did not provide them at registration (year, mfgr, model) or because no event has been pushed for the vehicle yet (status, prev_event, updated).

Is this a breaking change

A breaking change would require consumers or implementors of the API to modify their code for it to continue to function (ex: renaming of a required field or the change in data type of an existing field). A non-breaking change would allow existing code to continue to function (ex: addition of an optional field or the creation of a new optional endpoint).

  • No, not breaking

Impacted Spec

Which spec(s) will this pull request impact?

  • agency

@Retzoh Retzoh requested a review from a team March 6, 2020 16:53
@Retzoh Retzoh requested a review from a team as a code owner March 6, 2020 16:53
@sarob sarob added this to the Future milestone Mar 8, 2020
@sarob sarob added Agency Specific to the Agency API enhancement New feature or request labels Mar 8, 2020
@jfh01 jfh01 modified the milestones: Future, 1.0.0 Apr 9, 2020
@schnuerle schnuerle merged commit 8b64a54 into openmobilityfoundation:dev Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Agency Specific to the Agency API enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants