Add decorator after @Get

Its posible add my own decorator after @Get decorator? Because when I do this res seems to be not linked with express response

  @Get()
  @Decorator()
  public async getAll( @Res() res: Response) {
    res.status(HttpStatus.OK).send();

Update: Watching this I think it can be posible

[FranciZ]

@cojack Thanks, but I’m aware of this. I’d still rather have the option to apply middleware in the controller since it’ll be much more transparent.

I see usefulness in defining middleware in the module if it’s for all the routes of a controller or something more general. But for things like role specific access control and authentication it’s much more transparent to add it as a decorator in controller imo.

Having to define paths and methods affected in two different places is also something I’d rather avoid.

[FranciZ]

@silvelo @ThomRick I’m facing a similar dilemma. I want to have transparent route handling and plug authentication and role checking per route in the controller in most cases. Not sure what the advantage is of having this logic separated in another file (Module) and paths redefined in two places.

Something like the UseMiddlewares decorator as below would be great.

  @Delete('v1/user/:userId')
  @UseMiddlewares(new AuthMiddleware(['ADMIN']))
  public async deleteUser(@Req() req: IRequest, @Res() res: Response, @Param() reqParams: VDeleteUser): Promise<any> {
    const userId = reqParams.userId;
    const removedUser = await this.userService.remove(userId);
    if (removedUser === null) return this.responseService.error({
      res,
      code: HttpStatus.NOT_FOUND,
      data: { _id: userId }
    });
    this.responseService.success({ res, data: { _id: userId } });
  }