DropDown node payload null instead of 0

[A380Coding]

Current Behavior

Using Dropdown Node with one Option set to 0 there is an issue. When selecting this Option in dashboard, the payload is null instead of 0

This only happens to the value 0. If the value is changed to some other value, the returned payload is correct.

Expected Behavior

When selecting Option with value 0 the payload should be 0 instead of null

Steps To Reproduce

Create Dropdown with 2 options. First option set to value 0 second option set to value 1.
Connect a debug node to the output of dopdown to show payload.
Select the options back and forth and check the debug output. The debut output showas paylod null or payload 1. But it should be payload 0 or payload 1.

Environment

• Dashboard version: 1.22.0
• Node-RED version: 4.08
• Node.js version:
• npm version:
• Platform/OS: Win10
• Browser: Firefox latest

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[A380Coding]

Additionally, if you change the selection and change it back to 0, then change to another page, go back to the page with the drop down. Now the label is within the dropdown list.

[bartbutenaers]

Hi @A380Coding,

Had a quick view at the code, and indeed I would expect the dropdown would behave like you describe. Because that if(this.value) should be false (instead of true) for the following values:

But instead it seems to work fine for some reason:

If you see what I am doing different from you, please let me know.
Now I am off to the daily job...

[A380Coding]

I'm just using numbers, not a mix of int, bool, string

[bartbutenaers]

Did a quick test during my lunch break.
First I couldn't reproduce it, but I assume you have deactivated the "Allow search" feature

That is why it is always very helpful to share a simple flow here, so others can reproduce the problem easily
Will fix it tonight.

[A380Coding]

It is deactivated yes. Next time I will export the sample. It seemed to be easy to replicate but I understand it wasn't

[bartbutenaers]

@A380Coding
Here you go...