-
Notifications
You must be signed in to change notification settings - Fork 33
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
refactor!: rename values in ShapeBpmnMarkerKind
#3147
refactor!: rename values in ShapeBpmnMarkerKind
#3147
Conversation
The previous values included spaces which is not consistent with values in other enums. Use a kebab case and shorten the values. Refactor also the way markers are painted in `BaseActivityShape`: remove the use of the switch in favor of the use of a Map. This makes the implementation consistent with `EventShape`. BREAKING CHANGES: some values in `ShapeBpmnMarkerKind` have changed. Values are not supposed to be used directly, so this change should not have any impact. For applications using such values, replace the value by the of the enum, in particular for: - MULTI_INSTANCE_PARALLEL - MULTI_INSTANCE_SEQUENTIAL
🎊 PR Preview 8ad7a72 has been successfully built and deployed to https://process-analytics-bpmn-visualization-js-doc_preview-pr-3147.surge.sh 🕐 Build time: 0.01s 🤖 By surge-preview |
🎊 PR Preview 8ad7a72 has been successfully built and deployed to https://process-analytics-bpmn-visualization-js-demo_preview-pr-3147.surge.sh 🕐 Build time: 0.011s 🤖 By surge-preview |
ShapeBpmnMarkerKind
ShapeBpmnMarkerKind
Quality Gate passedIssues Measures |
The previous values related to "multi instance" included spaces which is not consistent with values in other enums.
They now follow the kebab-case convention and their values are shorter.
Refactor also the way markers are painted in
BaseActivityShape
: remove the use of the switch in favor of the use of a Map.This makes the implementation consistent with
EventShape
.BREAKING CHANGES: some values in
ShapeBpmnMarkerKind
have changed. Values are not supposed to be used directly, so this change should not have any impact. For applications using such values, use the enum directly, in particular for:Notes
Covers #3146