Oh, this just hit me, so here is a small addendum to my previous post! > >> - constructor => #$onInit() ✔ >> >> No, in ng1, the controller itself is 'constructed' way before the > $onInit, $onInit will get called, once all required controllers are 'newed' > up. It is a replacement for the post/pre-link concepts. >
If you start doing this in all your controllers, you will create new problem. You don't know in what order the controller's get their call to $onInit. This means that if you need something from another required controller, you can't be sure it is already 'done'. Seems to me that defeats the whole purpose on $onInit (which is to act on something after all relevant controllers are created!). Regards Sander -- 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
