We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the decision table parses input cells values as expressions. This leads to misleading syntax errors as in the screenshot below:
Pass unary tests separated by comma to the input cell.
Should be parsed as Unary Test.
Reported via https://camunda.slack.com/archives/C0693F1NFK5/p1717418704931359
Ideally, this should be configurable in the feel-editor
The text was updated successfully, but these errors were encountered:
Upstream fix pending integration: bpmn-io/feel-editor#53.
Sorry, something went wrong.
feat(decision-table): parse FEEL input cells as unary tests
8ac0e58
Closes #880
Reported again https://camunda.slack.com/archives/C0693F1NFK5/p1731061838985009
nikku
Successfully merging a pull request may close this issue.
Describe the Bug
Currently, the decision table parses input cells values as expressions. This leads to misleading syntax errors as in the screenshot below:
Steps to Reproduce
Pass unary tests separated by comma to the input cell.
Expected Behavior
Should be parsed as Unary Test.
Context
Reported via https://camunda.slack.com/archives/C0693F1NFK5/p1717418704931359
Ideally, this should be configurable in the feel-editor
The text was updated successfully, but these errors were encountered: