Null in unary-test expressions should resolve to `ValNull`
Closed this issue · 0 comments
remcowesterhoud commented
Describe the bug
A comparison using null or a non-existing variable should resolve to a ValNull
, except when it comes to comparisons. E.g.:
// Non existing less than
non-existing < 10
ValNull
// null greater than
null > 10
ValNull
For unary-test expressions one would expect the same behavior:
// Expected
null in < 10
ValNull
Instead, it will return a ValBoolean(true)
:
// Actual
null in < 10
ValBoolean(true)
Note that this is a regression introduced in #676. Before the return of these expressions would be ValBoolean(false)
!
There are tests verifying these that are ignored for now. They must be unignored when this is fixed:
Environment
- FEEL engine version: None affected yet. Only on the main branch