Download the PHP package kassko/class-resolver-bundle without Composer
On this page you can find all versions of the php package kassko/class-resolver-bundle. 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 class-resolver-bundle
class-resolver-bundle
Bundle which integrates class-resolver into Symfony. Please for natives features, take a look at the class-resolver documentation.
Installation
You can install this component with composer
composer require kassko/class-resolver-bundle:some_version
You also need to register the bundle to your kernel:
There are two differents ways to use the class-resolver
Example of semantic configuration
You can define some class resolvers in semantic configuration and use them in you service configuration file
You can both define some class resolvers on the fly and feed them with pairs [class, service] all from your service configuration file
You register your service like pairs [class, service] to a resolver you create on the fly:
And you inject the good resolver (identified by it's group) in the concerned services:
A group is a way not to manipulate some service.
This way to do has the advantage to add some new resolvers without changing the semantic configuration and to use work with only one file (the service configuration file).
For more information about this last feature, please read the more detailed documentation
Finally, you can use some class resolvers defined on the semantic configuration and feed them from your service configuration file
You register your service like a pair [class, service] in the already existing resolver my_container_resolver_service_one:
You inject the resolver my_container_resolver_service_one in a service which need it:
All versions of class-resolver-bundle with dependencies
symfony/framework-bundle Version ^2.5|^3.0|^4.0|^5.0
kassko/class-resolver Version ^1.0