http://trochette.github.io/Angular-Design-Patterns-Best-Practices/#/intro
2013/12/20 Sander Elias <[email protected]> > Hi Biloki, > > That is just a matter of taste. Some go as far as making a module out of > every source file. For myself I like to create modules for function groups. > so I have an utility module, there goes all the stuff that's generic, and > not specific to the application. Also an app-util module (on somewhat > larger apps) > Also I like to group things that have logic boundaries into their own > module. For instance. if you have an Sales app, there is a part that > handles the maintaining of the articles, and a part that handles customers, > and so on. > On the other hand, If you create a todo-app, making many modules isn't > really making things easier. > > Regards > Sander > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/groups/opt_out. > -- Atenciosamente Edmilson Lani -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
