DEV Community

Injecting request object to a custom validation class in NestJS

Krzysztof Szala on May 12, 2021

I'm a big fan of how NestJS handle validation using class-validator library. There are many advantages of using an external library for validation....

Read full post

Walid-Gerges • May 26 '22

You can go a step forward and use request context.

npmjs.com/package/@medibloc/nestjs...

Thanks for your tips, it helped me.

Monirul Islam • Sep 19 '21

this is not working ValidationArguments does not hold REQUEST_CONTEXT

Krzysztof Szala • Sep 20 '21

There was obviously typo in decorator composition class. Instead of AddUseTo, there should be InjectUserTo. Please try if it works for you now.

Krzysztof Szala • Sep 20 '21 • Edited

Are you sure you created interceptor, which injects the REQUEST_CONTEXT? I'm using similar code in my production-ready app and it works for me.

Monirul Islam • Sep 20 '21

yes i am using but its not working btw.I did exactly the way you said

Monirul Islam • Sep 20 '21

even console logged the args but REQUEST_CONTEXT returns undefined

Siavash Habil • Mar 29 '22

@monirul017 @avantar
I had exactly same problem and after investigating it is happening because of {whitelist: true} of ValidationPipe and when you set it to false it will working properly but I didn't continue in this way because I want to whitelist the properties so temporary I added _requestContext to the related DTO file that I used in my controller and added it as an @IsOptional() decorator

import { REQUEST_CONTEXT } from '../../../interceptors/inject-request-param.interceptor';


  @IsOptional()
  \[REQUEST_CONTEXT\]: any;

Ignore "\" from the above code.

For others trying to use this article as a solution continue using from attached repository.

At the end thank you @avantar for your solution.

Krzysztof Szala • Mar 29 '22

Thank you, @siavash_habil! This can be helpful as well.

github.com/AvantaR/nestjs-validati...

Siavash Habil • Mar 29 '22

@avantar This is almost happened at the same time for both of us because I solved it about 20 hours ago. :)
Thank you for sharing.

Krzysztof Szala • Mar 29 '22

What a coincidence! Magic 🎉

Ivan Brezhniev • Aug 30 '24 • Edited

Have you considered using a Symbol instead of a string for the REQUEST_CONTEXT constant?

export const REQUEST_CONTEXT = Symbol('REQUEST_CONTEXT');

In this case, you will not need to do this omit(value, REQUEST_CONTEXT);

tkssharma • Sep 10 '21

this is awesome but not sure if i want to use this !! not a clean solution

Krzysztof Szala • Sep 10 '21

Totally agree, but sometimes we need to do something dirty way 🤷‍♂️ Thanks for your feedback! 🙏

Wahyu Baskara • Aug 4 '23

ValidationArguments does not hold REQUEST_CONTEXT when using nested validation object

Dolphine Dev • Aug 4 '23 • Edited

When using @ValidateNested(), the args?.object[REQUEST_CONTEXT] is undefined because the context passed to the nested validation is not the same as the one at the top level.

Szymon Sukiennik • Nov 29 '21

Did you ever managed to port a similar approach to graphql in Nest? Namely, to have access to part or even whole gql context inside validator or validation rule?