-
Notifications
You must be signed in to change notification settings - Fork 1
RFC #0460 - Tracking for Yieldable Named Blocks #44
Comments
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: |
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. |
Has anyone started on this, thinking of starting this week if no one has yet. |
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... |
step 1: emberjs/ember.js#18454 |
There has been progress recently and we are looking to start documenting.
|
Just wanted to say that the named blocks design is awesome! 🥇 |
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
Ember CLI Team:
ember-cli
N/A
Ember Data Team:
ember-data
N/A
Learning Team:
guides-source
Steering Committee:
N/A
The text was updated successfully, but these errors were encountered: