Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

path in routeConfig not available anymore #440

Open
alexandermikuta opened this issue May 17, 2018 · 0 comments
Open

path in routeConfig not available anymore #440

alexandermikuta opened this issue May 17, 2018 · 0 comments

Comments

@alexandermikuta
Copy link

alexandermikuta commented May 17, 2018

Since the upgrade to Angular 6 (currently we use 6.0.2, but Problem also exists with Router 6.0.0) the value of routeConfig.path in ActivatedRouteSnapshot is not available anymore, also it is defined in our routes. According to the latest documentation at https://angular.io/api/router/ActivatedRouteSnapshot path is still (optional) part of routeConfig. I would expect the path defined like in Angular < 6.0.0 as it is defined in the routes. I could not find a breaking-change in the release-notes. Is there maybe an issue with this path-value? It looks like it may be related to this issue: fc4c195

related part of our routes-file (Problem occurs e.g. on route products/1):

const routes: Routes = [
  { path: 'products', component: ProductsComponent, canActivate: [AuthGuardService] },
  {
    path: 'products/:productId',
    component: ProductComponent,
    canActivate: [AuthGuardService],
    children: [...]
}]
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant