Angular 2 个嵌套路由解析执行
Angular 2 nested routes resolve execution
例如,如果我有以下路线组织:
const appRoutes: Routes = [
{
path: "",
component: AppComponent,
resolve: {
app: AppResolver
},
children: [
{
path: "",
component: NestedComponent,
resolve: {
subscribers: NestedResolver
}
}
]
}
];
和以下解析器:
export class AppResolver implements Resolve<any> {
constructor(private appService: AppService) {}
resolve(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Observable<any> {
return this.appService.getAppData();
}
}
export class NestedResolver implements Resolve<any> {
constructor(private nestedService: NestedService) {}
resolve(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Observable<any> {
console.log(route.parent.data); //when this is executed route.parent.data is empty :(
return this.nestedService.getNestedData();
}
}
应用引导后,NestedResolver 和 AppResolver 将首先执行并并行发出请求。
我们可以更改代码并实现 NestedResolver 等待 AppResolver 解析并访问 AppResolver 解析的数据吗?
Angular 2 RC6, Angular 路由器 3.0.0-rc.2
我知道这个问题已经很老了,但以防有人偶然发现它(比如我)。
这是一个已知错误,现已修复。只需将您的路由器版本更新到更高或等于 2.1.0 的版本,您就可以开始使用了。供参考这里是相关的 issue on github and the associated fix
例如,如果我有以下路线组织:
const appRoutes: Routes = [
{
path: "",
component: AppComponent,
resolve: {
app: AppResolver
},
children: [
{
path: "",
component: NestedComponent,
resolve: {
subscribers: NestedResolver
}
}
]
}
];
和以下解析器:
export class AppResolver implements Resolve<any> {
constructor(private appService: AppService) {}
resolve(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Observable<any> {
return this.appService.getAppData();
}
}
export class NestedResolver implements Resolve<any> {
constructor(private nestedService: NestedService) {}
resolve(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): Observable<any> {
console.log(route.parent.data); //when this is executed route.parent.data is empty :(
return this.nestedService.getNestedData();
}
}
应用引导后,NestedResolver 和 AppResolver 将首先执行并并行发出请求。
我们可以更改代码并实现 NestedResolver 等待 AppResolver 解析并访问 AppResolver 解析的数据吗?
Angular 2 RC6, Angular 路由器 3.0.0-rc.2
我知道这个问题已经很老了,但以防有人偶然发现它(比如我)。
这是一个已知错误,现已修复。只需将您的路由器版本更新到更高或等于 2.1.0 的版本,您就可以开始使用了。供参考这里是相关的 issue on github and the associated fix