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 #0460 - Tracking for Yieldable Named Blocks #44

Open
rwjblue opened this issue Apr 26, 2019 · 0 comments

Comments

2 participants
@rwjblue
Copy link
Member

commented Apr 26, 2019

RFC #0460 - Tracking for Yieldable Named Blocks

Champion: @wycats @rwjblue


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

  • Upgrade the various glimmer-vm projects in Ember to latest.
  • Flesh out API documentation (determine correct/best location) and coordinate with learning team

Ember CLI Team:

ember-cli

N/A

Ember Data Team:

ember-data

N/A

Learning Team:

guides-source

  • Add segment to guides-source explaining passing and using named blocks

Steering Committee:

N/A

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