Download the PHP package php-di/slim-bridge without Composer
On this page you can find all versions of the php package php-di/slim-bridge. 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 slim-bridge
PHP-DI integration with Slim
This package configures Slim to work with the PHP-DI container.
The full documentation is here: http://php-di.org/doc/frameworks/slim.html
Why?
PHP-DI as a container
The most obvious difference with the default Slim installation is that you will be using PHP-DI as the container, which has the following benefits:
- autowiring
- powerful configuration format
- support for modular systems
- ...
If you want to learn more about all that PHP-DI can offer have a look at its introduction.
Controllers as services
While your controllers can be simple closures, you can also write them as classes and have PHP-DI instantiate them only when they are called:
Dependencies can then be injected in your controller using autowiring, PHP-DI config files or even annotations.
Controller parameters
By default, Slim controllers have a strict signature: $request, $response, $args. The PHP-DI bridge offers a more flexible and developer friendly alternative.
Controller parameters can be any of these things:
- the request or response (parameters must be named
$requestor$response) - route placeholders
- request attributes
- services (injected by type-hint)
You can mix all these types of parameters together too. They will be matched by priority in the order of the list above.
Request or response injection
You can inject the request or response in the controller parameters by name:
As you can see, the order of the parameters doesn't matter. That allows to skip injecting the $request if it's not needed for example.
Route placeholder injection
As you can see above, the route's URL contains a name placeholder. By simply adding a parameter with the same name to the controller, PHP-DI will directly inject it.
Request attribute injection
As you can see above, a middleware sets a name attribute. By simply adding a parameter with the same name to the controller, PHP-DI will directly inject it.
Service injection
To inject services into your controllers, you can write them as classes. But if you want to write a micro-application using closures, you don't have to give up dependency injection either.
You can inject services by type-hinting them:
Note: you can only inject services that you can type-hint and that PHP-DI can provide. Type-hint injection is simple, it simply injects the result of
$container->get(/* the type-hinted class */).
Documentation
The documentation can be read here: http://php-di.org/doc/frameworks/slim.html
All versions of slim-bridge with dependencies
php-di/php-di Version ^6.0|^7.0
php-di/invoker Version ^2.0.0
slim/slim Version ^4.2.0