Download the PHP package hafo/di without Composer
On this page you can find all versions of the php package hafo/di. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 di
Hafo DI
What is this?
This is a small PHP Dependency Injection Container with autowiring and as little configuration as possible.
It extends Psr\Container\ContainerInterface and provides some goodies to help accelerate development.
How do I install this?
Via Composer:
PHP version 7.1 or higher is required.
How to use?
The easiest way is to use the ContainerBuilder class:
Adding service factories
You can add services via ContainerBuilder:
It is recommended to use the classnames as identifiers as these can be used for autowiring, if enabled. Also, it's best practice.
Parameter can be an array, or any iterable really, as long as it provides both the keys and the factory callbacks.
Decorating services
A decorator is a simple callback that gets called when a service is created. It can be used to modify the service before returning it.
Decision whether a decorator should be used for a service is done via simple is_a() check,
so you can easily decorate multiple services that implement same interface, for example.
The container makes sure that each decorator gets called only once for each service instance.
Adding parameters
You can also add parameters:
Parameters are then registered in the DI container and can be accessed via the get() method, just like the services.
Using autowiring
If you want to avoid writing many factories by hand, you can use autowiring. Just make sure that the constructor arguments for your service are resolvable, which means that all the dependencies must be instantiable using the DI container or they must have default values.
You can use Hafo\DI\Autowiring\AutowiringCache\NetteCache instead of MemoryCache if you use the nette/caching package.
You can also implement your own Hafo\DI\Autowiring\AutowiringCache or even Hafo\DI\Autowiring.
Interface-implementation map
It is good practice to use interfaces for your services. The DI container however doesn't know by default which specific class you want to return. We need to specify it:
Reusable modules
You can create self-contained reusable modules simply by implementing the Hafo\DI\Module interface.
Making the module work in your project is then as easy as instantiating it and calling a method install,
passing the builder as an argument.
