👋 Embereños! This week: Meet @model for route templates 🆕, share your thoughts on Apple Music being an Ember app 🍎, contribute to Octanify allthethings 📝, a designer's & developer's story of transitioning to Ember ⚛️➡️🐹, and celebrate the 4.0 release of Ember Sinon QUnit 🎉!
Starting with Ember Octane (3.14), you can use a named argument, @model, in the route template to refer to your data from the model() hook. The Ember Octane Guides have been updated to show uses of @model.
@model was introduced to help new developers quickly learn templates. By avoiding this.model, they would not need to understand another concept—the controller—to build their first Octane app. By using a named argument, we can also reinforce the idea that @ is used to denote things that are "passed as arguments" to the template.
In a recent tweet, Senior Product Designer Lenora Porter (@lenoraporter_) shared a video to pitch the most interesting learnings about Ember to those transitioning from other tech stacks.
Lenora, who has prior experience in React, talks about useful learning resources for those starting out Ember and what makes the transition worthwhile. In addition to Convention over Configuration and integrated tooling, she highlights how a supportive community makes learning Ember very straightforward.
Be sure to check out the full video and share with your JavaScript friends!
Thanks to their work, ember-sinon-qunit v4 allows us to do a one-time setup, use the sinon object directly in our tests, and never worry about cleaning up mocks after the tests are run. To learn more about the motivation for change and the new syntax, you can check out Jordan's blog post and the addon's README file.
Wondering about something related to Ember, Ember Data, Glimmer, or addons in the Ember ecosystem, but don't know where to ask? Readers’ Questions are just for you!
Submit your own short and sweet question under bit.ly/ask-ember-core. And don’t worry, there are no silly questions, we appreciate them all - promise! 🤞