Hello, I ran into the same problem. To me it feels like a bug. Is there any intend to change this behaviour ? I want to use modules to isolate components, so I can easily extract them from the project when needed. But with the current implementation, I can't really tell which are the actual dependencies required for a given module.
On Friday, February 8, 2013 12:04:12 AM UTC+1, Witold Szczerba wrote: > > Hi, > today I have figured out something scary during code review. Controller in > one of my modules is declaring a dependency on a service which is not > declared in any module declared as a dependency... > > Here is a simplified case: > http://jsfiddle.net/witoldsz/9peQv/ > > Isn't it a bug? If it is a feature then what are we declaring module > dependencies for or why do we split application to modules if everything is > going to be mixed up anyway? > > Regards, > Witold Szczerba > -- 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.
