This week in Ember is figuratively overflowing with requests for comments (RFCs) and here's our attempt to wrap everything up that has been proposed this week:
First, a major RFC regarding the upgrade story from minimal to more complex applications has been opened this week and is waiting for your comments.
The proposal explains
how the current monolithic ember-source
package that Ember apps depend on today, can be split up into smaller, independent units
giving developers more flexibility to include only those dependencies that are needed in their applications. The RFC also talks about how to provide a smooth semantic versioning
strategy that developers have already become accustomed to through the well-adopted release cycle in Ember.
Other open proposals this week include the introduction of Named Args
(incl. some proposal fixes
here) for a clearer separation between component arguments and internal properties. Another RFC postulates a new flag allowing the creation of markup-only components
free from wrapper <div>
s. You might already be familiar with these semantics from the way components are rendered in Glimmer. You can read more about the motivation behind bringing these so-called “Outer HTML” semantics
into template-only Ember components in the RFC itself
(with some more fixes
Removing one of the last wisdom teeth of the Ember 1.x era 👴, another RFC proposes the introduction of a new flag allowing to unwrap the application
from its wrapper <div>
. This will allow bringing “Outer HTML” semantics to the application template as well.
Next, the open RFC for ES5 getters
(with other fixes there
) is worth checking out if you are curious what the future of computed properties
in Ember will look like.
Second to last, but not second least, an RFC is proposing to extend the link-to helper
and to make its active state available in its yield
. This will allow for more complex, route state related markup. And really last, but not least, an RFC proposing to run the model hook on all route transitions
has been opened this week, ultimately making the developer ergonomics of the link-to helper
- used in conjunction with dynamically segmented routes - more straightforward.
Although contributors this week must have already been quite busy writing all of these detailed proposals up, already half of these new RFCs have seen their first implementation merged in this week (1
Many thanks to @bekzod
for their contributions to Ember this week 🎉