Say I have a RootComponent called <app> "app" is to be just a 'dumb' shell, with html markup describing navigation (using [routerLink]), and a <router-outlet>
Another component called, say, "about", shall be loaded in the <app>'s <router-outlet> upon navigation. So far so good But I don't want to have the route described in the <app> component, but instead want to have it in the <about> component itself. This way, each component should be responsible of their own routes I use this pattern in NG1 apps successfully (each views have their own angular module, in which the config "block" described the module's route) I can't seem to replicate this idea with NG2 Suggestions? Reasons why this would be a bad idea? Is it, maybe, a feature that's not there yet but coming evantually? Thank you! O. -- 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.
