emberjs

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 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.

Post all of our awesome refactoring, the visualizer and CSS debugger are largely broken. I figure this is a good time to revisit them and want to lay out a couple of things we should list as common traps.

Original Implementation Issue: html-next/smoke-and-mirrors#59
Original Implementation: https://github.com/runspired/smoke-and-mirrors/blob/feat/virtualizati

In the Native Classes In-Depth part of the guides it says:

Ember provides a number of decorators, such as the @tracked decorator, that will be described in greater detail later on in the guides.

but it's not obvious to me where "later on in the guides" is because this is