Download the PHP package evaneos/dic-it without Composer
On this page you can find all versions of the php package evaneos/dic-it. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download evaneos/dic-it
More information about evaneos/dic-it
Files in evaneos/dic-it
Package dic-it
Short Description Yet another dependency injection container
License MIT
Homepage http://github.com/Evaneos/dic-it
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 dic-it
dic-it
DIC-IT is a simple dependency injection container, with extensible activation & injection strategies.
Setup
The recommended setup is to create a config folder at the root of your repository. All configuration is based on YAML files.
Sample YAML file :
References
You can inject different kind of references inside class definitions. You can get other service instances, parameters, the container itself, env variables, and constant values.
- @ServiceName : fetch an instance of that definition
- %param : fetch a parameter defined in the container
- $container : fetch the container itself
- $env.ENV_NAME : fetch an environment variable
- $const.CONST_NAME : fetch a global defined constant value
Using includes
The configuration can be split into multiple files to ease management of your dependencies :
This allows you to separate parameters from service definitions for example.
Default object life-cycle
By default, all objects are created as non-singleton (this will definitely change) objects, so every time a reference is resolved by the container, a new instance of the requested object is created.
Managing circular dependencies
By default, circular dependencies are not handled well (stack overflow...) due the default object life-cycle. To enable circular dependencies for a given object, at least one of the two objects must be defined as a singleton. This however will not yield the expected results, so it is highly recommended to define both objects involved in the circular dependency as singletons.
