When I import a flow with a Configuration node that already exists, a new configuration is added to the Configuration Nodes tab. It ends with '!!', which seems to be expected behavior based on my code review. However, the '!!' suffix remains on the configuration node even after clicking the Deploy …

hi, please provide a super simple reproducible demo. I expect there will be 2 super simple flows (perhaps even just 1 node to which this config points at). flow 1 should be the before state flow 2 should be what you import step by step instructions (i.e. did you click "replace", order of events e…

Sure, the test is simple i attached a flow that can be used as flow 1 and flow 2 using mqtt in node (since it's one of the out of the box nodes that have configuration section) Import the flow which would add a configuration node and mqtt with a debug node very simple. Deploy and refresh the page I…

Confirmed, I'm going to push a fix :wink: PS: The "!!" means that the config node has changed.

[image] GogoVega: The "!!" means that the config node has changed. I'd forgotten we did that. I did make a start on adding proper change icons to the config node sidebar, but it opened a can of worms I decided to step away from this close to 4.0....

Sorry, I did'nt understand everything :thinking: :sweat_smile: Did you want to add some sort of badge (or other) but forgot that this indication existed?

[image] GogoVega: Confirmed, I'm going to push a fix :wink: Fix the Sidebar Config is not refreshed after a deploy node-red:master ← GogoVega:fix-sidebar-config opened 06:48PM - 29 May 24 UTC…

[image] GogoVega: Did you want to add some sort of badge (or other) but forgot that this indication existed? Ultimately, the nodes should have the same blue dot as we use in the workspace. The !! change was a quick hack to do something - but there is no hint to the user what it means and is e…

This makes me think that there is also the error badge for the config node. The badge exists but node.valid is not updated.

@GogoVega yes. I mentioned in my post about the can of worms I opened. I don't know if that translates - but basically, yes, there's a bunch of internal state in the editor that we track for flow nodes that we don't track for config nodes which is needed to properly manage the change/error icons for…

Should the double exclamation mark for imported configuration disapper after deploy?

Core Development

system Closed 2 September 2024 12:09 12

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Flows stopped due to missing node types. Check logs for details General	4	3285	29 March 2019
Deploy with improperly configured nodes Feature Requests editor	9	82	18 April 2025
Deploy button enabled after no change edit of node General	6	663	10 January 2020
I've broken the Deploy button General	6	338	10 December 2020
Starting getting errors when pressing deploy, how does one debug this? General	8	374	29 July 2022

Should the double exclamation mark for imported configuration disapper after deploy?

Related topics