Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silkscreen Paths cause extra pins in schematic view #308

Closed
seveibar opened this issue Nov 15, 2024 · 2 comments · Fixed by #315
Closed

Silkscreen Paths cause extra pins in schematic view #308

seveibar opened this issue Nov 15, 2024 · 2 comments · Fixed by #315

Comments

@seveibar
Copy link
Contributor

seveibar commented Nov 15, 2024

/bounty $10

Image

Copy link

algora-pbc bot commented Nov 15, 2024

💎 $10 bounty • tscircuit

Steps to solve:

  1. Start working: Comment /attempt #308 with your implementation plan
  2. Submit work: Create a pull request including /claim #308 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to tscircuit/core!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🟢 @vishwamartur Nov 15, 2024, 7:01:13 PM WIP

@vishwamartur
Copy link

vishwamartur commented Nov 15, 2024

/attempt #308

vishwamartur added a commit to vishwamartur/core that referenced this issue Nov 15, 2024
Related to tscircuit#308

Add method to prevent silkscreen paths from being interpreted as pins in schematic view.

* **SilkscreenPath.ts**
  - Add `doInitialSchematicComponentRender` method to `SilkscreenPath` class to prevent silkscreen paths from being interpreted as pins in the schematic view.
* **silkscreenpath.test.tsx**
  - Add test case to verify that silkscreen paths are not interpreted as pins in the schematic view.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants