I am trying to create a simple nested router. This sort of structure worked in the beta builds, but with the launch of the release candidate router I find myself stuck.
http://plnkr.co/edit/nn7KSJpqWuBpkxi1E6tJ
The plunkr above is a contrived version of my scenario. Despite having
@Routes([
new Route({ path: '/applications/...', component: ApplicationRouter })
])
the router doesn't appear to be recognising the non-terminal route.
Error: Uncaught (in promise): Cannot match any routes. Current segment: 'applications'. Available routes: ['/applications/...'].
In the new router /...
isn't necessary for routes that have child routes.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With