Hi Keldar, For purity and maintainability it should indeed. Imagine yourself reusing the module app.hub in another project, so you copy the corresponding js files, and your done. But now suddenly it's not working anymore. After hours of debugging you find out, that it's missing it's dependency......
However, in angular 1.x there is no technical reason to do this. The current module system and injector keeps a flat list. That means that all dependencies are in 1 big long list, and the injector will always find what it needs in there. It's also a big downside, as this makes naming collisions a real PITA. (for example, if you have 2 modules that have an 'list' and a 'edit' directive, you end up with 1 of them. And it seems random which one. 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/d/optout.
