Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid triggering Component reopen deprecation #326

Merged
merged 1 commit into from
Jun 9, 2021

Conversation

mixonic
Copy link
Member

@mixonic mixonic commented Jun 4, 2021

Ember.Component.reopen is deprecated with the id ember.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

Ember.Component.reopen is deprecated with the id ember.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.
@mixonic mixonic added the bug Something isn't working label Jun 4, 2021
mixonic added a commit to ember-cli/ember-cli-deprecation-workflow that referenced this pull request Jun 4, 2021
@mixonic mixonic merged commit c6417b7 into master Jun 9, 2021
@mixonic mixonic deleted the mixonic/no-component-deprecation branch June 9, 2021 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants