-
Notifications
You must be signed in to change notification settings - Fork 32
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
When the component is placed outside the board and connected, It should throw error #540
Comments
/bounty 10$ |
💎 $10 bounty • tscircuitSteps to solve:
Thank you for contributing to tscircuit/core! Add a bounty • Share on socials
|
@imrishabh18 Could you please let me know where you are encountering the error? I’m unable to see it on my end. If you could share the details, it would help me in resolving the issue. |
@techmannih Read the description, it says to THROW an error when the components are placed outside the board and connected, and not this is THROWING an error. |
@imrishabh18 Oh, yeah! Got it. I was misunderstanding. we need to do this in 3d-viewer or in this repo board component? |
/attempt #540 Options |
@UTK-a-RSH: Reminder that in 2 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
Just as a note on this, the error should be a circuit json error, we don't want the rendering process to throw |
@seveibar Please Explain this a bit more |
Now I got what you were to trying to make me understand thanks now I have reached to the point. |
The bounty is up for grabs! Everyone is welcome to |
https://snippets.tscircuit.com/editor?&snippet_type=board#data:application/gzip;base64,H4sIAPuPj2cAA42QvQ6CMBRGd57iphMMQlFH6ELiAzC5llJso/1JqdHE+O422AbD5Hi+nJuTXP60xnkY+UTvNw95AS2BPANoBkPdCA85etGiWikEgsuL8AFwIBKcYDk+y9kbtxDAF6lmPGhXFNfJGG+d1OEWH/E+zZqqoPV14pmJc/s6vCNaNqxYxR6jljK5BiPHIsbYnv6qdpvqbpNNnLreUcZhcka1qOxrIFBaqWsE3oSh+xmWi6Za3key4gPg67TLYQEAAA==
When the components are placed outside the board and are connected, then the snippet should throw error and not draw the traces.
The text was updated successfully, but these errors were encountered: