|
You are here |
fsharpforfunandprofit.com | ||
| | | | |
conradakunga.com
|
|
| | | | | This is Part 8 of a series on dependency injection. | |
| | | | |
jmmv.dev
|
|
| | | | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | |
| | | | |
mikemikina.com
|
|
| | | | | Vapor 3 has a very interesting dependency injection framework which will help you manage dependencies and mock them inside your tests. | |
| | | | |
tomasvotruba.com
|
|
| | | Series about PHP CLI Apps continues with 3rd part about writing Symfony Console Application with Dependency Injection in the first place. Not last, not second, **but the first**. Luckily, is easy to start using it and very difficult to | ||