mhevery/angular.js — comment on commit b49c6fc9646024a5e0159f9deafb0fde89dad837
File: src/service/scope.js line 42
By IgorMinar:

the more I'm thinking about this the more I'm sure that this kind of naming scheme is a mistake. There are several issues:

- angular.module.NG.foo is too verbose and doesn't reflect the reality (there is no object present at window.angular.module.NG.$rootScope)
- making Scope look like a property of angular.module.NG.$rootScope is just adding to the confusion

So here is my proposal:

- use `@name angular.foo` only for stuff that is expose globally via the angular namespace
- use `@name ng.$rootScope` for services
- use `@name angular.types.Scope` or `@name ng.types.Scope` or `@name angular.Scope` or `@name ng.Scope` for types
- use `@name ng.$filter.linky` for filters