We've all run into this: a junction node sits right on top of a wire — visually it looks like part of the flow — but it isn't actually connected to it. Finding these cases currently takes a lot of effort, because nothing in the editor distinguishes a junction that's properly wired from one that merely overlaps a wire.
The nasty case is a junction with exactly one connection (one wire in and nothing out, or vs.). A junction with zero connections is at least somewhat visible, since it usually sits on its own. But a single-connection junction that happens to lie over another wire is practically impossible to spot by eye — and Ctrl+F doesn't help either, because junctions have no name or properties to match against.
It would be very user friendly if such cases could be more easily identifiable. Two possible directions (either would solve it):
- A way to find junction nodes by their number of connections — the most useful being 0 and 1. This could live in the search, or as a "validate flows"-style check.
- Or, junctions with fewer than two connections could be rendered with a visual marker (for example a highlight, a different color, or a red exclamation mark), so they stand out on the canvas.
For context: right now the only approach I've found is to parse flows.json and count, for each junction, how often its ID appears in other nodes' wires (plus subflow in/out/status ports). That identifies which junctions are affected — but it still doesn't help me locate them in the editor: a junction has no name, so Ctrl+F won't find it by ID, and there are no visible coordinates to navigate to. In practice I have to trace back to a named upstream node to even find the junction on the canvas.
Optional, more general idea: the mechanism described in option 1 could be extended to any node type, not just junctions. For most standard nodes this is less interesting, but for function nodes it would be handy — e.g. quickly finding function nodes with no outgoing wire, which are often a forgotten or dead branch. The junction case above would just be one specific use of that more general capability.
Thanks!
