NestJS Tutorial #8 - Exceptions & Handling Exceptions
Тәжірибелік нұсқаулар және стиль
Become a Member: kzread.info...
Become a Patreon: / stuyy
Buy me a Coffee: ko-fi.com/anson
Donate on Streamlabs: streamlabs.com/ansondevacadem...
Donate on PayPal: paypal.me/ansonfoong
Connect with me:
Twitter: / ansonthedev
Discord: / discord
GitHub: github.com/stuyy
Twitch: / stuy
Пікірлер: 21
Thank you Anson, I learned a lot ! that's the tutorial I was looking for! Keep recording!
Thank you very much for your awesome tutorials!!! I learned a lot from your videos!
Great tutorial! Thanks a lot! Keep it going!
Only half way through, but have learned a lot. Great stuff!
Damn, I was expecting a copper but look what I found!!! It's a fckg gold. Thank you so much. I got so much inspiration in my head right now.
Really appreciated! You explain so smooth! Keep going
@ansonthedev
6 ай бұрын
Thank you!
still marathon watching and learning this...
@ansonthedev
6 ай бұрын
You got this!
thanks 💗
Nicely explained tutorial! i feel like custom exceptions is catered to a small niche.. like 99% of nestjs users can get everything they need from the built-in stuff. i might be wrong i'm still new to this.
Awesome video man. A little confused about the @Catch() decorator though. It looks optional at least for the use case you are showing. Things are already working as expected without the @Catch(). Could you please explain ?
1. I am waiting for Nest.js JWT tutorial. I wanted to learn about access and refresh tokens and using Redis as a whitelist for these tokens. Force logout feature will be great (deleting access and refresh token from Redis whitelist). 2. What topics do you plan to cover? 3. Great series btw. I am enjoying it very much so far. One thing that makes me confused is the middleware. Why are we still using them in Nest even if we have Guards?
@ansonthedev
2 жыл бұрын
JWT is on my mind, upcoming videos will be on Authentication, Sessions, and Testing. Guards are more important for guarding your routes based on authenticated users, or roles, for example. Middlewares should be responsible for performing some kind of task before the request reaches the Controller layer. It is possible to use middlewares instead of guards, but because Guards exist, it takes away the abstraction from middlewares, so you can focus more on doing things such as webhook validation, in the middleware layer.
thanks ^^
How to automatically get the import from first line to new line like that
May we throw exception inside middleware?
9:50
ok :)