# 0hmx - Problem: is unordered today... Channel: #contributor Source: https://discord.com/channels/1233487248129921135/1570160412962586685 Started: 2026-11-11T19:36:54.997000+00:00 Last activity: 2026-11-12T16:50:51.159000+00:00 ## 0hmx — 2026-11-11T19:36:54.620000+00:00 **Problem:** `` is unordered today. It's just a set of pins to connect. Making the order meaningful would change the behavior of every trace that uses `path`. The workaround (what core #5384 does) is to treat the order as meaningful only when a `` references the trace. I don't like that: it's hidden, undocumented behavior that you can't see by looking at the trace. **Proposal:** give `` two flat props that list each lane's pins in signal order, from the first pin to the last: ```tsx ``` This keeps `` exactly as it is, makes the order explicit where it matters, and gives the router what it needs: an ordered list of pins per lane, which maps directly onto the SRJ "path of point ids". The props are flat rather than nested, following the handbook (§1.2, "avoid nesting"). `positiveConnection` and `negativeConnection` are **deprecated** but keep working, so existing designs don't break. <@757706909351411845> ## Seve — 2026-11-11T19:45:38.407000+00:00 i think path is ordered ## Seve — 2026-11-11T19:45:45.441000+00:00 path should be ordered i think ## Seve — 2026-11-11T19:46:31.401000+00:00 <@400684445054795796> you REALLY need to be careful, because even though we've discussed this a lot, you've dropped the VERY IMPORTANT `connectionPath` naming ## Seve — 2026-11-11T19:46:45.227000+00:00 you've omitted `connection`, which is so important ## Seve — 2026-11-11T19:47:30.861000+00:00 <@809856037376491570> note the comment regarding core not always treating the path is ordered, that is a bug you've introduced here. The path should always be ordered, not conditionally ## Rishabh — 2026-11-11T19:54:44.585000+00:00 Ohh ## 0hmx — 2026-11-11T20:08:07.588000+00:00 the auto router uses the mst and dose not respect core; this is more on the auto router side; not because of <@809856037376491570> core respects the order internally but auto router dose not care Attachment: image.png — https://community.tscircuit.com/media/1570168268361306203 ## Seve — 2026-11-11T20:12:39.180000+00:00 the netpointpairssolver should use the path given by the user ## Rishabh — 2026-11-12T06:06:51.466000+00:00 https://github.com/tscircuit/length-matching-solver/pull/87 https://github.com/tscircuit/tscircuit-autorouter/pull/3643 cc <@400684445054795796> <@757706909351411845> This was the approach I had ## Seve — 2026-11-12T16:50:51.159000+00:00 i think your autorouter isn't using the path data properly- i could be wrong