Pass parameter into route guard

Instead of using forRole(), you can do this:

{    path: 'super-user-stuff',    component: SuperUserStuffComponent,   canActivate: RoleGuard,   data: {roles: ['SuperAdmin', ...]}}

and use this in your RoleGuard

canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot)    : Observable<boolean> | Promise<boolean> | boolean  {    let roles = route.data.roles as Array<string>;    ...}

Here's my take on this and a possible solution for the missing provider issue.

In my case, we have a guard that takes a permission or list of permissions as parameter, but it's the same thing has having a role.

We have a class for dealing with auth guards with or without permission:

@Injectable()export class AuthGuardService implements CanActivate {    checkUserLoggedIn() { ... }

This deals with checking user active session, etc.

It also contains a method used to obtain a custom permission guard, which is actually depending on the AuthGuardService itself

static forPermissions(permissions: string | string[]) {    @Injectable()    class AuthGuardServiceWithPermissions {      constructor(private authGuardService: AuthGuardService) { } // uses the parent class instance actually, but could in theory take any other deps      canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {        // checks typical activation (auth) + custom permissions        return this.authGuardService.canActivate(route, state) && this.checkPermissions();      }      checkPermissions() {        const user = ... // get the current user        // checks the given permissions with the current user         return user.hasPermissions(permissions);      }    }    AuthGuardService.guards.push(AuthGuardServiceWithPermissions);    return AuthGuardServiceWithPermissions;  }

This allows us to use the method to register some custom guards based on permissions parameter in our routing module:

....{ path: 'something',   component: SomeComponent,   canActivate: [ AuthGuardService.forPermissions('permission1', 'permission2') ] },

The interesting part of forPermission is AuthGuardService.guards.push - this basically makes sure that any time forPermissions is called to obtain a custom guard class it will also store it in this array. This is also static on the main class:

public static guards = [ ]; 

Then we can use this array to register all guards - this is ok as long as we make sure that by the time the app module registers these providers, the routes had been defined and all the guard classes had been created (e.g. check import order and keep these providers as low as possible in the list - having a routing module helps):

providers: [    // ...    AuthGuardService,    ...AuthGuardService.guards,]

Hope this helps.

Another option combination of approach with data and factory function:

export function canActivateForRoles(roles: Role[]) {  return {data: {roles}, canActivate: [RoleGuard]}}export class RoleGuard implements CanActivate {  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot)      : Observable<boolean> | Promise<boolean> | boolean  {        const roles = route.data.roles as Role[];    ...  }}...{ path: 'admin', component: AdminComponent, ...canActivateWithRoles([Role.Admin]) },