RFC #523 - Tracking for @model named argument to route templates

[locks]

RFC #0523 - Tracking for @model named argument to route templates

Champion: @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:

ember.js

• Implement @model (PR)

Ember CLI Team:

ember-cli

Ember Data Team:

ember-data

Learning Team:

guides-source

• References to this.model need to be updated
• @model might need to be explained before component arguments?
• update tutorial material
• update source code for Learning-managed Ember application
• make sure it doesn't break inspector
• include in release post

Steering Committee:

N/A

[locks]

I am marking "update source code for Learning-managed Ember application" as done despite it being worded a bit fuzzily as to exactly which applications this refers to, because we have certain hard blockers on certains applications that are being addressed and wouldn't make sense to track in the context of this RFC.

[locks]

Confirming the Ember Inspector item with the team. (cc @rwwagner90 ?)

[chancancode]

Yep this works

[locks]

Thank you!