zendframework/zend-pimple-config

Name: zend-pimple-config

Owner: Zend Framework

Description: Pimple container configurator based on ZF ServiceManager configuration

Created: 2017-09-27 20:31:23.0

Updated: 2018-04-11 17:55:54.0

Pushed: 2018-04-11 20:36:30.0

Homepage:

Size: 88

Language: PHP

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

zend-pimple-config

This library provides utilities to configure a PSR-11 compatible Pimple container using zend-servicemanager configuration, for purposes of usage within Expressive.

Installation

Run the following to install this library:

mposer require zendframework/zend-pimple-config

Configuration

To get a configured PSR-11 Pimple container, do the following:

p
Zend\Pimple\Config\Config;
Zend\Pimple\Config\ContainerFactory;

tory = new ContainerFactory();

tainer = $factory(
new Config([
    'dependencies' => [
        'services'          => [],
        'invokables'        => [],
        'factories'         => [],
        'aliases'           => [],
        'delegators'        => [],
        'extensions'        => [],
        'shared'            => [],
        'shared_by_default' => true,
    ],
    // ... other configuration
])

The dependencies sub associative array can contain the following keys:

• services: an associative array that maps a key to a specific service instance.
• invokables: an associative array that map a key to a constructor-less service; i.e., for services that do not require arguments to the constructor. The key and service name usually are the same; if they are not, the key is treated as an alias.
• factories: an associative array that maps a service name to a factory class name, or any callable. Factory classes must be instantiable without arguments, and callable once instantiated (i.e., implement the __invoke() method).
• aliases: an associative array that maps an alias to a service name (or another alias).
• delegators: an associative array that maps service names to lists of delegator factory keys, see the Expressive delegators documentation for more details.
• extensions: an associative array that maps service names to lists of extension factory names, see the the section below.
• shared: associative array that map a service name to a boolean, in order to indicate the service manager if it should cache or not a service created through the get method, independant of the shared_by_default setting.
• shared_by_default: boolean that indicates whether services created through the get method should be cached. This is true by default.

Please note, that the whole configuration is available in the $container on config key:

fig = $container->get('config');

extensions

The extensions configuration is only available with the Pimple container. If you are using Aura.Di or zend-servicemanager, you can use delegators instead. It is recommended to use delegators if you'd like to keep the highest compatibility and might consider changing the container library you use in the future.

An extension factory has the following signature:

Psr\Container\ContainerInterface;

ic function __invoke(
$service,
ContainerInterface $container,
$name

The parameters passed to the extension factory are the following:

• $service is the real service instance.
• $container is the container that is used while creating the extension for the requested service.
• $name is the name of the service being requested.

Here is an example extension factory:

Psr\Container\ContainerInterface;

s ExtensionFactory

public function __invoke($service, ContainerInterface $container, $name)
{
    // do something with $service

    return $service;
}

You can also return a different instance from the extension factory:

Psr\Container\ContainerInterface;

s ExtensionFactory

public function __invoke($service, ContainerInterface $container, $name)
{
    return new Decorator($service);
}

Please note that when configuring extensions, you must provide a list of extension factories for the service, and not a single extension factory name:

Config([
'dependencies' => [
    'invokables' => [
        'my-service' => MyInvokable\Service::class,
    ],
    'extensions' => [
        'my-service' => [
            Extension1Factory::class,
            Extension2Factory::class,
            // ...
        ],
    ],
],

Service extensions are called in the same order as defined in the list.

Using with Expressive

Replace contents of config/container.php with the following:

p

Zend\Pimple\Config\Config;
Zend\Pimple\Config\ContainerFactory;

fig  = require __DIR__ . '/config.php';
tory = new ContainerFactory();

rn $factory(new Config($config));