Various Yii 3.0 related documentation
There are two ways of re-using things in OOP: inheritance and composition.
Inheritance is simple:
class Cache
{
public function getCachedValue($key)
{
// ..
}
}
final readonly class CachedWidget extends Cache
{
public function render(): string
{
$output = $this->getCachedValue('cachedWidget');
if ($output !== null) {
return $output;
}
// ...
}
}
The issue here is that these two are becoming unnecessarily coupled or inter-dependent, making them more fragile.
Another way to handle this is composition:
interface CacheInterface
{
public function getCachedValue($key);
}
final readonly class Cache implements CacheInterface
{
public function getCachedValue($key)
{
// ..
}
}
final readonly class CachedWidget
{
public function __construct(
private CacheInterface $cache
)
{
}
public function render(): string
{
$output = $this->cache->getCachedValue('cachedWidget');
if ($output !== null) {
return $output;
}
// ...
}
}
We’ve avoided unnecessary inheritance and used interface to reduce coupling. You can replace cache
implementation without changing CachedWidget so it’s becoming more stable.
The CacheInterface here is a dependency: an object another object depends on.
The process of putting an instance of dependency into an object (CachedWidget) is called dependency injection.
There are many ways to perform it:
In the composition example above, note that the $cache property is declared as private.
This approach embraces composition by ensuring objects have well-defined interfaces for interaction rather than direct property access, making the code more maintainable and less prone to certain types of mistakes.
This design choice provides several benefits:
with*() methods return
new instances rather than modifying the current one.Injecting basic dependencies is straightforward. You’re choosing a place where you don’t care about dependencies, which is usually an action handler, which you aren’t going to unit-test ever, create instances of dependencies needed and pass these to dependent classes.
It works well when there are few dependencies overall and when there are no nested dependencies. When there are many and each dependency has dependencies itself, instantiating the whole hierarchy becomes a tedious process, which requires lots of code and may lead to hardly debuggable mistakes.
Additionally, lots of dependencies, such as certain third-party API wrappers, are the same for any class using it. So it makes sense to:
That’s what dependency containers are for.
A dependency injection (DI) container is an object that knows how to instantiate and configure objects and all their dependent objects. Martin Fowler’s article has well explained why DI container is useful. Here we will mainly explain the usage of the DI container provided by Yii.
Yii provides the DI container feature through the yiisoft/di package and yiisoft/injector package.
Because to create a new object you need its dependencies, you should register them as early as possible.
You can do it in the application configuration, config/web.php. For the following service:
final class MyService implements MyServiceInterface
{
public function __construct(int $amount)
{
}
public function setDiscount(int $discount): void
{
}
}
configuration could be:
return [
MyServiceInterface::class => [
'class' => MyService::class,
'__construct()' => [42],
'setDiscount()' => [10],
],
];
That’s equal to the following:
$myService = new MyService(42);
$myService->setDiscount(10);
There are extra methods of declaring dependencies:
return [
// declare a class for an interface, resolve dependencies automatically
EngineInterface::class => EngineMarkOne::class,
// array definition (same as above)
'full_definition' => [
'class' => EngineMarkOne::class,
'__construct()' => [42],
'$propertyName' => 'value',
'setX()' => [42],
],
// closure
'closure' => static function(ContainerInterface $container) {
return new MyClass($container->get('db'));
},
// static call
'static_call' => [MyFactory::class, 'create'],
// instance of an object
'object' => new MyClass(),
];
Directly referencing a container in a class is a bad idea since the code becomes non-generic, coupled to the container interface and, what’s worse, dependencies are becoming hidden. Because of that, Yii inverts the control by automatically injecting objects from a container in some constructors and methods based on method argument types.
This is primarily done in constructor and handing method of action handlers:
use \Yiisoft\Cache\CacheInterface;
final readonly class MyController
{
public function __construct(
private CacheInterface $cache
)
{
$this->cache = $cache;
}
public function actionDashboard(RevenueReport $report)
{
$reportData = $this->cache->getOrSet('revenue_report', function() use ($report) {
return $report->getData();
});
return $this->render('dashboard', [
'reportData' => $reportData,
]);
}
}
Since it’s yiisoft/injector that instantiates and calls action handler, it checks the constructor and method argument types, gets dependencies of these types from a container and passes them as arguments. That’s usually called auto-wiring. It happens for sub-dependencies as well, that’s if you don’t give dependency explicitly, the container would check if it has such a dependency first. It’s enough to declare a dependency you need, and it would be got from a container automatically.