repro61-schematic-trace-net-jumping#1503
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
imrishabh18
reviewed
Oct 14, 2025
Member
imrishabh18
left a comment
imrishabh18
left a comment
There was a problem hiding this comment.
What do you mean by "net jumping"? There is an issue for sure, like the trace was not needed
seveibar
approved these changes
Oct 14, 2025
Contributor
|
the issue here is more like there's a duplicate net label fwiw |
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
3 participants
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.
Adds a Repro test to ensure schematic traces with the same net name don’t visually merge. The new repro verifies that nets like “VCC” and “GND” remain isolated even when reused on multiple components, preventing unintended trace jumps in the schematic view.
Ref #1498