Sorry I strongly disagree. I do the route config already on the "app" component. I don't see "coupling" -> I see this as cross cutting concern. So I have to inject the "router logic" service into every Component and have to ask the service.
The decision should really be made by the developer. From my point of view the framework should provide the functionality. Regards Martin 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 angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
