Avoid triggering Component reopen deprecation #326
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.
Ember.Component.reopen
is deprecated with the idember.component.reopen
to be removed in Ember 4.0. Here, use a clever invocation to avoid the Ember deprecation.Both these APIs are deprecated targeting 4.0 anyway, so this deprecation doesn't need to exist after
Component.reopen
is removed.The avoidance of the deprecation is demonstrated by a green CI suite at ember-cli/ember-cli-deprecation-workflow#125 which would fail (with an exception of an unhandled deprecation) if the reopen deprecation were still triggered.
cc @chancancode @simonihmig