-
Notifications
You must be signed in to change notification settings - Fork 107
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
Support FEEL for Multiselect Values #679
Conversation
88b9b51
to
201c852
Compare
f80bdb7
to
1aafed2
Compare
201c852
to
35cdd75
Compare
35cdd75
to
d516482
Compare
d516482
to
cf043f3
Compare
cf043f3
to
7adaac8
Compare
7adaac8
to
a8a4790
Compare
This is ready for review now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me.
One comment regarding the deletion of entries when i switch the options source:
We could show a warning to the users when they have already added options and want to switch to another option source.
Right now i loose all of my entered options when doing so.
With a warning we could reduce frustration -> not sure if this is a painpoint at all - i just noticed it
// @Note(pinussilvestrus): There is an issue in the properties | ||
// panel so we have to wait a bit before showing the entry. | ||
// Cf. https://github.com/camunda/linting/blob/4f5328e2722f73ae60ae584c5f576eaec3999cb2/lib/modeler/Linting.js#L37 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have an issue to link to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, not yet. I will see that I'll create one
a8a4790
to
d93a2fa
Compare
I think this is a general pattern in our tooling, e.g. BPMN: when we switch element types, there are quite some properties that will be removed (cf. integration tests). I think the general answer to this is to ensure undo and redo is working. That's not the case in the demo, but should work in the modeler products. Let's keep an eye on that. |
Closes #673
valuesExpression
property to populate multiselect options via FEELAutoFocusSelectEntry
to focus another entry after select changeDemo: https://demo-673-values-feel--camunda-form-playground.netlify.app/