We really should be appending the DOM nodes into #qunit-fixture especially for things that require running the browsers HTML parser.

Is your feature request related to a problem? Please describe.
I understand Ember Inspector is for the development and Debugging phase. And I am of the opinion that, having access to the private (by convention, underscore prefixed) fields/property is a very useful feature when hunting for problems like why a certain computed property based on other field and property have an unexpected value.

We should have a test that validates each service can actually be resolved from the container (within a scope). See #339 for motivation. It would be fantastic if this could be done via reflection and not manually adding a new test every time you register a new service. I'm thinking we would define a static member that contained all the ServiceDescriptors. Then in the test we just get this member

We are no longer using the ember slack. Bonus points for notifying a bot on Discord.

• http://hangaroundtheweb.com/2019/10/creating-runtime-assisted-codemods-using-telemetry-helpers/
• http://hangaroundtheweb.com/2020/05/setting-up-coveralls-for-your-ember-addons/
• http://medium.com/@nowims/moving-from-react-to-ember-2020-86e082477d45
• http://www.balinterdi.com/blog/built-in-input-helpers-in-ember-js-when-and-whether-they-should-be-used
• https://0xadada.

(Issue edited by @jenweber)

Whenever you generate a new route, they have {{page-title}} in them! We should update our code examples to include this new boilerplate, and we need to let devs know what to do with it.

There are several places to update. If you want to fix one or many of them, please comment with the tasks you are working on, so we don't have duplicate work. When you open a PR,