[BUGFIX lts] Fix double container destroy #15207
Merged
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 code on the Engine Instance is not needed as it includes the
ContainerProxyMixin
, which already takes care of destroying thecontainer.
This duplicated destroy step was causing ember-cp-validations to
attempt to destroy validators twice. This destroy process tries to
nullify some property with
o.set(‘model’, null)
on an object that isalready destroyed.