-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDS-Agency Stops Specification #430
MDS-Agency Stops Specification #430
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to add GET /stops
to read multiple stops at a time. I suggest a response body that looks like { version: ..., stops: Stop[] }
.
Why not have a single definition for stop payloads referenced by the agency and provider specs to make sure:
|
@Retzoh I'd be happy to move these changes over to the branch currently focused on the Provider changes, and merge the data definitions (though it probably won't get done by the City Services meeting today). |
@avatarneil , let us ask this question during the city-services call today since docked is on the agenda |
See discussion on Provider Stops PR #427: #427 (comment) |
Closing in favor of #427 which consolidates both the agency & provider changes needed |
Explain pull request
This PR is a work in progress to reflect changes from #427 in MDS Agency .
Is this a breaking change
Impacted Spec
agency
Additional context
Add any other context or screenshots about the feature request here.