waldbaer / node-red-persistent-values / 37689685926

100%

push

github

Fix empty value list of value nodes before the first deploy (#38)

Issue: The value list in a value node's edit dialog stayed empty until
its configuration was deployed or saved from the configuration's own
dialog. Right after importing a flow, for example one of the examples,
value nodes couldn't be set up, and configuration changes that weren't
deployed yet didn't show up. The examples carried a workaround comment
for this.

The dialog now reads the configuration directly from the editor, so the
value list offers its values before the first deploy and includes
undeployed changes. The generated name of a new configuration counts
the configurations currently in the editor, so it includes undeployed
ones and no longer counts deleted ones until the next restart. The
backend configuration registry and its internal admin endpoints
`config/get`, `config/save` and `config/delete` are removed.

The examples drop the workaround comment and are re-aligned, so that
their nodes line up and don't overlap after an import.

Includes the OpenSpec change replace-config-registry.

167 of 167 branches covered (100.0%)

Branch coverage included in aggregate %.

287 of 287 relevant lines covered (100.0%)

144.7 hits per line