
π§
Technically\CascadeContainer
is simple yet powerful PSR-11 based service container implementation with layers and dependencies auto-wiring.
- PSR Container compatibility
- Semantic Versioning
- PHP 8.0+
- Minimal yet elegant API
- Supports inheriting services from a parent PSR-11 Service Container
- Supports forking the service container instance into an isolated layer, inheriting all existing service definitions from the original container.
- PSR Container compatibility
- Autowiring β automatic dependencies resolution
- Full PHP 8.0+ features support for auto-wiring (e.g. union types)
Use composer.
composer require technically/cascade-container
Checking presence, getting and setting service instances to the service container.
::get(string $id): mixed
β Get a service from the container by its name::has(string $id): bool
β Check if there is a service defined in the container with the given name::set(string $id, mixed $instance): void
β Define a service instance with the given name to the container
<?php
use Technically\CascadeContainer\CascadeContainer;
$container = new CascadeContainer();
// Set a service instance to the container
$container->set('acme', new AcmeService());
// Check if there is a service binding for the given service
echo $container->has('acme') ? 'ACME service is defined' : 'Nope';
// Get a service from container
$acme = $container->get('acme');
$acme->orderProducts();
It's handy to bind services by their abstract interfaces to explicitly declare its interface on both definition and consumer sides.
<?php
/** @var $container \Technically\CascadeContainer\CascadeContainer */
// Definition:
// Note we bind an instance by its **abstract** interface.
// This way you force consumers to not care about implementation details, but rely on the interface.
$container->set(\Psr\Log\LoggerInterface::class, $myLogger);
// Consumer:
// Then you have a consumer that needs a logger implementation,
// but doesn't care on details. It can use any PSR-compatible logger.
$logger = $container->get(\Psr\Log\LoggerInterface::class);
assert($logger instanceof \Psr\Log\LoggerInterface);
$logger->info('Nice!');
Sometimes you may also want to bind the same service by different IDs. You can use aliases for that:
::alias(string $serviceId, string $alias): void
β Allow accessing an existing service by its new alias name
<?php
/** @var $container \Technically\CascadeContainer\CascadeContainer */
$container->set(\Psr\Log\LoggerInterface::class, $myLogger);
$container->alias(\Psr\Log\LoggerInterface::class, alias: 'logger');
$logger = $container->get(\Psr\Log\LoggerInterface::class);
// ... or
$logger = $container->get('logger'); // 100% equivalent
$logger->info('Nice!');
You can declare a service by providing a deferred resolver function for it. The service container will call that function for the first time the service is requested and remember the result.
::deferred(string $serviceId, callable $resolver): void
β Provide a deferred resolver for the given service name.
Note: the callback function parameters are auto-wired the same way as with the ->call()
API.
<?php
/** @var $container \Technically\CascadeContainer\CascadeContainer */
$container->deferred('connection', function (ConnectionManager $manager) {
return $manager->initializeConnection();
});
// Consumer:
$connection = $container->get('connection'); // The connection object
$same_connection = $container->get('connection'); // The same connection object
assert($connection === $same_connection); // The same instance
You can also provide a factory function to be used to construct a new service instance every time it is requested.
It works very similarly to ->resolver()
, but calls the factory function every time.
::factory(string $serviceId, callable $factory): void
β Bind a service to a factory function to be called every time it is requested.
Note: the callback function parameters are auto-wired the same way as with the ->call()
API.
<?php
/** @var $container \Technically\CascadeContainer\CascadeContainer */
// Definition:
$container->factory('request', function (RequestFactory $factory) {
return $factory->createRequest();
});
// Consumer:
$request = $container->get('request');
$another = $container->get('request');
assert($request !== $another); // Different instances
Sometimes it is necessary to extend/decorate an existing service by changing it or wrapping it into a decorator.
-
::extend(string $serviceId, callable $extension): void
β Extend an existing service by providing a transformation function.- Whatever the callback function returns will replace the previous instance.
- If the service being extended is defined via a deferred resolver, the extension will become a deferred resolver too.
- If the service being extended is defined as a factory, the extension will become a factory too.
<?php
/** @var $container \Technically\CascadeContainer\CascadeContainer */
// Definition:
$container->deferred('cache', function () {
return new RedisCache('127.0.0.1');
});
// Wrap the caching service with a logging decorator
$container->extend('cache', function(RedisCache $cache, LoggerInterface $logger) {
return new LoggingCacheDecorator($cache, $logger);
});
// Consumer:
$cache = $container->get('cache'); // LoggingCacheDecorator object
// Uses cache seamlessly as before (implying that RedisCache and LoggingCacheDecorator have the same interface)
Sometimes it is necessary to create an isolated instance of the service container, inheriting its configured services and allowing to define more, without affecting the parent container.
Think of it as JavaScript variables scopes: a nested scope inherits all the variables from the parent scope. But defining new scope variables won't modify the parent scope. That's it.
::cascade(): CascadeContainer
β Create a new instance of the service container, inheriting all its defined services.
$project = new CascadeContainer();
$project->set('configuration', $config);
$module = $project->cascade();
$module->set('configuration', $config->extend($local));
$module->factory('request', function () {
// ...
});
// and so on
assert($project->get('configuration') !== $module->get('configuration')); // Parent service "configuration" instance remained unchanged
You can construct any class instance automatically injecting class-hinted dependencies from the service container. It will try to resolve dependencies from the container or construct them resolving their dependencies recursively.
::construct(string $className, array $parameters = []): mixed
β Create a new instance of the given class auto-wiring its dependencies from the service container.
<?php
/** @var $container \Technically\CascadeContainer\CascadeContainer */
// Class we need to inject dependencies into
class LoggingCacheDecorator {
public function __construct(CacheInterface $cache, LoggerInterface $logger, array $options = []) {
// initialize
}
}
$container->set(LoggerInterface::class, $logger);
$container->set(CacheInterface::class, $cache);
// Consumer:
$cache = $container->construct(LoggingCacheDecorator::class);
// you can also provide constructor arguments in the second parameter:
$cache = $container->construct(LoggingCacheDecorator::class, ['options' => ['level' => 'debug']]);
You can call any callable auto-wiring its dependencies from the service container.
::call(callable $callable, array $parameters = []): mixed
β Call the given callable auto-wiring its dependencies from the service container.
<?php
/** @var $container RockSymphony\ServiceContainer\ServiceContainer */
class MyController
{
public function showPost(string $url, PostsRepository $posts, TemplateEngine $templates)
{
$post = $posts->findByUrl($url);
return $templates->render('post.html', ['post' => $post]);
}
}
$container->call([new MyController(), 'showPost'], ['url' => '/hello-world']);
You can as well pass a Closure to it:
$container->call(function (PostsRepository $repository) {
$repository->erase();
});
This project is licensed under the terms of the MIT license.
Implemented by πΎ Ivan Voskoboinyk.