-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommended Folder Structure Using EAK #625
Comments
They both work, and are both supported/recommended. the first example is the "pod layout" and the second is the more classical. Interestingly these are both enabled by default, and work together. The pod layout just takes slightly higher priority. It would seem like we are really lacking documentation on this though... so lets use this issue to track documentation updates on this topic. |
Thanks for your reply Stefan! Will both be supported in Ember-CLI ? We are looking toward the future with this in mind. Thank you! |
Yes both projects share the same resolver. Tbh if you are starting a new project just use cli it's already way more stable then eak |
Thanks !! |
Hello Ember Toolkit,
We have been looking at a sample todo application that was built using the Ember App Toolkit. It uses a slightly different folder structure than the documentation for the ember app toolkit.
The folder structure for the Todo Application looks like this:
/app/todos/controller.js
/app/todos/active/.js
/app/todos/completed/.js
/app/todos/index/*.js
However, accordingly to the documentation structure, there is the following:
/app/controllers/*
/app/models/*
/app/routes/*
/app/templates/*.hbs
Is one recommended over the other? What are the benefits of using the first style as compared to the second?
Thanks!
The text was updated successfully, but these errors were encountered: