Dot notated namespacing

It would

Let’s say I have a simple API called:

var app = angular.module('slots', []);
app.service('slots.api', function() {
   return {
      get : function() {
         return true;
      }
   }
});

I use ng-annotate in conjunction with gulp to automatically include my dependencies for minification.

However, I have recently changed the way I namespace my modules, so If I have a service that’s specifically relating to the the slots module, I’ll prefix it with slots.

However ng-annotate doesn’t look like it supports that, is there a way to automatically do this with ng-annotate? so that the result would look something like:

app.service(['slots.api', function(api) {
    var result = api.get();
}]);

[samithaf]

@olov This seems to be a valid use case. If anyone is using ng-annotate in a large Angular App they going to hit this problem.

[deltaidea]

Perhaps, support for such cases can be achieved by adding some sort of aliasing syntax.

• The issue here is that if I have a service slots.api, that’s not a valid JS identifier and can’t be used as an argument name. You can’t write function(slots.api) { ... }.
• Just using api as the argument name isn’t gonna work either. If I want two dependencies foo.api and bar.api, which one should be referred to as api? What about the other one?

How about this?

// Source
angular.module('foo').service(function (api /*ng-from slots*/) {})

// Translates to
angular.module('foo').service(['slots.api', function (api) {}])

Or this:

// Source
angular.module('foo').service(function (/*ng-as slots.api*/ api) {})

// Translates to the same
angular.module('foo').service(['slots.api', function (api) {}])

This syntax should be optional and defined per dependency:

// Source
angular.module('foo').service(function (foo /*ng-from ns*/, bar, qux /*ng-from my*/) {})

// Translates to
angular.module('foo').service(['ns.foo', 'bar', 'my.qux', function (foo, bar, qux) {}])