Download the PHP package composite-php/container without Composer
On this page you can find all versions of the php package composite-php/container. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download composite-php/container
More information about composite-php/container
Files in composite-php/container
Package container
Short Description A PSR-11 implementation with auto-wiring.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package container
DI container
Yet another implementation of PSR-11 with support of automatic constructor injection.
Requires PHP 8.1 or higher.
Features
- Implements PSR-11.
- Supports automatic constructor injection ((via
Reflection). - Detects cyclic dependencies.
Installation
Install with composer:
Usage
Automatic resolution
The container can do constructor injection automatically. Assume you have the following classes in your project:
In order to create an instance of UserRegistrationService, you should pass its dependencies to the constructor:
The container is capable of doing it on its own:
The container is capable of automatic injection of arguments, as long as they are concrete classes or built-in types with default values:
Entries are reused once resolved
The container caches resolved entries (it also means, that the container retains references to resolved entries), so, be careful when writing stateful code:
Another example that demonstrates this:
Custom Definitions
You can specify definitions for entries by passing them to the constructor of the container. Each definition must be a callable identified by the entry ID. The simplest case would be an array:
However, any iterable is accepted by the constructor. Some may find this notation better:
You are not limited to classes/objects only, of course:
Once container is instantiated, its definitions cannot be modified.
Custom entries are prioritized over existing classes.
Usage is straightforward: create container instance, optionally passing your definitions.
The constructor accepts your definitions in form of an iterable (array/Generator/Traversable):
They key must be item name and the value must be a callable which returns the item.
The callable argument will be the Container instance.
