Mirage files are loaded on development environment even when ember-cli-mirage is disabled about ember-cli-mirage HOT 2 CLOSED

Given that getPosts accepts schema and request, I would say that is very much a mirage concern and suggest that you move the util from the tests directory and put a util in the mirage directory. I think would that would solve the problem.

Now for some questions. If you have mirage disabled in dev. Do you want that ALL the time. If so, I would use this environment variable https://www.ember-cli-mirage.com/docs/advanced/environment-options#excludefilesfrombuild instead of enabled. Think that would also solve your problem because then even config.js would not be included in you dev build. (although I do not know how this is going to look in an embroider world)

Given that you defined the route in the mirage config, is that a default, and in the test you are overriding that definition for that one specific for the test? If that route is used ONLY in that test, the you do not really need to define it in the routes if you are going to dynamically add it in the test.

from ember-cli-mirage.

Hi !

Given that getPosts accepts schema and request, I would say that is very much a mirage concern and suggest that you move the util from the tests directory and put a util in the mirage directory. I think would that would solve the problem.

No sure why it didn't work when I tried it, but it indeed works now 👍

Now for some questions. If you have mirage disabled in dev. Do you want that ALL the time. If so, I would use this environment variable https://www.ember-cli-mirage.com/docs/advanced/environment-options#excludefilesfrombuild instead of enabled. Think that would also solve your problem because then even config.js would not be included in you dev build. (although I do not know how this is going to look in an embroider world)

This is indeed what I was looking for because I never use mirage in dev env, and it works, thank you !

Given that you defined the route in the mirage config, is that a default, and in the test you are overriding that definition for that one specific for the test? If that route is used ONLY in that test, the you do not really need to define it in the routes if you are going to dynamically add it in the test.

Yes, I have some default route handlers defined in mirage/config.js which is used by the majority of my tests, but for some cases, I override those handlers in specific tests. So yep, I need to define route handlers in the mirage config file too.

Thank you very much for your detailed answer, I can close this issue then 🙂

from ember-cli-mirage.