Delegator Factories

  • Since 2.0.

Starting with the 2.0 version of the Expressive skeleton, we now support the concept of delegator factories, which allow decoration of services created by your dependency injection container, across all dependency injection containers supported by Expressive.

Delegator factories accept the following arguments:

  • The container itself;
  • The name of the service whose creation is being decrorated;
  • A callback that will produce the service being decorated.

As an example, let's say we have a UserRepository class that composes some sort of event manager. We might want to attach listeners to that event manager, but not wish to alter the basic creation logic for the repository itself. As such, we might write a delegator factory as follows:

namespace Acme;

use Psr\Container\ContainerInterface;
use Psr\Log\LoggerInterface;

class UserRepositoryListenerDelegatorFactory
     * @param ContainerInterface $container
     * @param string $name
     * @param callable $callback
     * @return UserRepository
    public function __invoke(ContainerInterface $container, $name, callable $callback)
        $listener = new LoggerListener($container->get(LoggerInterface::class));
        $repository = $callback();
        return $repository;

To notify the container about this delegator factory, we would add the following configuration to our application:

'dependencies' => [
    'delegators' => [
        Acme\UserRepository::class => [

Note that you specify delegator factories using the service name being decorated as the key, with an array of delegator factories as a value. You may attach multiple delegator factories to any given service, which can be a very powerful feature.

At the time of writing, this feature works for each of the Aura.Di, Pimple, and zend-servicemanager container implementations. Delegator factories have been supported with Pimple and zend-servicemanager since the 1.X series.