AngularJS Guide - Dependency Injection - Factory methods

Question

At the bottom of Angular's Dependency Injection guide, I came across this snippet about factory methods, and I'm having a hard time understanding where the "depProvider" and "depService" are being defined:

Here's the snippet:

  angular.module('myModule', []).
  config(['depProvider', function(depProvider){
    ...
  }]).
  factory('serviceId', ['depService', function(depService) {
    ...
  }]).
  directive('directiveName', ['depService', function(depService) {
    ...
  }]).
  filter('filterName', ['depService', function(depService) {
    ...
  }]).
  run(['depService', function(depService) {
    ...
  }]);

Am I correct in that 'depProvider' and 'depService' are injected into these definitions, and would have to be defined elsewhere? Or are these built-in dependencies?

Wottensprels · Accepted Answer · 2014-02-06 18:12:56Z

1

I assume that those are fictional modules that should show you how a factory (or anything else) could *dep*end on another service.

They are no built-in modules or anything.

answered Feb 6, 2014 at 18:12

Wottensprels

3,3273 gold badges31 silver badges39 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Michael Benford · Accepted Answer · 2014-02-06 18:35:13Z

1

Yes, you're right. That dependencies can be in the same module or in any module declared as a dependency (modules can have dependencies too).

For what it's worth every Angular built-in service starts with a $ so they are easily spotted (e.g. $scope, $http, $timeout etc).

edited Feb 6, 2014 at 18:35

answered Feb 6, 2014 at 18:15

Michael Benford

14.1k3 gold badges62 silver badges60 bronze badges

Collectives™ on Stack Overflow

AngularJS Guide - Dependency Injection - Factory methods

2 Answers 2

Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Related