-
Notifications
You must be signed in to change notification settings - Fork 2
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
Lint zeebe:TaskSchedule
Extension Elements
#86
Conversation
9e6cd15
to
eea90f0
Compare
eea90f0
to
9bf5c8c
Compare
zeebe:TaskSchedule
Extension Elements
if (!is(node, 'zeebe:PropertiesHolder')) { | ||
return; | ||
} | ||
|
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.
Could you give me a little more context to this here? Why are we removing it?
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.
We removed this type from the Zeebe model extension (cf. camunda/zeebe-bpmn-moddle#44 and bpmn-io/bpmn-js-properties-panel#861) because any element can have these extension properties. So there's no need for zeebe:PropertiesHolder
. Same in Camunda 7.
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.
Got it, thanks! Was trying to understand the relation to this PR. Will have another look at the PR
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.
LGTM
zeebe:TaskSchedule
extension elements supported by Camunda 8.2 will be validated by the engine. BothdueDate
andfollowUpDate
will be validated to be either valid FEEL expressions or valid ISO 8601 DateTime strings.zeebe:TaskSchedule
extension elements are only allowed by Camunda 8.2 and newer.Related to camunda/camunda-modeler#3484