You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The annotation-based generator maps boolean fields to boolean element template properties. Although boolean property type is defined in the element template schema, the Modeler doesn't support it.
We should default to Dropdown (true/false) in this case until boolean properties are supported in the modeler. We should keep the DSL for boolean type but default to a different behavior.
Why should we do it?
To avoid confusion for the template generator users.
The text was updated successfully, but these errors were encountered:
chillleader
added
the
kind:task
Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc.
label
Nov 7, 2023
@nikku As camunda/camunda-modeler#3622 is open for quite a while we discussed with the team whether you think it will be taken care of or whether we should implement this fallback behavior?
camunda/camunda-modeler#3622 is done and release, so the modeler should support this now, therefore this issue can be closed. @chillleader please take a look and close this issue if you also think it can be closed.
What should we do?
The annotation-based generator maps boolean fields to boolean element template properties. Although boolean property type is defined in the element template schema, the Modeler doesn't support it.
We should default to
Dropdown
(true/false) in this case until boolean properties are supported in the modeler. We should keep the DSL for boolean type but default to a different behavior.Why should we do it?
To avoid confusion for the template generator users.
The text was updated successfully, but these errors were encountered: