Thank you for great materials! About this one I have a concern though: isn’t this technique suggesting to deal with some kind of global variables? Like in php, globals are accessible everywhere and could be changed everywhere. It simplifies work with them at the begging, but it also becomes an issue very fast. Would appreciate your thought on this and/or links to theory of this technique.
Interesting. I've always attached metadata to the request object directly, added the type augmentations to make TS happy, and created custom decorators that retrieve that information from the request and inject into controller handler arguments. This looks much cleaner using request-scoped data. I always avoided scoping providers to request because all child providers also become request scoped. Love advanced NestJS stuff. There is a real dearth of advanced NestJS videos, I was considering making videos myself, but I hate my voice and I can't articulate :)
With this approach, can we access the auth user (provided with JWT), only for that request scope (like PHP), anywhere in the application? If we can, it really helps me.
Get my highly rated Udemy courses here at a discount: michaelguay.dev/udemy/
I knew that there is a smart way to achieve this behavior but I don't know how. Smart one explains it amazingly. Simply you are awesome
Pls create more videos on advanced NEST JS
Thank you for great materials! About this one I have a concern though: isn’t this technique suggesting to deal with some kind of global variables? Like in php, globals are accessible everywhere and could be changed everywhere. It simplifies work with them at the begging, but it also becomes an issue very fast.
Would appreciate your thought on this and/or links to theory of this technique.
Will be nice to have use cases of this patterns
can you please suggest some active communities for nodeJS, NestJS and typeORM? like the more or less the same stack of yours
Interesting. I've always attached metadata to the request object directly, added the type augmentations to make TS happy, and created custom decorators that retrieve that information from the request and inject into controller handler arguments. This looks much cleaner using request-scoped data. I always avoided scoping providers to request because all child providers also become request scoped.
Love advanced NestJS stuff. There is a real dearth of advanced NestJS videos, I was considering making videos myself, but I hate my voice and I can't articulate :)
you'll never know for sure until you try and receive audience feedback
You should absolutely do it. Trust me, no one likes the sound of their own voice!
@@mguay absolutely coz we grew tired of hearing it all our life
With this approach, can we access the auth user (provided with JWT), only for that request scope (like PHP), anywhere in the application? If we can, it really helps me.
Yes!
@@mguay I tested with concurrent requests and it doesn't work. I want to let you know.
Have you tried NestJS CLS package for this?
Yeah I highly recommend. Altogether I like to try it without a dependency first
Thank you for your effort ❤
Thanks you so much for your work.
Great content. However could you please work on your vocal Range. Sometimes it feels uncomfortable with your base tones like someone just woke up.