Explore >> Select a destination
|
You are here 
|
dagger.dev | ||
| | | | |
mikemikina.com
|
|
| | | | | Vapor 3 has a very interesting dependency injection framework which will help you manage dependencies and mock them inside your tests. | |
| | | | |
publicobject.com
|
|
| | | | | You can do dependency injection (DI) manually or with a library. Constructing your applications dependency graph by hand is a cute exercise but not practical beyond toy examples. Youll eventually find yourself extracting the repetitive manual DI code into your own bespoke library, one thats likely to | |
| | | | |
ryanharter.com
|
|
| | | | | I recently gave a presentation about how Dagger works under the hood, and I was once again struck by the elegance of the javax.inject.Provider interface. The interface is so simple it almost seems useless, but it's also incredibly flexible, and forms the basis of much of the code generated by Dagger. Like many dependency injection frameworks for JVM languages, Dagger uses and builds on the standard set of annotations for injectable classes defined in JSR-330 and provided in the javax. | |
| | | | |
www.arunkumar.dev
|
|
| | | Exploring how Dagger can be extended to add project specific dependency graph valditations for even more robust compile time verification. | ||
