Yeoman is a very handy tool, and I’ve used its angular-generator to generate a basic structure for several new projects before. You should use it if you’d like to have it worry about all of your project’s build process (minification, uglifying, compiling SASS, etc.).
But, in my opinion the default file structure is almost negligent. If you go along with it to create your different controllers and directive you end up with something that looks like this:
app/ scripts/ controllers/ main.js foo.js bar.js directives/ baz.js lolz.js services/ haha.js
Can you say “big ball of mud”?
This is bad, since when creating new entities in your project and arranging them, you shouldn’t put them together based on what Angular component they happen to be implemented with. No, we know this already. File structures should be a tool for grouping components logically. After all, when you need to make a change in the login module, do you want to go hunting for the right files under each directory, or open the “login” directory?
I believe you should strive to a structure that looks more like this:
app/ scripts/ login/ login-page.js password-validator.js dashboard/ cool-charts.js timeline.js
Do I have to stop using the generators for controllers, directives, etc.?
I know, it’s not fun. But as far as I can tell, the generators (e.g.
yo angular:controller login) don’t support a different file structure at the moment. It it something that’s planned according to the project’s site.
But it just boils down to a relatively simple template (in case you don’t want to type the boilerplate yourself when creating a new file) and adding a line to
index.html, really not that big of a deal if it means I get proper file structure.