In all seriousness, your new technique helps us assimilate your content even better! Thank you for improving and working on yourself, this creator deserves so much more. Great job 🎉
Good content. I made some experiments about this Doing a custom exception when an error in dto validation occurs. I also experimented injecting the context of the Logger automatically for every service, interceptor, filter, etc.. there is so much more that can be done.
@muhammadazeem-iz5mq I haven't done proper research to give you the best answer, but an easy solution would be to have a .env variable called "enviornment" and if it equals "production", inside your global error handler you remove the details from your error response, by simply checking the value of "environment"
![NestJs - Modules [04]](http://i.ytimg.com/vi/eN8ok5yQOTc/mqdefault.jpg)
Thanks for the video!
You're welcome :)
In all seriousness, your new technique helps us assimilate your content even better! Thank you for improving and working on yourself, this creator deserves so much more. Great job 🎉
Thank you so much for this kind message !
much better understanding, big time, as someone whose using nestjs in production env also
estoy viendo tu contenido y es super genial, me esta ayudando mucho!
succinct and valuable, thank you!
You're welcome!
Good content. I made some experiments about this Doing a custom exception when an error in dto validation occurs.
I also experimented injecting the context of the Logger automatically for every service, interceptor, filter, etc.. there is so much more that can be done.
@@gatogordo4131 Agreed! Good job experimenting.. practice makes perfect
but how to show error messages based on environments?
in prodcution we canot show detailed messages. how to properly deal please help
te amo hermano, mi respetos señor
The best ever !
what a great content bro!
Appreciate it !
awesome 🎉🎉🎉
but how to show error messages based on environments?
in prodcution we canot show detailed messages. how to properly deal please help
@muhammadazeem-iz5mq I haven't done proper research to give you the best answer, but an easy solution would be to have a .env variable called "enviornment"
and if it equals "production", inside your global error handler you remove the details from your error response, by simply checking the value of "environment"
HI
great video
Can u make some video about elasicsearch or rabbitmq or loginin/tracing with jaeger with nestjs
thanks
Thank you for the suggestions
Can you share me the source code of this video. Thank you so much