# Custom nodes to inherit linking from link-in, link-out nodes

**URL:** <https://discourse.nodered.org/t/custom-nodes-to-inherit-linking-from-link-in-link-out-nodes/33061>\
**Category:** Developing Nodes\
**Created:** [18 September 2020 22:09 UTC](https://discourse.nodered.org/t/custom-nodes-to-inherit-linking-from-link-in-link-out-nodes/33061 "2020-09-18T22:09:21Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![molesworth](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/molesworth/32/11748_2.png) [@molesworth](https://discourse.nodered.org/u/molesworth)\
**Post date:** [21 September 2020 07:58 UTC](https://discourse.nodered.org/t/custom-nodes-to-inherit-linking-from-link-in-link-out-nodes/33061/9 "2020-09-21T07:58:52Z")

</div>

> [@pitus](#):
>
> ... **to allow custom node developers gain control over which other nodes they can link to** (the list showed by the `link` editor - right now shows only other `link` nodes and shows all of them so the list could get huge - custom node can show only matching custom nodes with any kind of additional filtering that makes sense to that node as well as handle wildcard matching).

This sounds similar to the idea discussed in a recent thread - [Restricting connections between custom nodes](https://discourse.nodered.org/t/restricting-connections-between-custom-nodes/32756) - and I think the conclusion, and certainly my thought, is that restriction connection types is not really a good idea for several reasons. For example, new nodes might be unable to connect to yours even though it would be valid, or someone might think of a clever use for your node but be unable to link to it.

Can you maybe describe the sort of use-cases where restricting connections would make sense, and not limit future uses of a node?

---

_[View the full topic](https://discourse.nodered.org/t/custom-nodes-to-inherit-linking-from-link-in-link-out-nodes/33061)._