You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2020. It is now read-only.
What are the main pros and cons of this library over Dagger 2? Why should one choose injekt? It would be great to add a short section to README describing this
The text was updated successfully, but these errors were encountered:
Read the documentation for Dagger 2, then read the documentation for Injekt. If one makes more sense to you than the other, use it. Injekt is a object registry pattern where you are in complete control, and using default values for constructors that call Injekt, or initializing properties with Injekt or delegates of Injekt, you can easily build anything another dependency injection system can do but without anything being hidden. And it will also work in unit tests without even having to use injection if you layer things correctly. Again, because you are in complete control and everything is obvious. I don't use Dagger 2, never have, and didn't like the type of library it was when I read the docs so I moved on to my own.
What are the main pros and cons of this library over Dagger 2? Why should one choose injekt? It would be great to add a short section to README describing this
The text was updated successfully, but these errors were encountered: