Load conflicts last while fetching scenario data #14544
Open
+4
−1
Conversation
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
…calculation succeeded Signed-off-by: Pivouane (Pierre Santamaria) <[email protected]>
emersion
requested changes
Dec 27, 2025
| }); | ||
|
|
||
| const isReadyToFetchConflicts = | ||
| allTrainsSimulated && projectionPath?.pathfindingStatus === 'succeeded'; |
Member
There was a problem hiding this comment.
The current train might fail pathfinding, but we still want to load conflicts in that case.
More generally, I don't see why conflict loading should be tied to the projection. We want to load conflicts after all trains are simulated, regardless of the projection status.
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.
#14504
Frontend will now only fetch conflicts once pathfinding process succeeded