lacides/ember-cli-fixture-loader

Keep your fixtures separate from your models

ember-cli-fixture-loader's Issues

Exclude fixtures in production

It would be great to have a setting to not include the fixtures in specific ENVs.
For exmaple if someone wants to just use his fixtures for development and testing.

What do you think about it?

Improper Formatted Package

I installed using your guide and tried creating a fixture of a model and I get the following error.

MacBook-Pro:app Animal$ ember generate fixture league
The package ember-cli-fixture-loader is not a properly formatted package, we have used a fallback lookup to resolve it at /Users/Animal/Documents/Git/App/node_modules/ember-cli-fixture-loader. This is generally caused by an addon not having a main entry point (or index.js).
The ember-cli-fixture-loader addon could not be found at /Users/Animal/Documents/Git/App/node_modules/ember-cli-fixture-loader.

I double checked to make sure that the ember-cli-fixture-loader folder was in the node-modules and it is. I'm using up to date ember & ember-data. Any ideas?

Can't find fixtures when using pods

I cant seem to get the fixture loader to load fixtures in pods.

I've created a pod called case and used ember g fixture case --pod to generate a fixture. This created the file app/case/fixture.js which a populated with one object.

When calling this.store.find('case', 1) I get the error:

Assertion Failed: Unable to find fixtures for model type app@model:case:. If you're defining your fixtures using 'Model.FIXTURES = ...'', please change it to 'Model.reopenClass({ FIXTURES: ... })'

The fixtures for models not in pods load as expected and adding fixtures manually in the model file using Model.reopenClass({ FIXTURES: [ { id: 1 } ] }); works perfectly.

Anything I am missing regarding using fixtures with pods?