# LINK node suggestion
**URL:** https://discourse.nodered.org/t/link-node-suggestion/15522
**Category:** Feature Requests
**Created:** [13 September 2019 23:32 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522 "2019-09-13T23:32:17Z")
**Posts on this page:** 14
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [13 September 2019 23:32 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/1 "2019-09-13T23:32:17Z")
Ok, maybe contentious, but....
LINK nodes **are** handy to make flows neater looking and allow links between tabs.
Suggestion:
Part 1:
Links connected locally.
They are nice for local connections to _hide_ joints _going the wrong way_ (right to left on screen).
These can confuse you sometimes.
My _rule_ is unless short, any joints between nodes right to left of the screen are done by `link` nodes.
This is particularly true with routine blocks of nodes. It helps keep them as blocks.
When opening the nodes _edit_ window I am bombarded with a list of all the tabs and their `link` nodes.
Fair enough.
_ **Improvement** _ - **only** show `link` nodes which have **names** assigned by the user on other tabs.
Local `link` tabs are shown irrespective of their name state.
Why?
- If I am linking stuff on the same flow most of the time I am not worried about naming the `link` nodes.
And I can usually connect the two nodes from the edit screen.
{
Another _cheat_ way is to put the two `link` nodes (the `in` and `out`) close.
Then I join them. `Cut` the one to be moved, go to that part of the screen and `Paste` it.
Then I _wire_ it to the other node/s.
}
A quick _zoom out_ and I can see what is going on.
- If I am linking to another tab, I would say 99.9% of the time that destination `link` node will be named by me.
So only showing `link` nodes with names would really help de-clutter the huge list of unnamed `link` nodes.
Part 2:
When the big list of other link nodes is open scrolling through checking _who is connected to whom_ is not easy.
An extra button to **show only linked nodes** will then show you a cut down list of other `link` nodes connected to this one.
That will reduce the load on the user checking what is connected.
Then, if there are any incorrectly linked nodes, they can be easily un-ticked.
They won't/don't need to disappear from the list until that list is closed. Handy in case you accidently (?) un-tick the wrong one.
Part 3:
(This is really asking)
Maybe an option - somewhere - to show a tree structure for that node.
Showing it's interaction a bit better with the other flows.
(Saying it is an `in` node)
Have something like this:
The green circle is included indicating the selected node.
So if it was an `out` node, the circle would be around the respective node on the right side.
Yeah, the names are lame. But I hope it gives you the idea.
They would probably be the flow name and name of the node.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [14 September 2019 07:05 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/2 "2019-09-14T07:05:43Z")
Hi, thanks for those. I'm not sure which version you are running currently - but some improvements are on their way. In the upcoming version 1 the list is now a collapsible tree see below
And the current tab is the one with the \* next to it - so all in all the list should be much easier to navigate,
And once on the flow selecting the node will show which other tabs/flows it is connected to.
So hopefully these will both go some way to matching your thoughts.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [14 September 2019 07:12 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/3 "2019-09-14T07:12:51Z")
Ok.
Yes, I am not running the latest version.
0.20.6-ish.
Your picture shows a \* on the current tab.
But it doesn't show to which other ones it is connected.
Yes the next picture shows the links to the remote flows/tabs. But it doesn't show the `link` names as well.
I get that this would take more screen space.
So my suggestion would go on what you showed as Picture 1.
"Show all links" and it would list all connected tabs there.
So though what you show is better/nicer, it isn't quite as I suggested.
Sorry, I am not that good with graphic editing stuff, or I would construct a better explanation of what I mean.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [14 September 2019 07:24 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/4 "2019-09-14T07:24:55Z")
sorry - I hadn't ticked any of the connections in the top pic - which then show to which they are connected. - but yes there isn't a "show all connected" filter button. And yes the editor view doesn't show link names for exactly that reason (space and layout).
No worries I get what you mean. As I said hopefully it is a partial solution to your requirement.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [14 September 2019 07:28 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/5 "2019-09-14T07:28:17Z")
Yes, but that takes effort to scroll through all the tabs.
A button to `show connected nodes` would collapse all unused tabs (actually **hide** would be better) and only show the nodes on/in tabs used.
No other nodes.
That way it is a lot more compact view of the list to which the node is connected.
Re-reading your reply. Ok thanks.
I wasn't wanting to be/sound argumentative in the reply.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [15 September 2019 02:32 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/6 "2019-09-15T02:32:22Z")
(Got bored)
Here is a (poor) example of what I mean with the `node edit` and how it should look.
As I said: I am not a graphic designer. But I hope you get the idea.
And if you clicked on any of the `In` nodes, it should show a similar tree but rather than the `output` node at the top, the `in` node would be showing the tree structure from it's point of view.
---
### Author:  [@StrongTown](https://discourse.nodered.org/u/StrongTown)
#### Post date: [17 September 2019 01:45 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/7 "2019-09-17T01:45:05Z")
My comment on this topic would actually be a question. Every node that I provide a NAME to shows that name on the node within the tab, except the link nodes. Why is this? Trying to parse the connections without a name can get confusing.
ST.
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [17 September 2019 01:46 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/8 "2019-09-17T01:46:44Z")
If you hover the mouse over the `link` node the name appears.
Hope that helps.
Another "option" is (though messy) is to add a `comment` node near the `link` node and put the name there.
Better solution!
Pictures say 1000 words.
 
---
### Author:  [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [18 September 2019 16:41 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/10 "2019-09-18T16:41:28Z")
> [@StrongTown](#):
>
> Every node that I provide a NAME to shows that name on the node within the tab, except the link nodes.
No, the difference is that other nodes show their names by default, while the `link` node has it hidden by default. Check the Appearance tab in the node edit dialog.
---
### Author:  [@StrongTown](https://discourse.nodered.org/u/StrongTown)
#### Post date: [19 September 2019 10:23 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/11 "2019-09-19T10:23:21Z")
Thanks for that feedback. That did the trick. Much appreciated.
---
### Author:  [@DanEdens](https://discourse.nodered.org/u/DanEdens)
#### Post date: [17 March 2020 14:05 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/12 "2020-03-17T14:05:09Z")
Is there anyway to edit the default node to always show label? I use buckets of these things, getting annoying having to enable them all.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [17 March 2020 14:09 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/13 "2020-03-17T14:09:04Z")
You can set a default preference for regular nodes, but not for Link nodes. We should address that.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [17 March 2020 14:52 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/14 "2020-03-17T14:52:07Z")
@knolleary could there be an option to default the debug node to display the complete msg object too?
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [24 December 2020 23:13 UTC](https://discourse.nodered.org/t/link-node-suggestion/15522/15 "2020-12-24T23:13:23Z")
Only to keep things in context and under one topic rather than multiple posts on the same thread.
On the point about the `out` and `in` nodes being on the same flow and going from one end to the other:
I seem to remember it was asked how this could be done, as there are no _links_ to the other flows shown when it is on the same flow.
Ok, so you are at one of either nodes. (in or out)
You click on the link and it turns orange.
The RMB function has no assignations at this point.
Make it that if you RMB on the link, you get two options visible: `in` and `out`.
They take you to the respective node for that link.
This would then allow you to do this from even a mid-point. (Though why you would want to do that is a bit beyond me at this time)
But that is my recent thoughts on it.
This is only my thoughts submitted for your consideration.