RFC #0435 - Tracking for Forwarding Element Modifiers with "Splattributes"

[kategengler]

RFC #0435 - Tracking for Forwarding Element Modifiers with "Splattributes"

Champions: @rwjblue, @chancancode

---

Expand for Instructions

All teams need to consider a merged RFC to plan any required work. Each team should comment on or edit this with links to issues for the work (or a note to the effect of "No work required").

See the README for more information
See #3 for an example

Under each team, for each repo requiring work for the RFC under that team:
### [repo name](repo url)

- [ ] (issue or pr) description, (issue or pr) link

Remove Repos that do not apply, conversely, there will probably be other repos that need work and should be added.

Ember.js Team:

• Add support [RFC #435] Add feature flag and tests for forwarding modifiers with splattributes ember.js#17842
• Enable feature [FEATURE ember-glimmer-forward-modifiers-with-splattributes] enable 👌 ember.js#17901
• [BUGFIX beta] allow {{action}} modifier + component handlers, Splattributes, {{action}} modifier and component event handlers ember.js#17877
• Original tracking, Tracking Issue for RFC #435 (forwarding modifiers via splattributes) ember.js#17493

Ember CLI Team:

N/A

Ember Data Team:

N/A

Learning Team:

• review Guides for mentions of the behaviour of ...attributes
• document feature in component chapter

Steering Committee:

N/A

[cibernox]

Update:
The feature has been merged into glimmer master (glimmerjs/glimmer-vm#923) and backported into 0.38 in glimmerjs/glimmer-vm#925)

[rwjblue]

Updated description a bit, this feature is enabled by default and will be included in [email protected] barring any issues...