-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
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
FEEL error reported switches #3845
Comments
This happens because the syntax error takes a while to come through, so it uses the error it already has. |
I think the hierarchy of |
@philippfromme So in these cases, we prioritize the linting over the syntax error. Meaning the user just gets a "not valid" feedback |
Ah that makes sense then, didn't think of that. Thanks for explaining. I vouch for this then and will follow up. |
Should fix FEEL popup editor. Should fix #3845
Should fix FEEL popup editor. Should fix #3845
Describe the bug
Using the modelers validation feature leads to different errors flashing when invalid FEEL content is entered to a field:
It looks like two different validations kick in, resulting in different error messages.
Steps to reproduce
Expected behavior
A clear, meaningful, and stable error message is shown to me as a user. At best it indicates that
FEEL
is the format of the (expected) language. If possible the editor itself establishes additional context (red caret?).Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: