Passing current scope to an AngularJS Service


Is it correct to pass the “current” $scope to an AngularJS service?

I’m in the situation where I’ve a $service knowing it’s consumed by only one controller, and I’d like to have a reference to the controller’s scope in the $service methods themselves.

Is this philosophically correct?

Or I’d better to broadcast events to the $rootScope and then make my controller listen to them?


To let the controller know when something async happens, use Angular promises.

To provoke the $apply, you don’t need the scope, you can call $rootScope.$apply, as there is no difference calling it in a specific scope or in the root.

Regarding the variable reading, it would be better if you received parameters. But you could also read it from a scope as an object parameter, but I would go with parameter, that would make your service interface much more clearer.

Answered By – Caio Cunha

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published