PHP DI - Dependency Injection Container Component - Vection Framework

v0.1.0 2019-08-14 21:24 UTC


The php DI component provides a powerful and easy library for dependency injection with different injection types.


This component is a part of the PHP Vection-Framework and can be used by composer install only.

    "require": {
        "vection-framework/di-container": "dev-master"


    $ composer install vection-framework/di-container


The container can inject only registered objects by default. Classes can be registered by the Container::set method or by a optional php configuration file.

Registration by Container itself

    $container = new Container();

    # Very basic and fastest way to register an class by the container

    # You can also pass optional an Definition object for custom injection and creation information
    $definition = new Definition(My\Custom\Awesome::class);
    $definition->.....; #(explained at next section)
    $container->set(My\Custom\Awesome::class, $definition);

Dependency Definition object

The definition object registers a class for injection, defines the dependencies and how they have to be injected. This definition objects can be registered by the Container::set or a optional configuration file.

    $definition = new Definition(My\Custom\Awesome::class);
    # This defines which dependencies should be used as construction parameter when creating object
        My\Custom\Dependency::class, My\Other\Dependency::class, ...
    # This closure will be used on the fly to create the Awesome object
        $object = new My\Custom\Awesome();
        return $object;

    # This defines the dependencies which will be injected by 
    #setter (set<DependencyShortClassName> based almost on interfaces)
        My\Custom\Dependency::class, My\Other\Dependency::class, ...

    # This sets the class as not shareable to recreate on each injection
    # Register the class with its definition
    $container->set(My\Custom\Awesome::class, $definition);

Container Configuration file (optional, best practise)

The configuration file is recommended to keep the definition out of the main application code for better handling and maintenance. The configuration file is just a php file that returns an array of Definition objects, created by the Vection\Component\DI\set function.

    use function Vection\Component\DI\set;
    return [
                return new My\Custom\Awesome();
        # Each class that implements this interface will get an 
        #instance of Awesome class by setters defined in the interface
        # And so on, see definition at section previouse section

This configuration file have to be loaded by the container in following way.

    $container = new Container();

    # optional you can use the glob pattern for multiple config files
    # This will load all config files of each component

Using cache

It is recommended to use the cache to avoid performance issues on large applications. The DI component uses the Cache contracts of the Vection Contracts. So you can use an own cache implementation by implementing the CacheInterface from Vection\Contracts\Cache or use one of the already existed Vection Cache provider (Redis, Memcache, APCu). You can also use the Symfony Bridge (Vection\Bridge\Symfony\Cache\SymfonyCacheProviderBridge).

    $cacheProvider = new Vection\Component\Cache\Provider\RedisCacheProvider(...);
    $cache = new Vection\Component\Cache\Cache($cacheProvider);

    $container = new Container();