Subdirectories are not supported
See original GitHub issueWhen running:
ember g mirage-model foo/bar
The following error occurs when trying to access the route:
Assertion Failed: Subdirectories under foo are not supported
A related question:
How would you see Pods structure working with ember-cli-mirage?
Thanks!
Issue Analytics
- State:
- Created 8 years ago
- Comments:5
Top Results From Across the Web
Subdirectories are not supported · Issue #540 - GitHub
When running: ember g mirage-model foo/bar. The following error occurs when trying to access the route: Assertion Failed: Subdirectories ...
Read more >GCC warning: This configuration is not supported in the ...
GCC warning: This configuration is not supported in the following subdirectories. What does it means? Ask Question. Asked 2 years, 10 months ago....
Read more >Subdirectories are not supported for AMD modules?
Hi! I am currently developing a question type plugin that relies heavily on JavaScript AMD modules. I have a problem where i need...
Read more >Subdirectory Sites not working | WordPress.org
The site uses subdirectories. Today I wanted to add a new subsite but the upon clicking “Add Site” I'm only able to enter...
Read more >Git not pushing all subfolders or subdirectories - Stack Overflow
I have completed my project and I am pushing it to Github but the src folder which contains all my main code is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Filing under the “Subdirectory support” card on the Roadmap project.
I see. We should definitely support nested resources. I’m focused on other 0.2.0 issues at the moment, so if anyone else wants to spearhead this, I would start by making an app with nested resources, and taking a look at options.models in the Server constructor, as well as what ends up in
schema._registry
after all the models are registered.