Wesley Workman

@xamoom-pali Sorry for the delayed response. I just saw this issue (I missed the email :( ). I suspect what's happening is that because it's an integration test (not an...

Yeap, I'm not crazy 😜 . Ember-test-helpers actually invoke ember-data's `setupContainer` initializer manually. See: [ember-test-helpers/build-registry.js](https://github.com/switchfly/ember-test-helpers/blob/master/lib/ember-test-helpers/build-registry.js#L111-L112). So unfortunately that means there isn't some alternative way for ember-data-model-fragments to make this work...

@xamoom-pali I'm going to close this issue. If you have any further questions or concerns let me know.

@ldong What kind of tests are you doing? It looks like integration, is that right? Can you please try manually invoking the initializer in your test setup as I mentioned...

So I was wondering why it's unique problem to ember-data-model-fragments. I think maybe we could actually do without the initializer if we just added those files into the app directory....

To be honest, I'm not really much of an NPM expert. I think one option would be if this addon moved the ember-data dependency from `devDependencies` to `dependencies` and that...

Actually I saw this PR come through. https://github.com/jamesarosen/ember-i18n/pull/433/files It seems very relevant here. I'll investigate this in the near future when I have time.

I believe this is actually an issue with Ember proper. Unless you're saying that there is also a problem with the fragment data outside of the ember inspector.

See: https://github.com/emberjs/ember-inspector/issues/690 > If you open Developer Tools with Ember and you go the Data - chrome tab freezes and uses a lot of resources.

Do you think you could write either a failing test or an ember-twiddle for this? I could make some time to take a look.