Repository navigation
fix(route): Waypoints that force a loop far longer than your distance are now rejected - #56
Merged
Merged
Conversation
willsawyerrrr
enabled auto-merge (squash)
October 20, 2026 07:58
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Waypoints were only checked one at a time against the start, so several pins in different directions could force a loop far longer than the target (e.g. three pins ~400 m out for a 1 km route).
The server now checks the shortest straight-line round trip from the start through all pins against 1.5 × the target distance (the same bound a lone pin had). The iOS shape sheet applies the same check, marking all pins orange when the tour is too long.
Linear: WSD-623