Seve - Can someone look into this? https://gith...

<@757706909351411845>

just remove autorouter="sequential-trace"

oop

well i guess the issue is just to throw on sequential trace autorouting for that case "Not supported in sequential trace autorouter"

where we can chagne this ?

core

i think if core detects any sequential trace autorouting issue it should recommend turning it off haha

tbh why do we still have it ?

just legacy support- a lot of people unfortunately use it- we could create a "deprecation_warning" circuit json thing and have it emit

ai seems to like it because it does make the autorouting more predictable

<@757706909351411845> ``` const PassiveInSubcircuit = () => ( <subcircuit name="PassiveBlock" pcbX={2} pcbY={0} autorouter="sequential_trace" > <resistor name="R1" resistance="10k" footprint="0805" pcbX={0} pcbY={0} /> <trace from=".R1 > .pin2" to="net.GND" /> </subcircuit> ) export default () => ( <board width="10mm" height="7mm" autorouter="sequential_trace"> <pinheader name="J1" pinCount={1} footprint="pinrow1" pcbX={-3} pcbY={0} connections={{ pin1: "net.GND" }} /> <PassiveInSubcircuit /> <trace from=".J1 > .pin1" to=".PassiveBlock > net.GND" /> <copperpour name="top_gnd_pour" layer="top" connectsTo="net.GND" padMargin="0.25mm" traceMargin="0.2mm" /> </board> ) ```

<@757706909351411845>

oh why sequential trace for the autorouter

Oh codex haha

Same issue tho

yea it might even be better for snapshot consistency haha

but ya ya noted