-
Notifications
You must be signed in to change notification settings - Fork 34
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
GraphQL Trip Stop Sequence Support #604
GraphQL Trip Stop Sequence Support #604
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.
Looks good, just a few thoughts about types as usual
departureStoptime?: TripStopTime; | ||
gtfsId?: string; | ||
id: string; | ||
tripHeadsign?: string; |
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.
this field and gtfsId
are both required on the schema. Should we make them required here too? Just because they're required on the schema doesn't mean we have to request them in our query, so I can see it both ways.
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.
The data passed on this component is sometimes generated by a client instead of fed right in from OTP. Do you think it's still worth making this change? I guess those projects would then throw TS errors, which is good.
# Conflicts: # packages/types/src/index.ts
This PR adds stop sequence support when using the new GraphQL API.