Skip to content

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions content/ember/v6/deprecate-target-action-support.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
---
title: Deprecate Target Action Support
until: 7.0.0
since: 6.8.0
---

The `actions` hash on components, controllers, and routes, along with the `send` method, is deprecated. These APIs were primarily used with the previously-deprecated `{{action}}` modifier and helper.

The modern approach is to use standard class methods decorated with the `@action` decorator, and to pass functions directly.
Copy link
Contributor

@NullVoxPopuli NullVoxPopuli Jun 23, 2025

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

Copy link
Contributor Author

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?

Copy link
Contributor

@NullVoxPopuli NullVoxPopuli Jun 23, 2025

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


### `actions` hash and `send`

**Old Pattern**

Previously, you would define actions in an `actions` hash and use `this.send('actionName')` to call them.

```javascript
// app/components/my-component.js
import Component from '@ember/component';

export default Component.extend({
actions: {
save() {
// ... saving logic
},
cancel() {
// ... cancel logic
}
},

someMethod() {
this.send('save');
}
});
```

**New Pattern**

With modern classes, you can define methods directly on the class and decorate them with `@action`. You can then call them like any other method.

```javascript
// app/components/my-component.js
import Component from '@glimmer/component';
import { action } from '@ember/object';

export default class MyComponent extends Component {
@action
save() {
// ... saving logic
}

@action
cancel() {
// ... cancel logic
}

someMethod() {
this.save();
}
}
```