Skip to content

fix: treat isGround aliases as ground, not only the name GND - #1107

Open
Flame119052 wants to merge 1 commit into
tscircuit:mainfrom
Flame119052:cursor/ground-named-nets-73fd
Open

Flame119052 wants to merge 1 commit into
tscircuit:mainfrom
Flame119052:cursor/ground-named-nets-73fd

Conversation

@Flame119052

Copy link
Copy Markdown

Summary

Ground rail policy, unrouted-trace recovery skip, and outer-column GND label placement all looked up the literal net name "GND". Core already sets isGround on aliases (AGND, VSS, USB_GND, …), so those nets were treated as ordinary signals.

This collects every connectivity id that is either the canonical GND name (existing fixtures) or an isGround net connection, and uses that set in the three call sites.

Fixes #747

Test plan

  • bun test (352 pass, 4 skip)
  • tsc --noEmit
  • New coverage: AGND + isGround applies rail policy, skips recovery, and moves the shared rail label to the outer column
  • Canonical GND without isGround still works
  • Unmarked aliases such as RETURN / VDD are not treated as ground

Core already marks AGND, VSS, USB_GND, and similar nets isGround.
Three solver paths still keyed off the literal net name "GND", so
manually named ground nets skipped rail policy, recovery skip, and
outer-column label placement.

Fixes tscircuit#747
@vercel

vercel Bot commented Sep 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
schematic-trace-solver Ready Ready Preview Sep 8, 2026 8:24pm UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

something is broken related to manually named nets

1 participant