The HTTP In edit dialog currently displays the default, automatically generated, config node select box if the swagger node is installed.
Unlike other uses of config nodes, I don't think it makes sense to allow the user to pick from a list of existing swagger-doc nodes. There should be a closer affinity between the nodes - it either has a swagger-doc node associated or it doesn't.
We could either hack in special handling for this case in the HTTP In node, or add a more generic solution in the editor. Where a node identifies its relationship to a config node, we could add a flag (name tbd) to indicate the UI should offer a single button (either 'add' or 'edit' depending on what state it is in) rather than the select box.
The HTTP In edit dialog currently displays the default, automatically generated, config node select box if the swagger node is installed.
Unlike other uses of config nodes, I don't think it makes sense to allow the user to pick from a list of existing swagger-doc nodes. There should be a closer affinity between the nodes - it either has a swagger-doc node associated or it doesn't.
We could either hack in special handling for this case in the HTTP In node, or add a more generic solution in the editor. Where a node identifies its relationship to a config node, we could add a flag (name tbd) to indicate the UI should offer a single button (either 'add' or 'edit' depending on what state it is in) rather than the select box.