Skip to content

feat: propagate blind and buried via board option - #3374

Draft
seveibar wants to merge 1 commit into
mainfrom
feat/board-routing-layer-constraints
Draft

feat: propagate blind and buried via board option#3374
seveibar wants to merge 1 commit into
mainfrom
feat/board-routing-layer-constraints

Conversation

@seveibar

@seveibar seveibar commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • serialize <board allowBlindAndBuriedVias> to Circuit JSON as allow_blind_and_buried_vias
  • always materialize false for an actual board unless it explicitly opts in
  • translate the Circuit JSON field to Simple Route JSON as allowBlindAndBuriedVias
  • preserve legacy standalone/group behavior by omitting the Simple Route JSON field when no pcb_board exists

Cross-repository stack

This PR remains a draft until the props and Circuit JSON packages above are published. It was built and tested locally against their exact clean feature commits (4365a56 and 97189da).

Contract

For board-backed routing, false requests full-stack newly generated vias and true permits blind and buried generated vias. Existing authored partial-depth vias are not rewritten. A boardless conversion omits the field so standalone callers retain the autorouter's legacy compatibility behavior.

Validation

  • all autorouting utility tests, the two board propagation tests, and all three affected inline snapshots — 42 pass, 0 fail, 4 snapshots, 126 assertions
  • one test per newly added Core test file
  • bunx tsc --noEmit against the exact local props/Circuit JSON builds
  • bun run build against the exact local props/Circuit JSON builds
  • bun run format
  • git diff --check

@vercel

vercel Bot commented Aug 22, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
tscircuit-core-benchmarks Ready Ready Preview Aug 22, 2026 6:26pm

Request Review

@github-actions

Copy link
Copy Markdown

This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant