Upstream merge 2024-06-19 #215
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add plan query that follows the relay connection specification
…t-breaking-change-in-url Fix debug client after breaking change in dependency graphql-request
…/com.google.cloud-libraries-bom-26.x fix(deps): update dependency com.google.cloud:libraries-bom to v26.40.0
Remove unused Siri code
Remove TravelTime API
…ble-manager Extract timetable manager for realtime trip updates
…-semantics Use enum instead of boolean for real time update semantics
…/com.graphql-java-graphql-java-22.x Update dependency com.graphql-java:graphql-java to v22.1
…e-plugin to v3.3.0
…/debug-ui-dependencies-(non-major) chore(deps): update debug ui dependencies (non-major)
…/geotools.version fix(deps): update geotools.version to v31.2
…maven-plugin to v9
miles-grant-ibigroup
approved these changes
Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This one brings the brand new
planConnectionquery which allows you to specify the access and egress mode separately.It is also the first step towards sending several access/egress modes and have the backend select the "best" ones (but that is not implemented yet).
Here is the documentation: https://docs.opentripplanner.org/api/dev-2.x/graphql-gtfs/queries/planConnection
@daniel-heppner-ibigroup This will be interesting for you.