Accessing a FEEL expression [0] reports misleading message

[nikku]

Describe the Bug

I'm trying out the new validation for FEEL expression [0] access. Whenever I write a FEEL expression with a [0] part the editor reports "unparseable FEEL expression":

Steps to Reproduce

1. Create any FEEL expression, i.e. ServiceTask => Retries of the form = friends[0]
2. See editor indicates expression is unparseable

Expected Behavior

• The expression shows the issue, but is not marked as unparseable, because that is not correct, factually

Environment

• Host (Browser/Node version), if applicable: Chrome 128
• OS: Linux
• Library version: v5.24.0

[nikku]

I'm looking into this, and see if there is a quick fix available. As of today the properties panel always calls onError, no matter the FEEL validation returned.

https://github.com/bpmn-io/properties-panel/blob/5aa01eee0767b640c14dd153af4d0214b859d111/src/components/entries/FEEL/Feel.js#L135

[nikku]

Fixed in two ways:

• Guidance is now a warning (https://github.com/bpmn-io/feel-lint/releases/tag/v1.3.1)
• Only actual syntax errors mark the field as red (Integrate first-item FEEL validation gracefully, as a warning  properties-panel#381)