You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This is a valid FEEL expression: foo == bar
However, it will always evaluate to null. That's because we are comparing variable foo to an unary test: = bar.
This will bite any FEEL novice who wrote code before as most programming languages use double or even triple = for comparisons.
Describe the solution you'd like
Warn a user when they pass a unary test to a comparison:
Require to enclose unary test in parenthesis. However, that does not solve the problem, and is cumbersome when we actually want to use an inline unary test: foo in (100, >100)
Is your feature request related to a problem? Please describe.
This is a valid FEEL expression:
foo == bar
However, it will always evaluate to
null
. That's because we are comparing variablefoo
to an unary test:= bar
.This will bite any FEEL novice who wrote code before as most programming languages use double or even triple
=
for comparisons.Describe the solution you'd like
Warn a user when they pass a unary test to a comparison:
Describe alternatives you've considered
Require to enclose unary test in parenthesis. However, that does not solve the problem, and is cumbersome when we actually want to use an inline unary test:
foo in (100, >100)
Additional context
Discovered in bpmn-io/properties-panel#394
The text was updated successfully, but these errors were encountered: