waldbaer / node-red-persistent-values / 37683738202

100%

push

github

Fix value node edit dialog failing when its configuration is unknown (#37)

Issue: The value node's edit dialog broke with an uncaught error when
its configuration was missing or not deployed yet, for example right
after importing a flow.

When the backend didn't know the selected configuration, the
configuration select's change handler threw a `TypeError` on the
configuration's `name`, and the value list stayed enabled with the
deep-clone option visible. This happens for a value node imported
without its configuration, where Node-RED leaves the configuration
field without a selection, and for a configuration that isn't deployed
yet.

The handler now treats an unresolved configuration like "None": it
empties and disables the value list and hides the value tip and the
deep-clone option. The lookup already logs an error naming the
configuration ID. The value list's change event isn't fired, so Done
keeps the node's stored value reference. Selecting "None" now also
empties the value list.

The workaround described in the examples, pressing Update in the
configuration's dialog, still works and is still needed until the
backend configuration registry goes away.

Includes the OpenSpec change fix-editor-config-load-failure.

175 of 175 branches covered (100.0%)

Branch coverage included in aggregate %.

307 of 307 relevant lines covered (100.0%)

141.15 hits per line