Abse - @Seve what should we do about vias in cr...

imo we should detect traces connected to crystals and warn if it has vias

<@757706909351411845> wdyt?

<@398467566588264449> maybe you'd be interested in implementing impedence matching

i think we already do this

but there are just a ton of things that can go wrong

so it needs refinement

e.g. the crystals, if they aren't using crystal elements, need to have a warning to tell the user to use crystal elements

we should honestly like block autorouting if the crystal paths aren't planned

the crystal path is really bad on this one too

otherwise this board is like pretty sweet

even the usb is somehow impedance matched(!)

<@757706909351411845> first pr https://github.com/tscircuit/checks/pull/272

what does that pr do?

it looks like it actually does the opposite of what you want

it reduces it from an error to a warning?

you want it to be an error ?

oh error when there is a via in crystal trace but warning when not using the crystal element ?

https://github.com/tscircuit/core/pull/3713

Does any autorouter currently support maxViaCount

We might support it but it is a bit of a tough constraint, better solved with pcbPath etc

Since you can pre route the crystal

<@757706909351411845> how should impedance matching be applied ?