This week: submit to the Ember Camp Chicago CfP 🌭, celebration of 55 posts for #EmberJS2019 🎉, unravel the mystery of Ember testing syntax 💡, examine alternatives to the input helper 🤔, watch the Visual Regression Testing Made Easy talk video 📺, more expressive dependency injection ⬅️, and clean out unused components from your 🐹 app!
The EmberCamp Chicago CfP is open until June 30th. If you are interested in doing a talk, mini-talk, activity, workshop, or keynote, please submit soon!
Tickets are on sale now, with an Early Bird sale of $99 until July 8! If you want to receive announcements about EmberCamp, sign up on embercamp.com.
Over the last few weeks, we saw 55 blog posts, GitHub Gists, and tweets that described how Ember can continue to innovate in 2019. We thank everyone for participating, by writing a post, replying to one, and discussing it online or on podcasts. Please feel free to continue to write your #EmberJS2019 post even after the deadline. 💖
As Ember aligns with native JavaScript more each day, we get to reexamine the framework choices that we had made. For example, how should we handle events for input elements? @rwjblue and @stefanpenner met to discuss the historical context and alternatives to using the {{ opening_double_curly() }}input{{ closing_double_curly() }} helper.
@patocallaghan gave a lightning talk on “Visual Regression Testing Made Easy” at the April 2019 DublinJS Meetup. In his talk, Pat used Percy to scale visual regression testing from a manual to an automated workflow. You can catch potential CSS bugs, remove certain types of tests, and deal with large refactors and migrations. “Styles can sometimes make bad things happen.” Percy gives you confidence when you make big changes.
The recent Request for Comments (RFC), titled "Explicit Service Injection," proposes an update to the way services and other dependencies are registered, looked up and injected in Ember apps. The proposal argues that a class-based syntax for dependency injection is more explicit than the current string-based API and therefore preferable.
If you'd like to learn more about the new API design that is proposed in the RFC, be sure to read the original proposal and do not forget to join the discussion in the comments!
Finding components that aren't used in your application anymore can be tough. Due to different ways to invoke components (with curly braces or angle brackets) and the syntactical ambiguity between invoking helpers and components, it takes some time to prune your app from redundant components manually.
But now you can use the brand-new addon Ember Unused Components to clean up your codebase automatically. Use the --stats flag to get useful reports on the impact of your app optimization efforts as you go. Check it out today!
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! 🤞
