Rationale for couple URL and Route nesting?

I understand that when nesting routes in the router map instantiates each route down to the leaf, and establishes a bubble graph for event handling. However it seems odd to me that this is coupled to the URL’s required to reach those routes.

I may want to use root-level vanity URL’s, or nest them in some sort of conceptual manner–that really has nothing to do with the way I’m architecting my outlets and event handling.

Can someone explain the reasoning behind tying these together?

I was thinking the use of a leading slash in a path declaration could control whether the route was appended to or not.

1 Like

The parent route needs to know which model to use. Perhaps your parent route doesn’t need any information from the url to establish the model? In this case perhaps you could specify the path for the parent route as “/” or “” (I haven’t tried…).