-
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
Decouple DIs from business Objects #1472
Labels
enhancement
New feature or request
Comments
marstamm
changed the title
business-objects are decoupled from di
Decouple DIs from business Objects
Jul 30, 2021
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
backlog
Queued in backlog
labels
Aug 5, 2021
marstamm
added a commit
that referenced
this issue
Aug 6, 2021
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Aug 6, 2021
marstamm
added a commit
that referenced
this issue
Aug 20, 2021
marstamm
added a commit
that referenced
this issue
Aug 25, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
In the diagram `di` is now accessed via the diagram element, not the business object. This has the benefit that elements in multiple diagrams can easily be represented. Related to #1472 BREAKING CHANGE: * Instead of referencing the `di` from the business object, reference it from the diagram element representing it.
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
In the diagram `di` is now accessed via the diagram element, not the business object. This has the benefit that elements in multiple diagrams can easily be represented. Related to #1472 BREAKING CHANGE: * Instead of referencing the `di` from the business object, reference it from the diagram element representing it.
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
In the diagram `di` is now accessed via the diagram element, not the business object. This has the benefit that elements in multiple diagrams can easily be represented. Related to #1472 BREAKING CHANGE: * Instead of referencing the `di` from the business object, reference it from the diagram element representing it.
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
nikku
pushed a commit
that referenced
this issue
Aug 27, 2021
marstamm
added a commit
that referenced
this issue
Aug 30, 2021
In the diagram `di` is now accessed via the diagram element, not the business object. This has the benefit that elements in multiple diagrams can easily be represented. Related to #1472 BREAKING CHANGE: * Instead of referencing the `di` from the business object, reference it from the diagram element representing it.
marstamm
added a commit
that referenced
this issue
Aug 30, 2021
marstamm
added a commit
that referenced
this issue
Aug 30, 2021
marstamm
added a commit
that referenced
this issue
Aug 30, 2021
nikku
pushed a commit
that referenced
this issue
Sep 3, 2021
In the diagram `di` is now accessed via the diagram element, not the business object. This has the benefit that elements in multiple diagrams can easily be represented. Related to #1472 BREAKING CHANGE: * Instead of referencing the `di` from the business object, reference it from the diagram element representing it.
nikku
pushed a commit
that referenced
this issue
Sep 3, 2021
nikku
pushed a commit
that referenced
this issue
Sep 3, 2021
nikku
pushed a commit
that referenced
this issue
Sep 3, 2021
marstamm
added a commit
that referenced
this issue
Oct 8, 2021
In the diagram `di` is now accessed via the diagram element, not the business object. This has the benefit that elements in multiple diagrams can easily be represented. Related to #1472 BREAKING CHANGE: * Instead of referencing the `di` from the business object, reference it from the diagram element representing it.
marstamm
added a commit
that referenced
this issue
Oct 8, 2021
marstamm
added a commit
that referenced
this issue
Oct 8, 2021
marstamm
added a commit
that referenced
this issue
Oct 8, 2021
barmac
added a commit
to barmac/camunda-modeler-plugin-color-picker
that referenced
this issue
Aug 29, 2022
gclaussn
added a commit
to camunda-community-hub/bpmn-driven-testing
that referenced
this issue
Feb 11, 2023
gclaussn
added a commit
to camunda-community-hub/bpmn-driven-testing
that referenced
this issue
Feb 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should we do?
Remove the 1:1 connection between business Objects and DIs
Why should we do it?
The bpmn standard allows multiple DIs (in different Diagrams) to exist for the same BPMN element. With the limitation of 1 di per BO, we prevent imports of multiple diagrams.
Therefore we should
Breaking Changes
The di is no longer accessible from the business Object. It can only be accessed through the element, such as
element.di
or through the utility functiongetDi
inlib/util/ModelUtil.js
.To access DI in a safe manner from a shape or connection use the
lib/util/ModelUtil#getDi
utility.The text was updated successfully, but these errors were encountered: