Documenting this as suggested is important especially in the case where the application RouterConfig is an aggregation of RouterConfig arrays provided by the nested tree of components within the application. Being able to see the full RouterConfig array as a single structure makes the relationship between the various components and <router-outlet> elements within the application visually clear (easy to match up full / partial paths)
-- 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.
