Skip to content

Conversation

@RaghavArora14
Copy link
Contributor

@RaghavArora14 RaghavArora14 commented Oct 24, 2025

/Fixes #1576
/claim #1576

Reproduction

Before Fix:
image
image
Small spacing - width: 0.4 height: 1
Large spacing - width: 1.6 height: 4
Test FAILED

Fix

Changed width/height calculation in getAllDimensionsForSchematicBox.ts to use fixed MIN_PADDING (0.4) instead of schPinSpacing * 2.
After Fix:
image

Result

After fix, box width stays constant at 0.4 regardless of schPinSpacing value.

Small spacing - width: 0.4 height: 1
Large spacing - width: 0.4 height: 2.8
Tests PASS

@vercel
Copy link

vercel bot commented Oct 24, 2025

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

Project Deployment Preview Comments Updated (UTC)
tscircuit-core-benchmarks Ready Ready Preview Comment Oct 27, 2025 5:32pm

@RaghavArora14
Copy link
Contributor Author

hey @seveibar can i get a review on this, i reproduced this issue and then tried the fix. Please let me know if this is correct

Copy link
Contributor

@seveibar seveibar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no point in requesting a review with failing tests

also rename your test appropriately for the directory you put it in

@seveibar
Copy link
Contributor

also you need snapshot tests

@seveibar
Copy link
Contributor

@RaghavArora14 request your assigned maintainer for review. Work with them directly, join discord if needed https://tscircuit.com/join

https://docs.google.com/spreadsheets/d/1BU96V97WA6Xv9WyjIyN1qmdWvoJgLEir8mdqz--4B_o/edit?usp=sharing

@RaghavArora14
Copy link
Contributor Author

okay thanks, will ask the maintainer soon after fixing this up

- Changed width/height calculation to use fixed MIN_PADDING (0.4) instead of schPinSpacing * 2
- This ensures box dimensions only change based on pin positions, not pin spacing
- Added tests to verify width/height remain constant when schPinSpacing changes
- Updated snapshots for affected tests

Fixes tscircuit#1576
@RaghavArora14
Copy link
Contributor Author

hey @ShiboSoftwareDev can i get a review on this please, all the tests are now passing, have reproduced the issue and added test snapshots too

@RaghavArora14
Copy link
Contributor Author

also had created a seperate branch to reproduce the issue before fixing it and that was causing some issues with the format check so had to force push sorry if that causes any issues, lmk how i can fix those

@ShiboSoftwareDev
Copy link
Contributor

combine your repros into a single circuit in a single file

Removed comments explaining fixed padding for schWidth and schHeight.
@RaghavArora14
Copy link
Contributor Author

okay resolved the comments issue, will add them into a single repro file and ask for a review is that cool?

- Access footprint.children to get portHints instead of Port objects
- Port names are auto-generated (pin1, pin2), but portHints have actual labels
- Now correctly extracts meaningful labels like 'B8', 'A5' from USB-C footprints
- repro3 and repro68 tests now pass
- Footprint in props is still a React element, not instantiated
- Access this.children to find the instantiated Footprint component
- Now correctly extracts portHints labels (B8, A5, etc.)
- repro3 width increased from 0.4mm to 1.3mm (much better proportions)
const allPinLabels = {
...pinLabelsFromPorts,
...props.pinLabels,
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this merging necessary anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kept props.pinLabels merging - Still needed for label-to-pin-number mapping in getNumericSchPinStyle() and getAllDimensionsForSchematicBox() to handle non-numeric labels like "A4" or "C" in schPortArrangement

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you sure?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(please show the difference via a snapshot)

@seveibar seveibar merged commit 5268725 into tscircuit:main Oct 27, 2025
13 checks passed
@seveibar
Copy link
Contributor

/tip $30

@algora-pbc
Copy link

algora-pbc bot commented Oct 27, 2025

🎉🎈 @RaghavArora14 has been awarded $30 by tscircuit! 🎈🎊

@tscircuitbot
Copy link
Contributor

Thank you for your contribution! 🎉

PR Rating: ⭐⭐
Impact: Minor

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


Comment posted by tscircuitbot

@ShiboSoftwareDev
Copy link
Contributor

@RaghavArora14 don't give up next time, your first contributions will always be difficult, but the learning is invaluable so don't miss any chances.

@RaghavArora14
Copy link
Contributor Author

@ShiboSoftwareDev, thanks for all your help and patience throughout this pr, and yes i will keep a lookout for more issues and try to contribute more. Will keep on learning.

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.

Fix schPinSpacing changing the width of the schematic box

4 participants