IMO you have stumbled into the reason $scope is being replaced. $scope is a grab bag of functionality that should have been allocated to different components.
It serves as the binding context (now the responsibility of controller in controllerAs), a digest service, a message broker, and i-forget-what-else. In 2.0, these will (or should) stand on their own. Why not get ahead of the game? You can roll your own services around these distinct responsibilities and then inject where needed. If you need it in your controller, inject the digestService as you would a data service or whatever. Or you could take the hint from the $http implementation and perform the apply there, in the callback from your async operation. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
