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.
Description
What changed?
When the formio-builder component is destroyed, call destroy on the builder instance to clean up memory
Why have you chosen this solution?
Let say you have some kind of app that navigates between forms and displays a builder to edit that form. When the app navigates to another form the angular formio-builder is destroyed but the webform from the builder is still referenced in Formio.forms. We need to make sure to call destroy on that builder instance so that a memory leak does not occure
Breaking Changes / Backwards Compatibility
N/A
Dependencies
N/A
How has this PR been tested?
Manually tested
Checklist: