-
Notifications
You must be signed in to change notification settings - Fork 29
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
Deprecate this.element
and this.args
on class-based modifiers
#221
Merged
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
rwjblue
requested changes
Mar 23, 2022
chriskrycho
force-pushed
the
deprecate-element-field
branch
from
March 23, 2022 23:06
06fe0c5
to
f94ff29
Compare
For the sake of keeping merges clean and easy, this is now based on #220 and should land right after it does. |
rwjblue
reviewed
Mar 24, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs a rebase now?
The introduction of the `modify` hook on class-based modifiers allows users to use the `element` and both `positional` and `named` arguments directly, as arguments to `modify`, rather than having them as the class properties `this.element` and `this.args` (see #217). Accordingly, deprecate access to both `this.element` and `this.args`. (Users who want to stash the `element` on their modifier class can continue to do so directly, by assigning it from the `modify` call.)
chriskrycho
force-pushed
the
deprecate-element-field
branch
from
March 24, 2022 21:45
f94ff29
to
5dafa28
Compare
rwjblue
requested changes
Mar 24, 2022
rwjblue
approved these changes
Mar 24, 2022
evoactivity
added a commit
to evoactivity/ember-autoresize-modifier
that referenced
this pull request
Oct 12, 2022
Fixes deprecation warnings ember-modifier/ember-modifier#217 ember-modifier/ember-modifier#221
jelhan
pushed a commit
to jelhan/ember-autoresize-modifier
that referenced
this pull request
Oct 15, 2022
* Move to modify hook Fixes deprecation warnings ember-modifier/ember-modifier#217 ember-modifier/ember-modifier#221
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.
The introduction of the
modify
hook on class-based modifiers allows users to use theelement
and bothpositional
andnamed
arguments directly, as arguments tomodify
, rather than having them as the class propertiesthis.element
andthis.args
(see #217). Accordingly, deprecate access to boththis.element
andthis.args
.(Users who want to stash the
element
on their modifier class can continue to do so directly, by assigning it from themodify
call.)