@runspired dropped a big RFC on Ember Data packages. The RFC proposes public import path changes for ember-data and moving ember-data into the @ember-data namespace.
The motivations for these changes revolve around improving the TypeScript experience, reduce bike shedding, simplify the mental model, engage more contributors, improve CI time, and more! By breaking down the single large package into smaller consumable chunks, end users can pick and choose which parts they need and do not need as well as make the ecosystem easier to navigate.
This week a set of contributions to the Ember Guides will make concepts like Ember Components, Ember Data among others much easier to understand for learners of the framework. The contributors @zachgarwood, @ppcano, @LalithaRajanala and @sduquej made sure that new concepts are introduced sufficiently and that instructions in the Ember Tutorial are as clear as possible (1, 2, 3, 4, 5, 6). Thank you so much for your contributions to the Guides! ❤️
One of the great ways to learn Ember is by building the super-rentals app by following the tutorial in the guides. One of the things you’ll learn in that tutorial is how to integrate Google Maps into an Ember application. Sadly, some changes to Google Maps meant that now you would have to provide credit card information to embed it in your app.
Thankfully, the amazing @toddjordan has provided a great fix for this. He has switched the Google Maps part out of super-rentals and replaced it with the free alternative Leaflet Mapbox.
Thanks a lot for all of the hard work on this, @toddjordan! ❤️