This week: help design the Ember skill tree 🌱, observers going async ⏱, RFC to support populating head tag ⛑️, RFC to add load hook to Route 🎣, an update on Ember Inspector 🔍, submit your EmberFest 2019 talk today 🎤, and an EmberWeekend episode featuring Luke Melia 🔈!
A new RFC has been created by @michaelrkn to get feedback on the idea of adding a load hook to the Route. The motivation for this is that the term model() can be confusing "because it implies that only one piece of data will be fetched, and it uses the term model that is more typically associated with backend development".
Feel free to read the RFC and share your thoughts in the comment section.
In an effort to remove legacy code from Ember, promote better programming practices in apps and lay the foundation for clearer code paths, a recently accepted RFC (Request for Comments) proposes an important change to the observer APIs: the addObserver, removeObserver and the observer functions shall be configurable to operate either synchronously (the way observers always used to work in Ember apps since the pre-v1.0 days) or asynchronously.
In Ember apps today, observers will be called immediately after any of the properties they are tracking have changed. Async observers as proposed in the RFC would instead be scheduled for the next runloop.
The RFC highlights how we can use the sync option (a Boolean) to make our observers asynchronous, one by one. After the community has had sufficient time to migrate their code, the RFC argues that Ember would be able to deprecate synchronous observers.
The <head> tag does more than setting the title and favicon of a page. It also plays an integral role in SEO and unfurling links. Currently, we can use the ember-cli-head addon to modify the <head> tag. 💛
In the RFC, @rwwagner90 proposed that Ember gives developers the ability to modify the tag, using a route hook or service.
Ember Inspector recently dropped support for Ember versions < 3.4. This has freed us up to remove a lot of cruft that has existed for supporting older Ember versions, and start to clean up and modernize the code. We are continuing to design the features for the future and work towards delivering the features we promised in the past.
Ember Octane is still not currently supported, but we are working closely with the framework team to get the APIs we need to map components to DOM elements and enable us to show the arguments passed to the component, and manipulate them inline. This will allow Inspector users to debug component behavior even better.
We are always looking for more people to help out with the considerable efforts required to keep Ember Inspector running, so if you would be interested in helping out, please reach out in the dev-ember-inspector channel on Discord, we would love to have you!
A few episodes back the EmberWeekend podcast featured a great interview with long-time Ember contributor and former organizer of the Ember NYC Meetup, @lukemelia. The episode covers the origin story of the NYC meetup and some detail on the origins of Ember.js itself.
Luke has transitioned out of his role as organizer of the NYC Meetup, and he will be missed, but the well-attended and organized meetup is in good hands and is now being organized by @mixonic.
Bonus topics of the episode include Luke's experience using Ember Cordova for building mobile applications and Orbit.js!