# Arhan - While building a board in the tscircuit... Channel: #contributor Source: https://discord.com/channels/1233487248129921135/1529979751563923646 Started: 2026-07-23T22:33:18.883000+00:00 Last activity: 2026-07-24T17:13:18.287000+00:00 ## Arhan — 2026-07-23T22:33:18.422000+00:00 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 `` 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? Attachment: Screenshot_2026-07-24_at_4.02.07_AM.png — https://community.tscircuit.com/media/1529979751316586660 ## Seve — 2026-07-23T22:36:39.679000+00:00 it is an oversight probably ## Arhan — 2026-07-23T22:39:00.748000+00:00 In that case, would you prefer I open an issue in `@tscircuit/props` ? ## Seve — 2026-07-23T22:51:12.517000+00:00 no sorry i thought you said it was part of the board spec ## Seve — 2026-07-23T22:51:25.196000+00:00 i don't know what the api is for adjusting the DRC checks via board ## Seve — 2026-07-23T22:51:34.283000+00:00 i would need more evidence to make the determination ## Arhan — 2026-07-24T10:15:10.119000+00:00 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 — 2026-07-24T17:13:18.287000+00:00 thanks for doing the research!