-
-
Notifications
You must be signed in to change notification settings - Fork 70
Add Target Action Support deprecation guide #1410
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ember-deprecations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
||
The `actions` hash on components, controllers, and routes, along with the `send` method, is deprecated. These APIs were primarily used with the now-deprecated `{{action}}` modifier and helper. | ||
|
||
The modern approach is to use standard class methods decorated with the `@action` decorator, and to pass functions directly. |
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.
speaking of @action
-- do we ever update deprecation guides? the recommendation will change once we actually get plain methods working for real
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.
Wouldn't we just deprecate @action
at that point?
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.
we could -- tho that would be hugely disruptive across the ecosystem, so I think I'd want to wait a smidge.
There was huge resistance to deprecating @action
here: emberjs/rfcs#1045 (which the RFC wasn't even proposing)
maybe that'll change once the alternative ships
Co-authored-by: NullVoxPopuli <[email protected]>
RFC: emberjs/rfcs#1041