It would be nice to have a setting for the Link in / Link out node to be only visible to the current flow.
Usecase: I like to use link nodes in more complex flows to reduce "visual complexity". A flow can get nasty having all the wires visible all the time.
I often create groups for "sub processes" of a flow, and use link in / Link out to communicate with the rest of the flow. However, creating a lot of link nodes will pollute the list of link targets quickly.
If I could say that a specific link node should be only used within the current flow, it would keep the list of link targets much shorter an cleaner.
Please let me know if you would consider such feature, and I'll be happy to implement this.
The limitation I see is that it adds a purely visual property to the node. Either we use a new property, e.g., scoped (boolean), or we use local storage, which has the advantage of not modifying the flow.json file but the disadvantage of being per user (browser).
Another possibility would be that if the node is in a flow/group/subflow, it only extends the list of nodes in that flow/group/subflow. Other flows/groups/subflows are not extended.
That would be a serious limitation that would break a lot of existing flows though. You would still need a flag in the node.
You could, I suppose, instead use Node-RED's existing context variables. Look at UIBUILDER's Cache node for an example. But if you wanted the setting to be permanent, that wouldn't really make much sense.
A simple flag added as a property to the node's would be the way to go I think.
