Hi Sander, I think it depends on the use case and I also think the framework should give us the possibility so that we can decide.
But I'm curious: Do you know for sure, that this is not supported? Wishes, Manfred Am Dienstag, 22. Dezember 2015 11:21:40 UTC+1 schrieb Sander Elias: > > Hi Manfred, Martin. > > There is a good reason there is no support for this. It leads to tightly > coupled code, and the code tends to land 'far' away from where it belongs. > The easy solution is to create a service that checks the thing you need, > and then just assign that to the canActivate lifetime hooks you need it. > > 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.
