Talofa Emberistas! 🐹 We hope to see you at EmberConf next week!
Polish up the Guides preview for Octane ⛽️, invoke nested components with angle bracket syntax 📐, an update on module unification 📝, check out the new Yieldable Named Blocks RFC 📇, an Ember Data Development Plan RFC 💾 and more!
Do you have a few minutes to read a page of the Work in Progress (WIP) of the new Octane Guides and send a PR for any kind of small fix? It's all about spelling, typos and factual accuracy in this round of copy-editing for the Octane Guides, and your help - however big or small - is greatly appreciated! 🖤 Your work will contribute to a big initiative the Learning Core team and friends have been working on for a while and which will be highlighted at EmberConf next week!
Even though angle bracket syntax is the modern and already available way of invoking components in Ember, it is still not possible to invoke all your components in your Ember app this way (yet!).
In contrast to curly invocation syntax, or classic invocation syntax, angle bracket syntax does not allow you to invoke components from nested directories, e.g. app/components/blog/post/comment.js. A new Request for Comments (RFC) aims to change exactly that. It paves a way for Ember developers to use angle bracket invocation syntax on components from all app directories - nested or not.
If you are interested in Module Unification (MU) and the plans surrounding that topic, the blog post that @tomdale wrote will tell you all about it. Tom tells the story starting with the Module Unification RFC from 2016 and how the community worked really hard to make MU work.
Unfortunately, MU will not be shipped in Octane. The implementation of MU, in for example Glimmer, showed that there are challenges in making MU work intuitively and useable. With these challenges in mind and looking at the development of Angle bracket components, there is a new path wide open. The first steps towards MU in Ember start with the SFC & Template Imports RFC to make template imports possible.
@igorT recently opened an RFC setting a medium term plan for Ember Data's development with the goals of increasing approachability, speed, stability, flexibility and shedding some legacy layers.
The RFC describes a tactical plan to refactor Ember Data's internals to isolate DS.Model to facilitate swapping it out in the future, replaceInternalModel functionality, and introduce RecordIdentity to uniquely identify records and harden system boundaries.