-
Notifications
You must be signed in to change notification settings - Fork 488
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
Form Editor crashes when FEEL expression is created in the File Picker form element #4644
Comments
cc @camunda/hto |
I'll check this |
@GeethaParthasarathy I can't reproduce it. Did I do something wrong? Could check if the steps are correct? 2024-10-29.18-15-26.mp4 |
38 tasks
Hey @vsgoulart I guess there is a missed step this issue happens when there is an error in your Feel expression and then even if you rectify it the form editor is broken Screen.Recording.2024-10-30.at.09.14.39.mov |
This was referenced Oct 30, 2024
fix: prevent form editor from breaking on invalid expression on filepicker prop
bpmn-io/form-js#1311
Merged
@GeethaParthasarathy Here's the fix: #4647 |
Closed via #4647. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When we create a FEEL expression in the
supported file formats field
of the File Picker form element, the current form editor crashes such that it affects the subsequently created forms as wellSteps to reproduce
-> Feel pop up editor does not open up
-> Form editor properties panel is frozen
->subsequently opened up forms are all affected
Screen.Recording.2024-10-29.at.14.39.49.mov
Expected behavior
Adding an unparsable FEEL expression to the form field should not break the form editor
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: