I can use a unary-test as a list filter

[mdouaihy]

The FEEL expression [1, 2, 3][>1] is expected to returns [2, 3]. Instead, it's returning []

The issue can be observed using the Playground running version 1.19.1 of the engine
https://camunda.github.io/feel-scala/docs/playground/?expression-type=expression

For information, the playground is reporting the below warnings

[NO_VARIABLE_FOUND] No input value found.
[NOT_COMPARABLE] Can't compare 'null' with '1'
[NO_VARIABLE_FOUND] No input value found.
[NOT_COMPARABLE] Can't compare 'null' with '1'
[NO_VARIABLE_FOUND] No input value found.
[NOT_COMPARABLE] Can't compare 'null' with '1'
[NO_VARIABLE_FOUND] No input value found.
[NOT_COMPARABLE] Can't compare 'null' with '1'

[mdouaihy]

According to the document, https://www.omg.org/spec/DMN/1.5/PDF

• we have the grammar rule 50. filter expression = expression , "[" , expression , "]" ; in the section 10.3.1.2 Grammar rules
• and we have an The expression in square brackets can reference a list element using the name item, in the section 10.3.2.5 Lists and filters

Other implementations support the synthax [1, 2, 3][>1].

[saig0]

@mdouaihy thank you for reporting. 👍 I agree that the grammar allows a unary-test in the list filter expression. However, I don't see that this case is mentioned explicitly in the specification.

Do you see a reference for the evaluation in the specification?
Do you see a related test case in the DMN TCK?

---

The issue is related to camunda/camunda#27458.

The FEEL JS engine evaluates the expression as expected: FEEL JS Playground