# 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:** 3

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [19 September 2020 19:40 UTC](https://discourse.nodered.org/t/custom-nodes-to-inherit-linking-from-link-in-link-out-nodes/33061/3 "2020-09-19T19:40:57Z")

</div>

This sort of thing has been discussed before, for example [here](https://discourse.nodered.org/t/possible-new-contributed-message-gate-node/7382) and [here](https://discourse.nodered.org/t/q-gate-feature-request-link-gates-together/26480). The general consensus seems to be that the cost in readability/maintainabilty outweighs the benefits. Not that anything stops you from pursuing the idea if you wish. A word of caution is that the mechanisms supporting the `link` nodes (as well as the `status` and `catch` nodes) are buried deep in the [runtime](https://discourse.nodered.org/t/examples-that-publish-subscribe-mqtt/7320/14) and not available to contributed nodes.

---

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