It's been the 50th time I'm listening to this video, every time I understand 1% better DI in Nest but I'm far from understanding it well yet, 50% actually :)
I like his glasses. Moreover, I must say I love the principles of Nest.js on the backend, but honestly, I think Angular is worse than React. Vue makes a good compromise between freedom and code predictability. :)
why would you want that? You can use normal inheritance for an Interface and a generic type declaration is just a type construct that can't be passed around outside of a type definition.
@@api-first Yes I also dont really see a reason for that. Even if you wanted to switch between providers which implement a specific interface after init you could just assign the initially injected provider to the interface in the constructor. If you want to choose before init you can just use a custom provider factory, which doesn't need type information due to the custom token.
It's been the 50th time I'm listening to this video, every time I understand 1% better DI in Nest but I'm far from understanding it well yet, 50% actually :)
working with nest for more than a year now, what a cool talk, I can feel my heart beating faster as he explains it
I'm in love with NestJS!
I am build a new product using nestjs .... This video is god-tier explainer on how nestjs DI works. Learnt a lot
Thankyou so much for sharing
Great talk! Love NestJS!
Watched this to study nestjs fundamentals. Crazy experience
I'm in love with NestJS!,its amazing .
Wow, this dude is a legend!
I like his glasses. Moreover, I must say I love the principles of Nest.js on the backend, but honestly, I think Angular is worse than React. Vue makes a good compromise between freedom and code predictability. :)
Why compromise when you have svelte?
NestJS Rules! s2
Whoa look at the back of his notebook, this guy sure loves stickers :D
I'd like to know why nest.js strictly applies to Isolation of modules
To save some time for some people, Nest.js's DI framework does not offer a solution for Interfaces and Generics to be used as providers
why would you want that? You can use normal inheritance for an Interface and a generic type declaration is just a type construct that can't be passed around outside of a type definition.
@@api-first Yes I also dont really see a reason for that. Even if you wanted to switch between providers which implement a specific interface after init you could just assign the initially injected provider to the interface in the constructor. If you want to choose before init you can just use a custom provider factory, which doesn't need type information due to the custom token.
thanks for the warning. I am dying looking for a solution for this crap.
NestJS ftw
Those shorts caught me off guard
#LoveNestJS
this guy's glasses detract from his credibility
React fans hating Angular but loving Nestjs... I'm like WTF ???
Because Angular sucks but Nestjs doesn't