Skip to content

feat: add blind and buried via board option - #808

Merged
seveibar merged 1 commit into
mainfrom
feat/board-routing-layer-constraints
Aug 22, 2026
Merged

feat: add blind and buried via board option#808
seveibar merged 1 commit into
mainfrom
feat/board-routing-layer-constraints

Conversation

@seveibar

@seveibar seveibar commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add the board-level allowBlindAndBuriedVias boolean
  • default it to false, so ordinary boards request full-stack generated vias unless they explicitly opt in
  • clarify that CopperPourProps.unbroken reserves a pour during autorouting while allowing vias to cross through antipads
  • regenerate the public component and props references

Contract

allowBlindAndBuriedVias={false} is the default and restricts newly generated vias to the full board stack. Setting it to true allows the autorouter to generate blind and buried vias when the fabrication process supports them.

To keep an unrelated trace from splitting a copper pour, board authors can mark the pour unbroken; vias may still cross the reserved region using antipads.

Cross-repository stack

Validation

  • bun test — 442 pass, 0 fail
  • focused boolean tests — 2 pass, 0 fail
  • bun run typecheck
  • bun run check-circular-deps
  • bun run build
  • bun run format:check
  • all four required documentation generators

Comment thread tests/board.test.ts Outdated
@seveibar seveibar changed the title feat: add board autorouting constraints feat: add blind and buried via board option Aug 22, 2026
@seveibar seveibar reopened this Aug 22, 2026
@seveibar
seveibar force-pushed the feat/board-routing-layer-constraints branch from ff5da2d to 4365a56 Compare August 22, 2026 18:15
@seveibar
seveibar merged commit c61a030 into main Aug 22, 2026
5 checks passed
@tscircuitbot

Copy link
Copy Markdown
Contributor

Thank you for your contribution! 🎉

PR Rating: ⭐⭐
Impact: Minor

Track your contributions and see the leaderboard at: tscircuit Contribution Tracker


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.

2 participants