Conversation
This branch has not been 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
1 participant
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.
PR Description
Summary
Fixes an edge-routing bug where connector arrows could terminate in empty space instead of visually attaching to the destination node. This was especially noticeable when multiple edges shared a target or when endpoint spacing adjustments were applied for sibling routing.
What changed
Kept the final edge endpoint anchored to the actual target handle position rather than offsetting it during sibling/fanout routing.
Preserved route spacing and corridor logic for source-side branching, without letting that offset distort the final connection point.
Added/updated routing safeguards so imported or stale ELK routes still fall back cleanly when the geometry no longer matches the live node positions.
Why this fixes the bug
The root problem was that the path generator used route offsets as if they were the true terminal coordinates. That caused the arrowhead to stop short of the destination node and appear disconnected. By pinning the final endpoint to the real target handle, the arrow always connects properly while the route can still bend around neighboring edges.