Download the PHP package hughnoble/injector without Composer
On this page you can find all versions of the php package hughnoble/injector. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download hughnoble/injector
More information about hughnoble/injector
Files in hughnoble/injector
Package injector
Short Description An easy to configure and flexible PSR-11 compliant IoC container for PHP
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 injector
Injector IoC
An easy to configure and flexible PSR-11 compliant IoC container for PHP.
Basic Usage
The most simple use case is as below.
Auto-Wiring
By default the container will automatically attempt to resolve any dependencies it can without them needing to be bound.
If the EntityManager class is instantiable (not an interface or abstract, and has no dependencies that can't be resolved) then the container will resolve it using the code below.
However if the dependency is an interface or abstract it will need binding. There are different ways to do this.
Auto-Wired Binding
The most common form of binding is by binding to a concrete so they can be auto wired.
Closure Binding
In this example the closure will be run every time this dependency is requested. This means that if two classes require it within the same process they will both get new instances.
Singleton Binding
In this case the closure within $childDependency will be run the first time it is requested and then cached. Subsequent calls will result in the same instance being returned.
Child dependencies for singletons can also be auto wire bindings. This is useful when you always want the same instance and isn't limited to interface binding.
By binding a class to itself as a singleton it ensures the same instance will always be returned.
Injecting the Container
The following reserved bindings can be used to access the container as a dependency.
Injector\Container and Psr\Container\ContainerInterface will always resolve to the instance of the container.
Injector\Binding\BindingMapInterface will always resolve to the binding map in use by the container.
This is useful when you might want programmatic binding through providers.
