Proposal to change of Mirage Setup about ember-cli-mirage HOT 4 CLOSED

Being able to have your mirage config in a separate addon within the company for sharing would be a good thing. Nice point.

Thats just importing config though, since ember-cli-mirage still looks up the mirage models, factories, etc. and discoverEmberDataModels, there are still possible embroider issues.

We may need to look at explicit imports for all those things instead of the ember magic of looking them up (would make embroider happy and statical analyzable).

This would be a good first step.

from ember-cli-mirage.

One additional advantage to note is that this approach would make it easier to load a config that exists outside of the application. We have a couple of applications that share a Mirage setup, and explicitly importing makeServer like this would make it trivial to import that config from a shared package.

from ember-cli-mirage.

As it turns out, this param is already in startMirage, its just having setupMirage pass it

from ember-cli-mirage.

I thought I was going to have to update several pieces of the start up code, as it turns out it was all there, just missing giving setupMirage the ability to pass the options to startMirage. Was so easy a fix not sure why I didnt see it earlier

from ember-cli-mirage.