The Ember Times - Issue No. 66

Sep 28, 2018 – By Bill Heaton, Chris Ng, Ryan Mark, Preston Sego, Amy Lam, Kenneth Larsen, Jesse Jordan, Alon Bukai

Emberistas سلام! 🐹

Don't miss brand-new 🔥 RFCs for collocated addon tests and Router served query params this week! We also have news from Ember CLI Deprecation Workflow and a Lost & Found 🕵🏾‍ from the Ember API Docs for you, as well as a Thank You note for the most amazing Issue Triaging Experts! 🙂

The Addon Test Is Right Where It Belongs ❤️

Spending too much time looking for the test files of your in-repo addon? Feeling too exhausted to maintain a large test suite in which addon and host app test cases are meshed together? It doesn't have to be this way.

Read more about how collocated in-repo test files are able to make your developer life easier in this shiny, new Request for Comments (RFC). And as always, be sure to leave your questions or ❤️ emojis right below the RFC's pull request description! ✨

ember-cli-deprecation-workflow 1.0.0 Release 🎉

This week, @rwjblue (with help from @mixonic, @atsao, and @gaurav0) released 1.0.0 of ember-cli-deprecation-workflow!

ember-cli-deprecation-workflow is an addon geared towards making Ember upgrades easier by allowing you to work through deprecations without massive console noise from Ember 1.x and 2.x deprecations.

It silences the console.log noise or "deprecation spew" via configuration so that only unhandled deprecations will be displayed in your console. And now that the spew has settled down, you can process one deprecation at a time while ensuring that no new deprecations are introduced.

Check it out on the GitHub repo!

Ever had the need to read query params (QPs) off a Controller and pass it down to a component to change its UI state depending on the QP value?

Ever had a hard time passing down QP values through layers and layers of components?

It doesn't have to be this way. Read this new RFC about exposing QPs as a computed property on the RouterService. It proposes that this Service can then be injected into components, which makes laborious passing of QP data obsolete.

As always, leave your comments and appreciation below the original proposal as long as it's still under discussion!

The Missing Docs Has Returned 📃

There has been some documentation missing from the Ember API docs from the release of 3.3 to 3.4. @Gaurav0 has done some great detective work 🕵 and fixed these issues which means that the missing documentation is now back.

Going forward the plan is to provide better testing for cases like this so you always have access to the documentation you need.

Project Structure for Single Page Apps 📂

Inspired by Module Unification, @NullVoxPopuli has written an article on general project structure for single page apps. In the article he explains how structure is not specific to Ember, React, Vue, or anything else, but needs to meet a set of guidelines for some common desired goals.

Read it here: A general and flexible file structure that works for all projects in any ecosystem

Issue Triage 🕵️

This week we had 5 volunteers helping 🚑 triage old issues that were inactive, we closed 9 and labelled 31 of 50 from last week that need a submitter response 🙀. Those 31 may be closed in the next week or two. Together, we addressed 17 issues that were inactive (and are still open 📂). We are beginning to establish a cadence again of a team addressing issue triage 🛠️ on Friday mornings.

Thanks for your triage contributions over the past two weeks 🙏… @yininge, @ryanlabouve, @yohanmishkin, @esbanarango, @hakilebara, and @pixelhandler.

The @emberjs/issues-team objective is to increase signal-to-noise ratio of issues and 🐛 bugs so that the core team (and contributors) can take action to resolve bugs, and spend less effort sorting the issues queue. Currently there are about 67 open bugs, of those 25 had a reproduction (e.g. using ember-twiddle.com), and one with a pull request - total count about 270. Our aim is to get down to 150 in the next couple months. If you'd like to help see the #issue-triage room in the community Discord chat.

Contributors' Corner 👏

This week we'd like to thank @rwjblue, @pzuraq, @chancancode, @Gaurav0, @simonihmig, @chadhietala, @bekzod, @iezer, @chrisrng, @jessica-jordan, @pixelhandler, @amyrlam, @tylerturdenpants, @acorncom, @runspired, @jrjohnson, @tmquinn, @BryanCrotaz, @mfeckie, @bmac, @Turbo87, @SparshithNR, @dcyriller, @gandalfar, @CodingItWrong, @ppcano, @hybridmuse for their contributions to Ember and related repositories! 💖

Got a Question? Ask Readers' Questions! 🤓

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! 🤞

#embertimes 📰

Want to write for the Ember Times? Have a suggestion for next week's issue? Join us at #support-ember-times on the Ember Community Discord or ping us @embertimes on Twitter.

Keep on top of what's been going on in Emberland this week by subscribing to our e-mail newsletter! You can also find our posts on the Ember blog.

That's another wrap! ✨

Be kind,

Bill Heaton, Chris Ng, Ryan Mark, L. Preston Sego III, Amy Lam, Kenneth Larsen, Jessica Jordan, Alon Bukai and the Learning Team