Working with new Container/Registry Implementation

[rwjblue]

@dgeb - You are the most knowledgeable on these changes in Ember itself. What changes are needed here to accommodate them?

[rwjblue]

@dgeb - We really need to make a game plan for this, as 1.11.0-beta.1 will be shipping in a couple weeks....

[dgeb]

@rwjblue ok, so the game plan we discussed in IRC is:

1. Fix up isolatedContainer to avoid deprecations for now
   1. Build a registry with Application.buildRegistry() - eliminating need for custom registrations
   2. Create a container with registry.container()
   3. Override container.register to call container._registry.register without deprecations. Consider overriding other registry calls without deprecations as well.
2. If supported, use ApplicationInstance instead of isolatedContainer, in ember-test-helpers

[rwjblue]

Downstream issue in ember-qunit: https://github.com/rwjblue/ember-qunit/issues/118

[dgeb]

The deprecation warnings are now showing up in 1.11 beta, so we need to tackle this very soon.

[rwjblue]

Yes, agreed.

[dgeb]

See #15 for a quick fix to silence the deprecation warnings. I avoided the steps above (for now) because buildRegistry has gotten more complicated, and now involves configuration of a resolver. I think all that can wait until we straighten out ApplicationInstance and expose that for testing instead of isolatedContainer.

[Turbo87]

It seems to me that this issue is no longer relevant 🤔