Hi folks, I am a java developer, starting to get move heavily into web/js development, and I've looking into a few different patterns for JS project structures, and now im trying to figure out how it relates to angular projects. Specifically: I am just wondering if there are any standards about whether a module should be implemented in multiple files.
Say I have a module with a controller, a directive, and a service A and a factory B. One might argue that in java terms this would be kind of like a module serving as a package, with a few different classes in it. So you might want to create some kind of naming convention and split the implementation across other files, for ex: modalService.service.myServiceA.js modalService.directive.myDirective.js ... This makes it challenging if you're using grunt paths with wildcards though, since the file order matters... I might be tempted to put it all in 1 file if its "small", but as this module gets larger and larger, it relates to having huge classes, where its common practice to split huge classes into multiple classes. What do you guys think? Thanks, Brian -- 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.
