How pass params to the Middleware?

Congratulations, it’s a cool framework.

I’m need restrict access to route on role-based. This works for me on express:

app.get('/dashboard', middleware.hasRole(['admin', 'creator', 'editor']), function(req,res){});

I have tried to implement a NestMiddleware, but I can not pass the parameters to it:

builder.use({
    middlewares: [ HasRole ],
    forRoutes: [{
    	path: 'dashboard', 
    	method: RequestMethod.ALL, 
    	data: { 'roles': ['admin', 'creator', 'editor'] } 
    }]
})

Here we can think of implementing guardians directly in the controller, inspired by the canActivate concept of Angular2:

{
  path: 'dashboard', 
  component: dashboardComponent, 
  canActivate: [ RoleGuard ], 
  data: { roles: [ 'admin', 'creator', 'editor' ] } 
}

Something like so:

@RequestMapping({ 
	path: '/dashboard', 
	method: RequestMethod.GET, 
	canActivate: [ HasRole ],
	data: { roles: [ 'admin', 'creator', 'editor' ] } 
})

@kamilmysliwiec What do you think is better, do you plan to implement something like this for the future?

[kamilmysliwiec]

So finally:

Since RC.8 - use() method is deprecated. Instead of use() method you should use apply().

Old way (deprecated):

builder.use({
    middlewares: [ HasRole ],
    forRoutes: [{
    	path: 'dashboard', 
    	method: RequestMethod.ALL, 
    	data: { 'roles': ['admin', 'creator', 'editor'] } 
    }]
})

New way:

builder.apply(HasRole)
    .with('admin', 'creator', 'editor')
    .forRoutes({
        path: 'dashboard',
        method: RequestMethod.ALL
    });

Using with() you can pass whatever you want (objects, arrays etc.) to the middleware resolve(...args) method. You only have to separate arguments by comma.

Now, your resolve() method of HasRole middleware should looks like that:

class HasRole {
    resolve(...roles) {
        /// the rest
    }
}

Where roles is an array of arguments passed by with() method (in this example, I used spread operator).

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.