I would like to propose a feature enhancement for Node-RED that allows users to directly navigate from a Link-Call Node to its corresponding definition node. Currently, while Link-Call Nodes help organize flows by linking different parts, there is no built-in functionality to jump directly to the node that is being called.
Proposed Feature:
Implement a feature that allows users to click on a Link-Call Node and be taken directly to the node it references. This could be achieved through a context menu option or a simple double-click action.
Benefits:
Improved usability and efficiency when working with complex flows.
Easier debugging and flow management by allowing users to quickly access the linked nodes.
Enhanced user experience, especially for those who work with large and intricate Node-RED projects.
Additional Notes:
This feature would greatly benefit users who manage extensive flows and need to navigate between various nodes frequently. Thank you for considering this request!
PS: I too would like a (built in) way to navigate from link-call to the link node - I did a large project recently and this was very much a missing feature IMHO.
As @Steve-Mcl already linked to, I did implement something that uses green dots instead of double clicks.
Admittedly not that clean especially if colour blind but yer, it works.
One thing that I noticed was that it's one thing to jump to the corresponding link in node (from a link call node) but it's equally important to come back to the original link call node. Hence my green dot is a bidirectional solution allowing for jumping back to the original link call node, across flow tabs, from a link in node.
This should definitely be taken into consideration when implementing any "professional" solution to the problem because it definitely is a problem - even for smaller projects.
This (jumping back) will work only if there is a 1:1 relation between the calling node and the called node, in which case there is not much value in using link-call anyway (link-call is good for calling generic "subroutines" from many different places).
Moreover, link-call supports a dynamic target (msg.target) which is only resolved in runtime (and IMHO is preferable to statically pointing to link-in Id's which can change upon copy/paste, import etc.)
I think adding a content-menu option for the node to jump to its target would be an easy win without having to invent any new UX decoration on the node itself (which has always been the sticking point here).
Jump back (in my mind) need only be akin to a browsers back button. In this scenario, navigating flows becomes far more superior.
I used to program PLCs and whenever I switched to a flavour of PLC that did NOT have "jump back", it was super easy to lose focus/mental track of where you were and why you went down that rabbit hole if the first place. Quite literally, downtime stoppages increased due to the lack of this feature. I am not even kidding!
In essence, I am suggesting, if we add "Jump To" capability in Node-RED, I instantly want "Jump Back". For anyone who doesn't believe the benefits of this - once we have it, I will ask "who would like us to remove this feature"
Not quite correct since - in the solution I created - once I jump from a link-call node to the link-in node, I mark the green dot on the link-in node with the id of the link-call node from which I came so that I know were I came from. Clicking on the green dot on the link-in node brings me back to the original link-call node.
Totally agree, thankfully I don't have to wait for an "official solution" having my own
And dynamic targets are a case of I can break my finger with a hammer but I can also nail nails - sure I can have a link call node with a dynamic target but the other 90% of link call nodes can be navigable.
