Skip to content Skip to sidebar Skip to footer

Angular Nested Route With Param "Cannot Match Any Routes"

Here are the 3 routes I'm working on: game/:id game/:id/pricing game/:id/history I'd like the game/:id to be the parent view, and house a for the children t

Solution 1:

After a (long) while, I was able to solve this by removing the naming for the <router-outlet>. Turns out, single child router outlets 'just work' - so naming isn't required...

However, as of writing this, I'm still unaware of how to use router outlet naming within child routes. If anyone wants to elaborate here, I'd be more than appreciative. (maybe naming only works if there's more than 1 outlet at the same level?)


Post a Comment for "Angular Nested Route With Param "Cannot Match Any Routes""