What should be the type of dropdown output?

I see something strange on dropdown node output :

With this simple test flow :
I used this values
(note that 1st value is a number, other are strings)

When I test each values, I receive in the debug :

I would expect to received "2" as a string and not as a numerical value.
This behavior has changed between dashboard 2.27.0 and 2.28.1.

Is there some reason to receive 2 as number while I set string in the node ? Is it the expected behavior ?

Node red 1.2.9 and nodejs v12.19.1

Welcome to the forum.

I see that in Dashboard 2.28.2 also. I think there was a fix for something in that area recently so possibly the fix corrected one thing and broke another. Since the developers have not noticed this thread so far the best thing to do is to submit an issue here so it will not get forgotten.

When reporting it export your mini-flow by selecting the nodes and select Export from the menu (or Ctrl+E) and paste it into the report. That makes it easy to test.

[Edit] I realise now that I was running the dashboard version from github master, not 2.28.2 so I have deleted that sentence.

Thanks for your feedback Colin.
I have submitted issue here:

The issue has been fixed in github master, so should be in the next release of node-red-dashboard, which should be 2.28.2. If you want to try it now you can install the latest development version by (important!) going into your .node-red folder and using
npm install node-red/node-red-dashboard
Note that the install rebuilds the dashboard code, which on something like a Pi 3 can take a very long time. Maybe an hour or more. Node red will continue to run while it installs however. Once it has installed then re-start node-red and clear the cache in your browser and refresh the page.
When the new version is released then to install it remove the development version and install the released version (which does not take a long time as it is pre-built)
npm remove node-red-dashboard
npm install node-red-dashboard
and again restart node-red and clear the browser cache.

Hello Colin
I have tested with the version 2.28.2, it is working properly (both in the test flow and in my original flow).
Thanks a lot for your very fast action.

For the record, it wasn't me that fixed it.

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