This isn't a big deal, but is a bit annoying.
I have a project / examples with ui-builder on a tab.
They are still vague to me and I am not working on them much.
I have disabled that tab.
Yet every time I try to DEPLOY I get warnings about some of the nodes on the flow not being configured correctly.
Um....
Ok, but!
That flow is DISABLED
I would have hoped that if the tab is DISABLED, then when you DEPLOY things, any problems are ignored.
Just mentioning.
But to me, it would be nicer if that is/was the case.
1 Like
Hi @Trying_to_learn
Probably one for @TotallyInformation to provide further info on.
But actually this is Node Red behaviour, not directly ui-builder its self.
If a Node becomes invalid (due to other dependent Nodes being disabled for instance) - even on the same disabled tab
I think Node RED STILL errors out, despite the tab being disabled.
As an example, I just dragged an MQTT Node on to a tab (I didn't configured it), deployed = Error (to be expected), then disabled its tab, and Node RED still complains, despite many deploys after
But yes, I agree - disabled tabs, should not be subject to error warnings
1 Like
If it happens on other nodes - a simple one to check would be the function node - then, as Marcus say's, that is a Node-RED "feature" rather than a uibuilder one.
Should be easy enough to get rid of any uibuilder errors though, there aren't that many things that would cause a uibuilder node to return an error.
Sorry for not putting it under ui-builder
