core: expose allowed track sections in the pathfinding api#17372
Merged
Conversation
4675e90 to
d5d20bf
Compare
Erashin
requested changes
Jun 24, 2026
Erashin
reviewed
Jun 24, 2026
Khoyo
reviewed
Jun 24, 2026
d5d20bf to
772a5c6
Compare
The pathfinding api did not use any track section constraints whereas the simulation did which means that pathfinding requests might be valid but their corresponding simulation may not have been doable. Signed-off-by: Martin Bourbier <mbourbier28@gmail.com>
772a5c6 to
771c3bd
Compare
Erashin
approved these changes
Jun 25, 2026
Contributor
There was a problem hiding this comment.
Good job and thanks for that! Been waiting for this feature for a while :)
As long as you modify the STDCMEndpoint's allowedTrackSections accordingly, this looks mergeable to me! (This could be done in another PR btw, as it will entail small changes on the editoast side as well)
5ddf165 to
771c3bd
Compare
This file contains hidden or 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
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.
Part of #16699
The pathfinding api did not use any track section constraints whereas the simulation did which means that pathfinding requests might be valid but their corresponding simulation may not have been doable.
This PR only implements the core part: editoast and front will follow soon