Set node config values as `undefined`

General
1

So...
This might be a really simple thing I am missing...

But I am migrating a node over to typescript.
and I have a need to set a config value as undefined if its length is <1...

setting this.someConfigValue = undefined in side oneditsave if it has no length does not seem to work.
its being rendered as a 0 length string?

am I missing something?

Example:
Printing config inside the JS file -> "apiKeys_firmwareUpdateService":""

2

Hard to say without seeing the src. Is there a repo on GitHub or somewhere else?

3

Morning @Steve-Mcl
I think I have narrowed it down.

When I do this:

const runtimeNodeSettings = {
    category: 'config',
    defaults: {
        security_S0_Legacy: {
            value: undefined,
            required: false
        }
    },
    oneditsave: cleanValues
}

RED.nodes.registerType('zwavejs-runtime', runtimeNodeSettings);
function cleanValues() {
    this.security_S0_Legacy = undefined;
}

security_S0_Legacy is still being set to what's in the text box - an empty string ""

Doing this however:

const runtimeNodeSettings = {
    category: 'config',
    defaults: {
        security_S0_Legacy: {
            value: undefined,
            required: false
        }
    },
    oneditsave: cleanValues
}
RED.nodes.registerType('zwavejs-runtime', runtimeNodeSettings);

function cleanValues() {
    this.security_S0_Legacy = undefined;
    $('#node-config-input-security_S0_Legacy').remove(); /* <---- This */
}

It does take affect. I was assuming oneditsave is after the values being fetched from the inputs,
but seems to be before.

I remove the element to stop it being set to an empty string at the end of the pipeline.

I only need to do this if the string length is < 1 but above was just a demo sketch describing the "problem"

4

You might be better off disassociating the variable from the form. What I mean by this is instead of giving the element an ID of "node-input-xyz" you could ID the element "my-node-el-xyz".

In doing so, you would need to manually retrieve the value in oneditprepare and store the value in your defaults variable in oneditsave.

5

Agreed!

My current work around feels tacky :sweat_smile:

Thanks