Skip to content

Recommend idiomatic identifiers for invalid pin labels - #2976

Merged
seveibar merged 1 commit into
mainfrom
agent/recommend-pin-label-identifiers
Aug 2, 2026
Merged

Recommend idiomatic identifiers for invalid pin labels#2976
seveibar merged 1 commit into
mainfrom
agent/recommend-pin-label-identifiers

Conversation

@seveibar

@seveibar seveibar commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • recommend idiomatic V3_3, V5, and related identifiers for common voltage pin labels such as 3.3V, +3V3, and +5V
  • include the recommendation in both ignored-property warnings and schematic pin-label parse errors
  • add regression coverage for chip pin labels and schematic arrangements

Why

tscircuit pin identifiers only support letters, numbers, and underscores. Common module labels containing + or . were filtered out, and schematic arrangements could then fail with an opaque error. This can produce empty/black footprint renders when the component never finishes creating.

The new guidance maps common voltage forms to exact idiomatic identifiers, for example:

  • 3.3V or +3V3 -> V3_3
  • +5V -> V5

The actual voltage metadata remains unchanged; only the pin identifier recommendation is normalized.

Verification

  • bun test tests/components/normal-components/chip-invalid-pin.test.tsx
  • bun run build
  • bunx tsc --noEmit

@vercel

vercel Bot commented Aug 2, 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 2, 2026 8:27pm

Request Review

@seveibar
seveibar marked this pull request as ready for review August 2, 2026 20:32
@seveibar
seveibar merged commit be84f16 into main Aug 2, 2026
11 checks passed
@seveibar
seveibar deleted the agent/recommend-pin-label-identifiers branch August 2, 2026 20:32
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.

1 participant