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
Describe the bug
The FEEL engine fails to parse a nested for-loop expression:
context merge(
for entry in
for kvPair in (for kvPair in split(rawContent, "\n") return kvPair) return split(kvPair, "=")
return
context put({}, entry[1], entry[2])
)
If I wrap the nested for-loop inside parenthesis, the FEEL engine can parse the expression:
context merge(
for entry in
(for kvPair in (for kvPair in split(rawContent, "\n") return kvPair) return split(kvPair, "="))
return
context put({}, entry[1], entry[2])
)
failed to parse expression 'context merge(
for entry in
for kvPair in (for kvPair in split(rawContent, "\n") return kvPair) return split(kvPair, "=")
return
context put({}, entry[1], entry[2])
)': Expected (binaryComparison | between | instanceOf | in | "and" | "or" | end-of-input):1:9, found "merge(\n f"
Expected behavior
I can parse a nested for-loop without adding parenthesis.
Environment
FEEL engine version: 1.18.1
Affects:
Camunda Automation Platform 7: [7.x]
Zeebe broker: [0.x]
The text was updated successfully, but these errors were encountered:
Describe the bug
The FEEL engine fails to parse a nested for-loop expression:
If I wrap the nested for-loop inside parenthesis, the FEEL engine can parse the expression:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I can parse a nested for-loop without adding parenthesis.
Environment
1.18.1
The text was updated successfully, but these errors were encountered: