Deploy with improperly configured nodes

Core Development Feature Requests
1

When you do a deploy, even only of modified nodes, Node-red checks all flows for nodes not properly configured. Of course this is essential, a badly configured node might be accessed by a link from the current flow, or it may be a config node not visible on any flow.

Is it possible to ignore improperly configured nodes which are on a disabled tab?

For example, I have a tab with dashboard v1 nodes.
The tab is disabled and it's dashboard page(tab) is deleted but I want to retain the nodes for reference.

image
image684Ɨ413 41.8 KB

Now I'm working on an unrelated flow and a deploy brings up irrelevant warnings

image
image1104Ɨ387 28.5 KB

1 Like
2

In fact the deployment should ignore them, I'll investigate.

Ok, only works if the node is disabled - will fix that :wink:

1 Like
3

I fully fully concur with this, and would also add another related request:
Today, when I deploy, if there are unused configuration nodes I get a warning. While I can see the value in warning against accumulating garbage, sometimes I may want to have a set of configuration nodes (e.g. DB connections) of which only one is concurrently active, and would not want to get warned of unused config nodes who are disabled

1 Like
4

100% if a node or config is badly configured AND is disabled, I don't want to be bugged every time. I disabled it for a reason.

5

Agreed.

6

Thanks @GogoVega :+1:

1 Like
7

Can one disable a config node?

8

Of course, config nodes like nodes can be disabled.

9

Oh yes, back at my computer I see that you can.