Set (number) value to NaN in change / inject node

I used to do the following to create a NaN :

I'm pretty sure this worked fine - until recently.
Now (post 3.1) the typedInput field gets the red error indicating border & the node gets flagged with the red issue triangle.

Is this the intended / preferred way to create a NaN?
If yes, would you accept a PR to re-enable this functionality?

I think it still works & it is just a visual thing - did you deploy and test?

While you are at it, you might want to fix up binary 0b0101, octal 0o17 and hexadecimal input 0x2b1c :stuck_out_tongue:

I noticed this ↑ recently and haven't yet raised an issue! (naughty me)

PR is placed - including fixes for binary, octal & hex.


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