Sign up ×
Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute:

Is possible to inject a controller into another controller that is apart of the same module?

example:

var app = angular.module('myAppModule', [])
.controller('controllerOne', ['$scope'. function($scope){
  $scope.helloWorld = function(){
    return 'Hello World';
  }
}])
.controller('controllerTwo', ['$scope', 'controllerOne', function($scope, controllerOne){
  console.log(controllerOne.helloWorld());
}])

I keep getting unknown provider on controllerOne. I don't see that how that's possible since they coexist in the same module. Any help would be much appreciated.

share|improve this question
    
possible duplicate of Can one controller call another? – Artem Petrosian Apr 28 '15 at 18:09
    
In my issue, my controllers are located in the same module and written in purely angularjs format. The post you provided wasn't, I'm a amateur and didn't really understand anything in the other post. Thanks for you suggestion though :) – Joseph Freeman Apr 28 '15 at 18:17
    
Thanks for all suggestions!!! You all are right, i'll be moving the shared logic into a factory, it's just easier and less of a headache lol. – Joseph Freeman Apr 28 '15 at 18:58
up vote 4 down vote accepted

You need to use $controller dependency by using that you can inject one controller to another

.controller('controllerTwo', ['$scope', '$controller', function($scope, $controller){
  $controller('controllerOne', {$scope: $scope})
  //inside scope you the controllerOne scope will available
}]);

But do prefer service/factory to share data

share|improve this answer
    
This is a great solution but how is this not as good as using a service/factory to share data? What if I just want to use a function in controllerOne ? Can't I use $controller for that? – gerl Apr 28 '15 at 20:52

Move your logic into a "service" (either a factory/service/provider). I personally prefer factories, I just like controlling my own object instead of using this or anything like that with the other options.

Using a service, you give yourself the ability to abstract business logic from your controllers, and make that logic -- reusable -- !

var app = angular.module('myAppModule', [])

// typically people use the word Service at the end of the name 
// even if it's a factory (it's all the same thing really...

.factory('sharedService', function () {

    var methods = {};

    methods.helloWorld = function () {
        return 'Hello World!';
    };

    // whatever methods/properties you have within this methods object
    // will be available to be called anywhere sharedService is injected.

    return methods;
})

Notice sharedService is injected

.controller('ControllerOne', ['$scope', 'sharedService', function($scope, sharedService) {
    $scope.helloWorld = sharedService.helloWorld();
}])

// Notice sharedService is injected here as well
.controller('ControllerTwo', ['$scope', 'sharedService', function($scope, sharedService){

    // Now we can access it here too!
    console.log( sharedService.helloWorld() );
}]);

Side note : Controllers should be capitalized to show their significance!

The power of services :)

share|improve this answer

If the a controllerTwo needs to call the same function as controllerOne, you may want to create a service to handle it. Angular Services - they are accessible throughout your program through dependency injection.

var app = angular.module('myAppModule', [])
.controller('controllerOne', ['$scope', 'Hello', function($scope, Hello){
   console.log(Hello.helloWorld() + ' controller one');
}])
.controller('controllerTwo', ['$scope', 'Hello', function($scope, Hello){
   console.log(Hello.helloWorld() + ' controller two');
}])
.factory('Hello', [function() {
   var data = {
      'helloWorld': function() {
          return 'Hello World';
       }
   }

   return data;
}]);

Hope this helps!

share|improve this answer

You cannot inject controllers in another controllers,only serviceProviers are injectable.That's the reason you are getting error as unkown provider in controller one.

Use Services instead and inject them in controllers,if there is some come functionality to be shared among controllers.Services are the best way to share data in between controllers.

You can declare a variable or function or say object on $rootScope, it's exists in your whole application.

Angular: Share data between controllers

share|improve this answer
    
using $rootScope is considered as bad pattern in angularjs – Pankaj Parkar Apr 28 '15 at 19:43
    
Yes, it is a bad practice to use $rootScope,i mentioned it as it is the one of the options to be used. – Ritesh Apr 28 '15 at 19:47
    
You should never use $rootScope , that is why I'm saying that you $rootScope suggestion not appropriate – Pankaj Parkar Apr 28 '15 at 19:49

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.