Download the PHP package mmoreram/symfony-bundle-dependencies without Composer
On this page you can find all versions of the php package mmoreram/symfony-bundle-dependencies. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mmoreram/symfony-bundle-dependencies
More information about mmoreram/symfony-bundle-dependencies
Files in mmoreram/symfony-bundle-dependencies
Package symfony-bundle-dependencies
Short Description Dependencies resolver for Symfony Bundles
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 symfony-bundle-dependencies
Symfony Bundle Dependencies
The minimum requirements of this bundle is PHP 7.1 and Symfony 3.2 because the bundle is using features on both versions. If you're not using them yet, I encourage you to do it.
This package provides a very simple way of adding dependencies between Symfony Bundles. Composer defines these definitions in a very soft layer, only downloading these dependent packages. Bundles should as well force other Bundles to be instanced in the application to comply with Dependency Injection dependencies.
- For your bundle
- For your kernel
- Performance
- The order
For your Bundle
If you want your bundles to provide this feature, then is as simple as make your bundles implement an interface. That simple.
Take in account that this addition will only provide compatibility with projects using this project, and will not affect anyway projects not using it.
Maybe one of your bundle dependencies need an specific value in the constructor. Well, this is a very very weird case, and you should definitely avoid it, but you can do it by adding the instance instead of the namespace.
By default, all bundles defined as their namespace are instanced with the kernel object as first parameter, so doing something like that doesn't really have sense at all.
As you will see later, using instances instead of names will remove the possibility of using cache in the final project.
For your Kernel
In your project, you should be able to resolve all these dependencies. This is why this package offers you as well a way of doing that in your kernel.
In that case, you can pass as well instances of bundles instead of strings.
Performance
As you may see, resolving dependencies can penalize a lot your website performance. Each time your Kernel is booted, all dependencies are resolved once and again, and this has no sense at all.
This package offers you as well a cache layer, reducing to 0 from the second time your Kernel is booted and until your next deployment (cache file is stored in Kernel cache folder).
One simple change to your code. That easy.
Caching your bundle dependencies resolution can only be used when all dependencies are defined as strings instead of instances.
This library assumes that, as soon as something changes in your project that can change the dependencies file, you will remove cache. Just take it in account.
The order
Of course, the order matters. If two of your dependencies instantiate the same bundle with different parameters, then the first one to be defined will be the winner. In that case, if you want to explicitly define how a bundle must be instantiated even if other dependencies do, add this bundle at the beginning of your array.
This is also applied when defining the bundle dependencies.
