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

RFC #0460 - Tracking for Yieldable Named Blocks #44

Closed
3 tasks
rwjblue opened this issue Apr 26, 2019 · 7 comments
Closed
3 tasks

RFC #0460 - Tracking for Yieldable Named Blocks #44

rwjblue opened this issue Apr 26, 2019 · 7 comments
Assignees
Labels
team:ember.js ember.js team

Comments

@rwjblue
Copy link
Member

rwjblue 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

@rwjblue rwjblue added team:ember.js ember.js team needs planning:learning Needs planning by the learning team labels Apr 26, 2019
@rwjblue rwjblue self-assigned this Apr 26, 2019
@rwjblue rwjblue changed the title RFC #0000 - Tracking for Yieldable Named Blocks RFC #0460 - Tracking for Yieldable Named Blocks Apr 26, 2019
@rwjblue rwjblue added needs planning:learning Needs planning by the learning team needs planning:ember-cli Needs planning by ember-cli team needs planning:ember-data Needs planning by ember-data team needs planning:ember.js Needs planning by ember.js team needs planning:steering committee Needs planning by the steering committee and removed needs planning:learning Needs planning by the learning team needs planning:ember-cli Needs planning by ember-cli team needs planning:ember-data Needs planning by ember-data team needs planning:ember.js Needs planning by ember.js team needs planning:steering committee Needs planning by the steering committee labels Apr 30, 2019
@acorncom acorncom removed the needs planning:learning Needs planning by the learning team label Jun 6, 2019
@rwjblue
Copy link
Member Author

rwjblue commented Jul 30, 2019

A very rough idea of the work needed for upgrading in Ember can be seen in the upgrades done to Glimmer.js for the same range:

@Exelord
Copy link

Exelord commented Aug 17, 2019

Is there any rough estimation when we can expect this feature? <=3.14 or later? :)

I'm working on new addon which will use it as core functionality and I'm wondering when I could be able to release it.

@knownasilya
Copy link

knownasilya commented Oct 1, 2019

Has anyone started on this, thinking of starting this week if no one has yet.

@rwjblue
Copy link
Member Author

rwjblue commented Oct 2, 2019

Not that I know of. I think that many/most folks with time to work on OSS at the moment are pretty focused on making Octane successful. Not an excuse or anything, just mentioning that as a reason why this is simmering for a bit...

@knownasilya
Copy link

step 1: emberjs/ember.js#18454

@locks
Copy link
Contributor

locks commented Apr 11, 2020

There has been progress recently and we are looking to start documenting.
These are roughly the documentation goals:

@sandstrom
Copy link

Just wanted to say that the named blocks design is awesome! 🥇

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
team:ember.js ember.js team
Projects
None yet
Development

No branches or pull requests

6 participants