Feature request: panel rails, fiducials, tooling holes, V-score and tab control

Open
#5,067 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Abse2001 is already working on this.

Since Nov 2, 2026.

  • #5078 by @Abse2001 — open
  • #5081 by @Abse2001 — open
  • #5216 by @Abse2001 — open
  • #5217 by @Abse2001 — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react, typescript
Domain
devtools

Research direction

This bundles six separate panel features, so it needs a maintainer to split it before anyone can start. Start with how <panel> handles edgePadding and panelizationMethod, and where <toolingrail>, <fiducial> and <hole> are accepted, since the issue says these are only valid inside a <board>. Done means one item is scoped into its own issue with an agreed API, and the related issues #5065 and #5066 are checked for overlap.

Written by the indexing model from the issue text.

Description

Feature request: a few things a fab panel needs that <panel> can't express yet.

  • Rails: edgePadding makes a frame, but nothing can go on it. <toolingrail> is in props with only children, and core doesn't use it.
  • Fiducials and tooling holes on the panel: <fiducial> and <hole> only work inside a <board>, and a panel can only contain boards.
  • V-score as a panelizationMethod, for rectangular boards.
  • Tab control: the number of tabs per edge, their positions, and keep-outs. Today it's one centred tab per edge.
  • Panel silkscreen: a panel id, board names, a date.
  • A size check against a minimum and maximum panel size, since assembly lines have both.

Related: #5065, #5066.

Dominant language
TypeScript
Stars
61
Forks
256
Avg merge
20h 21m
Merged PRs (30d)
289

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tscircuit/core

All issues in tscircuit/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.