moderntribe / square1-container
A dependency injection container wrapper for square one
Installs: 24 591
Dependents: 14
Suggesters: 0
Security: 0
Stars: 0
Watchers: 21
Forks: 1
Open Issues: 0
Requires
- php: >=7.4
- php-di/php-di: ^6.0
- 4.x-dev
- 4.2.0
- dev-master / 4.1.x-dev
- 4.1.0
- 4.0.16
- 4.0.15
- 4.0.13
- 4.0.12
- 4.0.8
- 4.0.7
- 4.0.5
- 4.0.4
- 4.0.3
- 3.6.0
- 3.5.1
- 3.5.0
- 3.4.18
- 3.4.17
- 3.4.16
- 3.4.15
- 3.4.14
- 3.4.13
- 3.4.12
- 3.4.11
- 3.4.10
- 3.4.9
- 3.4.8
- 3.4.7
- 3.4.6
- v3.4.4
- v3.4.2
- v3.4.1
- v3.4.0
- v3.3.0
- v3.2.0
- v3.1.2
- v3.1.1
- v3.1.0
- v3.0.0
- 2.1.2
- v2.1.1
- v2.0.0
- 0.0.2
- 0.0.1
- dev-feature/monorepo
This package is auto-updated.
Last update: 2024-10-25 20:58:35 UTC
README
The Tribe Libs Container uses PHP-DI to help you build object graphs, allowing for autowiring dependency injection.
Mutable Container
In general, you should design your services to be stateless.
However, for long-running processes (like queues) or in situations where you absolutely must create a fresh object, including all of its dependencies, you can use the Mutable Container.
This opens up the makeFresh()
method, which works exactly like PHP-DI's make() method, but flushes the container's resolved entries, meaning the object's dependencies will also be recreated from scratch.
NOTE: Only use this when necessary, this is not as performant as the default container.
In a definer:
<?php declare(strict_types=1); namespace Tribe\Project\Feature; use Psr\Container\ContainerInterface; use Symfony\Contracts\HttpClient\HttpClientInterface; use Tribe\Explore_Navigation\Azure\Factories\Client_Factory; use Tribe\Libs\Container\Definer_Interface; use Tribe\Libs\Container\MutableContainer; use Tribe\Libs\Container\Container; class My_Feature_Definer implements Definer_Interface { public function define(): array { return [ // Define our abstract to the interface, placing our existing container inside the mutable container. MutableContainer::class => static fn ( ContainerInterface $c ) => ( new Container() )->wrap( $c ), ]; } }
Then you can utilize the makeFresh()
method to create purely fresh objects
each time it's called:
<?php declare(strict_types=1); namespace Tribe\Project\Feature; use Tribe\Libs\Container\Abstract_Subscriber; use Tribe\Libs\Container\MutableContainer; class My_Queue_Factory { protected MutableContainer $container; public function __construct( MutableContainer $container ) { $this->container = $container; } /** * Make a fresh object. * * @param string $class_name e.g. \Tribe\Project\Feature\SomeFeature::class * * @return mixed|string */ public function make( string $class_name ) { return $this->container->makeFresh( $class_name ); } }
Then call your factory:
<?php declare(strict_types=1); namespace Tribe\Project\Feature; use Tribe\Libs\Container\Abstract_Subscriber; use Tribe\Libs\Container\MutableContainer; class My_Feature_Subscriber extends Abstract_Subscriber { public function register(): void { add_action( 'init', function(): void { // Both of these will be completely separate instances, // including any dependencies SomeFeature::class has. var_dump( $this->container->get( MutableContainer::class )->make( '\Tribe\Project\Feature\SomeFeature::class' ) ); var_dump( $this->container->get( MutableContainer::class )->make( '\Tribe\Project\Feature\SomeFeature::class' ) ); // This will be the same instance as the last freshly made object var_dump( $this->container->get( SomeFeature::class ) ); }, 10, 0 ); } }