Download the PHP package istok/container without Composer
On this page you can find all versions of the php package istok/container. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download istok/container
More information about istok/container
Files in istok/container
Package container
Short Description DI / IoC container with `call(\Closure $fn): mixed` method
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
- allow to call any
\ClosurewithContainer::call(\Closure $fn): mixedmethod - allow custom resolving by attributes (useful to fill DTO)
- allow param-name binding:
Container::argument(string $name, string $for, \Closure $resolver) - provided with wrapper implementing PSR-11 (see
Istok\Container\Psr\StrictContainerandIstok\Container\Psr\GreedyContainer)
Registration methods
$definition parameters will be resolved by Container
Retrieving
Identifier resolution order
- use direct registration
- use attributes, use if any suited
- try to construct
Closure arguments resolution
- apply explicitly provided arguments
- use
Container::get()to resolve rest
Resolving by attributes
If target class has attribute that implements Istok\Container\Resolver interface, instance of attribute will be constructed (by Container::get, not ReflectionAttribute::newInstance()), and then result of Resolver::resolve($targetName, ...$attributeArgs) will be returned as result.
Service and Model resolving
According to Object Design Style Guide by Matthias Noback, there are two types of objects:
Two types of objects
In an application there are typically two types of objects:
- Service objects which either perform a task, or return a piece of information.
- Objects that hold some data, and optionally expose some behavior for manipulating or retrieving that data.
First type have a well-known name, Service, and other one I called Model (I have to called it someway).
While Services depends on both other Services and Models, Models depends only on other Models and input.
One of reasons why I want to create this container was the desire to be able to get well-typed DTOs filled from user input, or config, as arguments of my controllers.
To achieve this, I added Resolver interface, which implementation can be used as attribute of Model.
This allows to add contextual configuration for resolving this type of objects.
So, Container itself is mostly for resolving Services, and ModelResolver used for resolving Models, like request DTOs.
