How pass params to the Middleware? about nest

[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).

[kamilmysliwiec]

Hi @cdiaz,

Thanks! :) It is a good question. Since Middlewares in Nest are just types it is not so easy to pass them additional data. I have been wondering how to provide this feature in easy way to use and I decided to do it as below:

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

So it will be still possible to chain use() calls, pass arrays in both use() and forRoutes() and also add some custom data between use() and forRoutes() calls (with() - of course - is optional). Is it looks more intuitive? What do you think?

Referring to your proposal with canActivate concept - some middlewares just decorate requests with data. Their responsibility is not only to activate / deactivate routes. This is why I drop this idea :)

[cdiaz]

This is great and very useful, just what I wanted.
Thanks

[nextsoftpl]

That's really nice, however how can i inject a service then in the middleware? when passing parameters to resolve, then injection stops working

[lock]

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.