refactor!: remove BpmnVisualization.getVersion
#3231
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This method was deprecated in 0.43.0 and replaced by the `getVersion` function. BREAKING CHANGES: The `BpmnVisualization.getVersion` method is now removed. Use the `getVersion` function instead.
|
♻️ PR Preview 7e28698 has been successfully destroyed since this PR has been closed.
🤖 By surge-preview |
|
♻️ PR Preview 7e28698 has been successfully destroyed since this PR has been closed.
🤖 By surge-preview |
|
csouchet
approved these changes
Dec 17, 2024
tbouffard
deleted the
refactor/2966-remove_BpmnVisualization.getVersion
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This method was deprecated in 0.43.0 and replaced by the
getVersionfunction.BREAKING CHANGES: The
BpmnVisualization.getVersionmethod is now removed. Use thegetVersionfunction instead.Notes
Closes #2966
Version 0.43.0 was released over a year ago, so the depreciation period is sufficient to remove the method.
What's more, all the examples and demonstrations in the Process Analytics organization already use the new function, so we can safely remove the old method.