config node in config node

I’m trying to get a series of custom nodes created where one config node includes another config node. A simple less specific example could be if you want to have a “host” config node that defines your server providing a couple of services - then you have several “service” config nodes and they all should point to the “host” config node and provide additional configuration on top. This is quite beneficial if your “host” needs to change and you need to update only once…

The issue I’m running into is that the UI appears to support this setup when I use in the config node something like this (in this case the “parent” config node defines an IoT sub-network):

    <div class="form-row">
        <label for="node-input-network"><i class="fa fa-globe"></i> Network</label>
        <input type="text" id="node-input-network">
    </div>

but the network information is not stored as part of the node config and therefore not accessible (or I don’t know how). What I thought would be the correct setup is unfortunately not working. The UI just shows a simple textbox instead of the config node selection UI:

    <div class="form-row">
        <label for="node-config-input-network"><i class="fa fa-globe"></i> Network</label>
        <input type="text" id="node-config-input-network">
    </div>

Not sure if this is an issue or actually a feature request (or I’m just not clever enough to get it to work).

[knolleary]

The ability to have config nodes under config nodes will arrive in the 0.14.0 release.

[sirockin]

thanks @hardillb and @knolleary for replying so quickly. I’ll have a closer look at my code and the examples you gave me first and see if I can work it out.