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! 🙂
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! ✨
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.
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 to do just that?
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 easily which makes laborious passing of QP data obsolete.
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 just needs to meet a set of guidelines for some common desired goals.
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.
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.