Skip to content
This repository was archived by the owner on May 13, 2022. It is now read-only.
This repository was archived by the owner on May 13, 2022. It is now read-only.

RFC #0460 - Tracking for Yieldable Named Blocks #44

@rwjblue

Description

@rwjblue

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions