#Nest use annotation instead or registering them
7 messages · Page 1 of 1 (latest)
Then you'd lose modularity and a way to separate implementations from interfaces.
Comparing to spring that still uses modularity but doesn’t require manual registration of dependencies
Java != TypeScript. 🤷🏻♂️ (Thank the heavens.....)
I get that
Manual registration just seems more stressful and easier to fall into resolving dependency issues
Dependencies in Spring (Boot) get unwieldy really fast. Debugging that is one hell. I am glad Nest doesn't do it. And I'm glad .NET Core (C#) also doesn't do it. And any of the popular IoC frameworks for Kotlin (Koin, Dagger Hilt) don't do it 😅
Oh that I haven’t experienced yet