Thank you for your response, it works like a charm.
Thank you for your response. The resolver on 'users/user-detail/:id' works very well, but 'users' does not. I think I need to remove the existing 'users' route, but I haven't been able to manage it.
{
path: 'users',
component: ReplaceableRouteContainerComponent,
data: {
requiredPolicy: 'AbpIdentity.Users',
replaceableComponent: {
key: eIdentityComponents.Users,
defaultComponent: UsersComponent,
} as ReplaceableComponents.RouteData<UsersComponent>,
},
title: "AbpIdentity::Users",
resolve: { 'hasDeclarationModule': hasDeclarationModuleResolver } //Does not work
},
{
path: 'users/user-detail/:id',
component: ReplaceableRouteContainerComponent,
data: {
requiredPolicy: 'AbpIdentity.Users',
replaceableComponent: {
key: 'Identity.UserDetailComponent',
defaultComponent: UserDetailComponent,
} as ReplaceableComponents.RouteData<UserDetailComponent>,
},
title: "AbpIdentity::Users",
resolve: { 'hasDeclarationModule': hasDeclarationModuleResolver } //Does work
},
I need a resolver for the identity/user route. I believe I need to override the IdentityRoutingModule.
I found this support question: https://abp.io/support/questions/5639/How-to-change-saastenant-route-in-angular. I tried to apply the same approach, but I couldn't manage to replace the route.
Hello, thank you for your response. I found the cause of routing problem. I also have TicketModule and nested routing does not load along with side menu.
localhost:4200/tickets-cart
works fine.
localhost:4200/tickets/cart
does not work fine.
How can I solve the problem, when there are nested routings?