Skip to content
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

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

locks opened this issue Sep 2, 2019 · 0 comments


Copy link

commented Sep 2, 2019

RFC #0523 - Tracking for {{RFC Description}}

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:


  • Implement @model (PR)

Ember CLI Team:


Ember Data Team:


Learning Team:


  • 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:


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.