← Back to community index
# contributor·Active

Arhan - While building a board in the tscircuit...

While building a board in the tscircuit repo, I noticed something and wanted to check if it's intentional. I was trying to disable placement DRC so the autorouter could continue despite overlapping footprints. Circuit({ platform: { placementDrcChecksDisabled: true } }) works as e

Started by ArhanJul 23, 20268 messages

Discussion

Last active last month · plain text
Arhanoriginal post
While building a board in the `tscircuit` repo, I noticed something and wanted to check if it's intentional. I was trying to disable placement DRC so the autorouter could continue despite overlapping footprints. `Circuit({ platform: { placementDrcChecksDisabled: true } })` works as expected, but `<board placementDrcChecksDisabled />` has no effect—the placement errors remain and autorouting is still skipped. I traced it and found the board prop gets stripped by the component schema before it reaches `@tscircuit/core`. Is `placementDrcChecksDisabled` only intended to be supported via `PlatformConfig`, or is this an oversight?
Seve
it is an oversight probably
Arhan
In that case, would you prefer I open an issue in `@tscircuit/props` ?
Seve
no sorry i thought you said it was part of the board spec
Seve
i don't know what the api is for adjusting the DRC checks via board
Seve
i would need more evidence to make the determination
Arhan
I dug through the history, docs, PRs, and type definitions. I couldn't find evidence that `placementDrcChecksDisabled` was ever intended to be a board/group prop. The docs only expose it through `PlatformConfig`, and all of the PRs that introduced the DRC flags scoped them to `PlatformConfig` only. The reason I thought it might be an oversight is that `schematicDisabled` followed a similar evolution and was later mirrored to board props, and core already supports inherited properties. But I don't have enough evidence to conclude that was the intended API here.
Seve
thanks for doing the research!

Want to add to the conversation?

Reply in Discord so your notes stay connected to the source.
Continue in Discord ↗