-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ensure existing values are preserved #86
Conversation
I'll conduct an E2E test on this feature tomorrow, using camunda/connectors as a foundation. |
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.
The logic works well, I would slightly refactor it to make it easier to understand. I added my suggestion in a separate PR: #89
Pending: Integration test against current connector templates. I'm still trying go get these from somewhere. |
fix(cloud-element-templates): only apply conditional portion of template * ensures we properly account for default values * when we apply a conditional template, ensure we test conditions against the original template ---- Documented in https://github.com/bpmn-io/element-templates/blob/main/docs/LIFE_CYCLE.md#upgrade-behavior Related to camunda/camunda-modeler#4249
We apply conditional logic independent of whether old and new template are the same; any change (upgrade) may trigger it, the only important aspect to consider is if actual bindings changed (and hence we need to reapply.
Do not depend element transformation for dependent dropdowns test.
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.
Great, thank you!
✔️ from my side
During integration testing I found an interesting follow-up issue: camunda/camunda-modeler#4252. |
Context
This PR
Related to camunda/camunda-modeler#4249