Wow - well, at the risk of having my baby called ugly... imo, this is not only very useful, but fairly nice looking! ;*)
debug node clearly has a wire attached (as denoted by the arrowhead), while the wire is routed behind the
subflow node and not connected (an empty input port defaults to a diamond shape).
Frankly, I could take it or leave it - but the people paying my salary LOVE the arrowheads. And since I don't want to continue to be in the business of maintaining custom editor code just to draw some arrowheads, I have a proposal: pluggable functions for common editor svg drawing tasks.
That way, the core team would not have to deal with requests for:
- alternate wire routing paths (iirc, discussed in google groups in 2018)
- input/output port shapes (see Nick's suggested implementation)
- extra canvas background elements (e.g. swimlanes anyone?)
- alternate displays for the grid (i.e. major/minor tics, as requested recently)
Users would be free to add their own SVG "styling" to the editor without changing the flow file format. I could imagine installing contributed "themes" from the flows library, similar to applying different CSS styles/themes for the dashboard. And since it would get me out of custom NR editor maintenance, I'd be willing to put together a PR to get the ball rolling...
Can I get an "Amen", anyone? Or is this just a bunch of faff? Inquiring minds want to know...