chore(deps): bump bpmn-visualization from 0.34.1 to 0.35.0

[dependabot[bot]]

Bumps bpmn-visualization from 0.34.1 to 0.35.0.

Release notes

Sourced from bpmn-visualization's releases.

0.35.0

This new version introduces support for the "BPMN in color" specification and dependency changes.

Thanks to all the contributors of this release 🌈: @​tbouffard

See milestone 0.35.0 to get the list of issues covered by this release.

Highlights

Support for the BPMN in Color specification

The "BPMN in Color" specification lets you define the colors of BPMN elements during modeling. This specification is recommended for color exchange between BPMN modeling tools.

ℹ️ More details about the specification are available in the bpmn-miwg/bpmn-in-color GitHub repository.

In bpmn-visualization 0.35.0, "BPMN in Color" support is enabled with a fallback to bpmn.io-specific BPMN extensions for colors. By default, rendering of colors defined in the BPMN source is disabled. To enable "BPMN in Color" support, use the following code snippet:

const bpmnVisualization = new BpmnVisualization({
            container: 'bpmn-container',
            renderer: { ignoreBpmnColors: false }
});

Rendering of the C.1.0 diagram when the "BPMN in Color" support is enable

⏩ Want to test it live? Give a try to the following example:

• Load and navigation demo
• Example that loads diagrams from miwg-test-suite. Load A.4.1 or C.1.0 for instance.

Dependency changes

Switched from lodash to lodash-es

Previously, bpmn-visualization depended on the lodash-throttle and lodash-debounce CommonJS dependencies. They have been replaced by a single ESM dependency: lodash-es.

Using the ESM dependency allows for better tree shaking and improves interoperability with bundlers.

For example, this change eliminates the need to configure the removal of warnings issued by Angular 15 due to lodash dependencies. In Angular 15, there is a warning about using CommonJS dependencies, specifically for the lodash dependencies. However, the step to remove these warnings is no longer necessary as demonstrated in process-analytics/bpmn-visualization-examples#495.

ℹ️ For more information, see #2678.

... (truncated)

Commits

• 82bbc85 chore(release): 0.35.0
• e5d7da7 chore(release): prepare version for release
• 815554b chore(deps-dev): bump jest-html-reporter from 3.9.0 to 3.10.0 (#2714)
• 0379e4e test: prepare support for transaction sub-processes (#2713)
• d340bae feat: add support for 'BPMN in Color' (#2614)
• 48c678e fix: keep CSS classes when calling the "Update Style" API (#2709)
• 7f5ac76 feat(parser): let configure XML attribute processing (#2704)
• 0ed2ad1 chore(gha): bump slackapi/slack-github-action from 1.23.0 to 1.24.0 (#2710)
• 65a3540 feat(demo): simplify logs displaying fit and load options (#2707)
• 6c32d5a chore(deps): use the lodash-es dependency (#2678)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)