(B) is a fine approach, I think. I'd really only create separate modules for reusable components that are not module-specific, and then only if I actually have another module to use them in, or I'm sharing them with other developers or something.
Also, there is this advice from Misko Hevery, back in 2012: http://www.youtube.com/watch?v=ZhfUv0spHCY&t=34m18s If there are indeed benefits from splitting components across modules in a single application, I would be delighted to hear what they are. -- 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/d/optout.
