FP-3141: Changed DISABLED_VALUE constant from None to {{DISABLED_VALUE}}

[manuelnogueiramov]

FP-3141

• Changed DISABLED_VALUE constant from None to {{DISABLED_VALUE}}

I'm positive that this will affect previously set Disabled Values. They will not show as disabled in all the Flows / Node instances, but they will show as None instead. Any suggestions on how to fix this? - @diasnad @diasdm

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[diasdm]

If I understand the issue well, the user is setting the parameter default value to the value used to indicate a disabled parameter (None). To properly fix this we need an actual enabled field on the parameter, which is something that I don't see happening soon...

I've checked checked the behavior on EE 2.3.1, at least in the Node editor the parameter doesn't show as disabled, do you know how it was detected then?

[manuelnogueiramov]

If I understand the issue well, the user is setting the parameter default value to the value used to indicate a disabled parameter (None). To properly fix this we need an actual enabled field on the parameter, which is something that I don't see happening soon...

I've checked checked the behavior on EE 2.3.1, at least in the Node editor the parameter doesn't show as disabled, do you know how it was detected then?

Not 100% but I remember debating it back in the day. It was either by passing null or undefined which might be as problematic as the None was.

[pedro-cristovao]

Code seems ok