-
Notifications
You must be signed in to change notification settings - Fork 490
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
Element Template Runtime Versions #4530
Comments
I'd add "User is offered templates relevant to his context". |
Yana has done some work on missing templates that might be informative. I'll go through it and see if there's anything we need to be aware of. |
@jarekdanielak Let's ensure we keep this issue (our tracking issue) updated and relevant during the course of the implementation. 🙂 |
Updated after latest discussions. |
feat: support `engines` meta data Related to camunda/camunda-modeler#4530 Related to camunda/element-templates-json-schema#146
Config for current runtime platform and version can now be passed to elementTemplates. If template has information about supported engines, compatibility will be verified. Related to camunda/camunda-modeler#4530
Config for current runtime platform and version can now be passed to elementTemplates. If template has information about supported engines, compatibility will be verified. Related to camunda/camunda-modeler#4530
Config for current runtime platform and version can now be passed to elementTemplates. If template has information about supported engines, compatibility will be verified. Related to camunda/camunda-modeler#4530
Config for current runtime platform and version can now be passed to elementTemplates. If template has information about supported engines, compatibility will be verified. Related to camunda/camunda-modeler#4530 feat(element-templates): emit <changed> as part of <set> This allows us to safely use <set> to reflect internal changes.
Config for current runtime platform and version can now be passed to elementTemplates. If template has information about supported engines, compatibility will be verified. Related to camunda/camunda-modeler#4530 feat: emit <changed> as part of <set> This allows us to safely use <set> to reflect internal changes.
Config for current runtime platform and version can now be passed to elementTemplates. If template has information about supported engines, compatibility will be verified. Related to camunda/camunda-modeler#4530 feat: emit <changed> as part of <set> This allows us to safely use <set> to reflect internal changes.
Reopening as there are still some integration and documentation tasks to do. |
With the feature integrated in both modelers and documentation pending to be merged, I consider this closed now. |
This is a tracking issue for Element Template Runtime Versions epic.
Description
We want to detect, communicate and help users solve incompatibilities between their platform version and element template version.
We want to warn the user about the incompatibility in a non-blocking way, allowing them to fix the problem or continue with the deployment.
To do:
Follow up:
Note:
Additional documentation
The text was updated successfully, but these errors were encountered: