It's not odd, because the scope chain is the underlying mechanism for angular's 
dirty checking, even if you use controllerAs.

If it's the $scope reference itself that strikes you as odd, inject $rootScope 
instead; if you're calling $apply they do the same thing anyway.

But I wouldn't be scared of injecting $scope just because you use controllerAs. 
The point of the latter is to keep your scope chain clean and encapsulate 
functionality, not to forever banish $scope from your code. You'll still need 
it for manual watches, scope events, etc. Continue to embrace $scope where it's 
useful and you get the best of both worlds.

-- 
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.

Reply via email to