this.subject() throws error in moduleForModel if { integration: true } about ember-test-helpers

[rwjblue]

This is because modelForModel with integration: true is not running the initializers (or the setup code from isolatedContainer).

I think we should be adding all of these registrations from [inside the _setupIntegrationContainer](https://github.com/switchfly/ember-test-helpers/blob/0a514b2367c19cf6f67728629617b63c55128dfc/lib/ember-test-helpers/test-module.js#L222-L238) in addition to calling Ember.Application.buildRegistry`.

[rwjblue]

We should extract those registrations into a stand alone function, then call it from both isolatedContainer and _setupIntegrationContainer.

[mitchlloyd]

Thanks for the quick reply! For now I've got a workaround using DS._setupContainer(this.container).

[wagenet]

@rwjblue you also said this was the same as the "missing component:-text-area" stuff, right?

[rwjblue]

Yes

[nikz]

Added a failing test for this in #51

[mitchlloyd]

Does it seem reasonable that Ember and Ember Data could maintain this list of registrations?

For instance, in Ember, this minimal set of container items could be extracted from the application buildRegistry method and be exposed as a public API.

I know that is beyond the scope of this bug, but I just wanted to see if this was a decent idea.

[rwjblue]

@mitchlloyd - Both Ember Data (in the last couple versions) and Ember (since 1.0.0!) have a mechanism for populating a container with what is needed for a default setup. Unfortunately, we haven't been using them here. I submitted #49 to resolve that, and remove this super annoying hard-coding of registrations/options/etc.

[rwjblue]

Resolved and released in [email protected] and [email protected].