Author Latest Version Github Issues Pending Pull-Requests Software License Build Status Coverage Status Quality Score Total Downloads


This package is compliant with PSR-1, PSR-2, PSR-4 and PSR-11. If you notice compliance oversights, please send a patch via pull request.

Download 1.4.1


Via Composer:

$ composer require kocuj/di


The following versions of PHP are supported by this version:

  • PHP 7.0
  • PHP 7.1
  • PHP 7.2
  • PHP 7.3


In this documentation it is assumed that you will import namespaces for the Kocuj DI library by using the following code:

use Kocuj\Di\Di;
use Kocuj\Di\Service\ServiceType\ServiceType;

To use the Kocuj DI library you must first initialize it:

$di = new Di();

It will create a Kocuj DI library object. You can create more Di objects, but it is not recommended. The better solution is to create more DI containers, which will be explained in the next part of this documentation.

After the construction, the $di variable will have one container for Dependency Injection, which you can get by using the following code:

$defaultContainer = $di->getDefault();

You can also create more containers:

$myContainer = $di->create();

You can also create new container based on already existing container by using the following code:

$myContainer = $di->copy($oldContainer);

From now on you can use new container by using methods on $myContainer variable. However, the following documentation will use default container for explanations about using the Kocuj DI library.

After creating the container (default or other), you can add services into it. There are two types of services:

  • shared - service which will be constructed only once, like in Singleton design pattern;
  • standard - service which will be constructed on each use.

To create service you can use the following method: add(ServiceType $serviceType, string $id, string $source, array $arguments = []): ContainerInterface

The $serviceType argument can be one of the following:

  • to create shared service - new ServiceType(ServiceType::SHARED);
  • to create standard service - new ServiceType(ServiceType::STANDARD).

If you want to ommit a $serviceType argument, you can use one of the following methods:

  • to create shared service - addShared(string $id, string $source, array $arguments = []): ContainerInterface;
  • to create standard service - addStandard(string $id, string $source, array $arguments = []): ContainerInterface.

Argument $id is an identifier of created service. All identifiers will be automatically converted to camelCase format. Remember, that inside one container there can be only one service with the selected identifier.

Argument $source is a fully qualified class name for service. It is a good practice to use "::class" notation in this place.

For example, to add shared service from class \Services\Service with "someService" identifier, use the following code:

$myContainer->addShared('someService', \Services\Service::class);

However, the best feature of the Kocuj DI library is to automatically resolving dependencies between services. To use this feature, there should be at least one argument sent to a service constructor. The place to do so is in $arguments argument.

Each argument in $arguments contains an array with one element with index "type" and second with index "value" which value depends on value set in index "type". Element with index "type" contains a name of argument type.

There are two types of arguments selected by element with index "type":

  • "service" - to set service to get, there must be a second element in array with index "value" containing service identifier;
  • "value" - to set value, there must be a second element in array with index "value" containing this value.

For example, to add shared service from class \Services\OtherService with "otherService" identifier, which has constructor __construct(\Services\Service $service, bool $status) and require $status to set to true, use the following code:

$myContainer->addShared('otherService', \Services\OtherService::class, [
        'type' => 'service',
        'value' => \Services\Service::class
        'type' => 'value',
        'value' => true

The order of adding services to container is not important, because during construction of service all dependencies will be automatically resolved.

To get service object you can use the following code:




Additionally you can check type of service by using the following method: checkType(string $id, ServiceType $serviceType): bool. You can also check if service exists in container by using the following method: has($id): bool.

To control any wrong situations, there are the following exceptions available:

  • \Kocuj\Di\ArgumentParser\Exception - for problems with argument with other services and/or values for created service;
  • \Kocuj\Di\Container\Exception - for problem with creating or getting service in container;
  • \Kocuj\Di\Service\Exception - for problems with service type; however, this exception will not be used when this library is used correctly.

Example of using the library:


use Kocuj\Di\Di;

// initialize DI container
$di = new Di();
// get DI container
$container = $di->getDefault();
// set DI services
$container->addShared('input', InputService::class);
$container->addShared('output', OutputService::class);
$container->addStandard('main', Main::class, [
        'type' => 'service',
        'value' => 'input'
        'type' => 'service',
        'value' => 'output'
// execute

For more information you can see examples included in this project or by looking on project website.


$ vendor/bin/phpunit

Creating programming documentation

$ vendor/bin/phpdoc


Please see CONTRIBUTING for details.


If you discover any security related issues, please contact me by using contact form on project website instead of using the issue tracker.


The MIT License (MIT). Please see License File for more information.