fix: plugin boundary retry if plugin logic is skipped [LIBS-633] #862
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
flaminic
approved these changes
Jul 10, 2024
dhis2-bot
added a commit
that referenced
this pull request
Jul 10, 2024
## [11.6.2](v11.6.1...v11.6.2) (2024-07-10) ### Bug Fixes * plugin boundary retry if plugin logic is skipped ([#862](#862)) ([01a3160](01a3160))
|
🎉 This PR is included in version 11.6.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Part of LIBS-633
I noticed a small bug: when clicking on the "Retry" button in the plugin error boundary in the App Wrapper, if
skipPluginLogicis set ind2.config.js, the action can fail with the errorclearPluginError is not a function-- here's a fix by checking if that prop exists before executingBefore:
plugin-error-before.mov
After:
plugin-error-after.mov