-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix: set loop characteristics in a command #1970
Conversation
d61ecae
to
1f6a25e
Compare
if (entry.active) { | ||
newLoopCharacteristics = undefined; |
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.
🙃
} | ||
|
||
// update `isSequential` property | ||
newLoopCharacteristics.set('isSequential', entry.options.isSequential); |
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.
I'm not sure if we need to copy the full loop characteristics here. As long as we properly undo or redo. What about using Modeling#updateModdleProperty
to simply change isSequential
to the target value?
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 could if there was only a single object type assigned to loopCharacteristics
. However, this can be one of two:
bpmn:MultiInstanceLoopCharacteristics
with propertyisSequential
, orbpmn:StandardLoopCharacteristics
without properties.
Both of them can have Camunda properties which need to be copied if we change the type of the object.
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.
Related to #1679
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.
Or rather #1581
1f6a25e
to
32dc7a6
Compare
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.
👍
Closes #1960