/explore
|
You are here 
|
brandonsavage.net | ||
| | | | |
tomasvotruba.com
|
|
| | | | | Regarding Laravel, one of the biggest "no"s in 2022 was how it handles passing services around the project. I'm not talking about the facades or active records but **the static reflection container**. At first, it raised my blood pressure - we have a dependency injection, and everything must be passed via the constructor, right? Then I remembered a wise saying: "There are no best solutions, only trade-offs." | |
| | | | |
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 ... | |
| | | | |
sookocheff.com
|
|
| | | | | Inversion of Control (IoC), also known as Dependency Injection (DI), allows an object to define their dependencies as constructor arguments (strictly speaking, you can set these dependencies as properties, but the examples I will use today are constructor-based). This is the inverse of the object itself controlling the instantiation or location of its dependencies, hence the name Inversion of Control. Let's look at an example from Stackoverflow using a text editor with a spell checking component: | |
| | | | |
jeffreytse.net
|
|
| | | |||
