Expression Node Operators

Feedback & Ideas
1

Any plans on adding distinctions for =, == and === at some point?
e.g. for Date to String comparison, String (uppercase) to String (lowercase), String to Number, and maybe in the future String to Path comparisons?

(would obviously break backwards compatibility at this point, but hence asking to consider usage of = and == before doing any porting / usage of the expression node)

Secondly, mostly for the Expression Row Filter (and a hopeful future Splitter version): any plans on supporting IN and LIKE straight away? (including string representation as present in Rule-Based nodes?)

2

Hi @fe145f9fb2a1f6b ,

No, we do not plan to distinguish between = and ==. People with different backgrounds have different expectations and especially == looks unexpected. While we generally try to have only one way to do things, this is a case with two equivalent options.

We plan to add support for collections including a function to test whether a collection contains an item or not (similar to IN).

There is a like() function available, which can be used in a case-sensitive or non case-sensitive way.

Thanks for your feedback,

nan

1 Like