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

RFC #0226 - Tracking for Named Blocks #13

Closed
kategengler opened this issue Feb 12, 2019 · 5 comments
Closed

RFC #0226 - Tracking for Named Blocks #13

kategengler opened this issue Feb 12, 2019 · 5 comments
Assignees
@wycats
Labels
team:ember.js ember.js team

Comments

@kategengler
Copy link
Member

kategengler commented Feb 12, 2019 •
edited by locks
Loading

RFC #0226 - Tracking for Named Blocks

Champion: @wycats

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").

Ember.js Team:

N/A

Ember CLI Team:

N/A

Ember Data Team:

N/A

Learning Team:

N/A

Steering Committee:

N/A
@kategengler kategengler added this to Accepted in RFC Tracking Feb 12, 2019
@kategengler kategengler added the team:ember.js ember.js team label Feb 22, 2019
@locks
Copy link
Contributor

locks commented Apr 15, 2019

Superseded by emberjs/rfcs#460.

@locks locks closed this as completed Apr 15, 2019
@kategengler kategengler removed this from Accepted in RFC Tracking May 10, 2019
@Exelord
Copy link

Exelord commented Jul 15, 2019

Is there any tracking PR for emberjs/rfcs#460 ?

@kategengler
Copy link
Member Author

@Exelord Yes, #44

@Exelord
Copy link

Exelord commented Jul 15, 2019

Thanks. Its missing the reference

@kategengler
Copy link
Member Author

It is linked from the merged RFC

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@wycats wycats

Labels
team:ember.js ember.js team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wycats @locks @kategengler @Exelord