You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.
Describe the bug
With vCD 10.1, the angular container version has been upgraded to 8+ in vCD appliance. With this new version, I am encountering routing issue with my existing plugin which worked well otherwise.
Issue:
Not able to navigate using router.navigate(router.navigate([extentionPrefix, 'about'])
I have setup a router guard in my routing module to redirect certain requests based on user role,
eg
/plugin/ -> Redirect to /plugin/config // Provider view
/plugin/ -> Redirect to /plugin/overview // Tenant view
I handle this redirection through a router guard and call the router (Router) navigate API to redirect the user.
The error I see in v10.1 is, Error: Cannot match any routes. URL Segment: 'about'
Thank you to letting us know about this one. I think 10.1 dev container branch is not ready yet, at this point it's the same like 9.7 - 10.0. (My comment is not relevant if you took the branch implementation from my PR: #24)
Describe the bug
With vCD 10.1, the angular container version has been upgraded to 8+ in vCD appliance. With this new version, I am encountering routing issue with my existing plugin which worked well otherwise.
Issue:
Not able to navigate using
router.navigate(router.navigate([extentionPrefix, 'about'])
I have setup a router guard in my routing module to redirect certain requests based on user role,
eg
/plugin/ -> Redirect to /plugin/config // Provider view
/plugin/ -> Redirect to /plugin/overview // Tenant view
I handle this redirection through a router guard and call the router (Router) navigate API to redirect the user.
The error I see in v10.1 is,
Error: Cannot match any routes. URL Segment: 'about'
My routes:
const ROUTES: Routes = [ { path: "", component: SubnavComponent, children: [ { path: "", redirectTo: "status", pathMatch: "full" }, { path: "status", component: StatusComponent, canActivate: [RouterGuardService] }, { path: "about", component: AboutComponent } ] } ];
If I open the URL /plugin/about directly, it works fine.
To Reproduce
Steps to reproduce the behaviour:
Expected behavior
Since the route is valid, the redirect should have worked just fine.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: