/explore
|
You are here 
|
dagger.dev | ||
| | | | |
fusectore.dev
This is the first part in a series of articles on dependency injection for the play framework using guice. As soon as Ive written the next part, it will be linked here. Please note that while the examples are written in Scala, the principles apply for Java likewise. Furthermore, please be aware that Guice is not the only framework to do dependency injection with. It is probably the most prominent one in the play ecosystem though. Guice does so called runtime dependency injection. This means dependencies ... |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
mikemikina.com
Vapor 3 has a very interesting dependency injection framework which will help you manage dependencies and mock them inside your tests. |
|
| | | | | ||
| | | | |
blog.theamazingrando.com
The point of this post isn't to convince you of the usefulness of Dependency Injection there's been plenty of pixels spilled about it already. Instead, I want to talk about using Dry::Container to alleviate some of the pain points that DI introduces. |
|
| | | |||
