Download the PHP package matthiasnoback/symfony-bundle-plugins without Composer

On this page you can find all versions of the php package matthiasnoback/symfony-bundle-plugins. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package symfony-bundle-plugins

Symfony Bundle Plugins

By Matthias Noback

Build Status Coverage Status

This package helps you create extensible bundles, by introducing a plugin system for bundles. Each bundle plugin can define its own services and configuration. This basically makes your bundles conform to the open/closed principle.

Setup

Install this library in your project by running

composer require matthiasnoback/symfony-bundle-plugins

Example

First, your bundle should extend BundleWithPlugins. You need to implement the getAlias method. It should return the name of your bundle's configuration key (as it will be used in config.yml for instance).

Each plugin for the bundle should implement BundlePlugin:

When instantiating this bundle in your AppKernel class, you can provide any number of BundlePlugin instances:

If some of the plugins are required, just introduce a CorePlugin and make sure it is always registered by overriding your bundle's alwaysRegisteredPlugins() method:

Register compiler passes

When a bundle plugin needs to register a compiler pass, it can do so in its build() method.

Booting a plugin

Whenever the main bundle is booted, plugins are allowed to do some runtime initialization as well. They can do this in their boot() method. At that time, the fully initialized service container is available:

Simple plugins

If your plugin is quite simple (i.e. only needs a load() method), just make the plugin class extend SimpleBundlePlugin which contains stub implementations for the interface methods that you won't need.

Thanks

To @dennisdegreef for reviving the test suite of this project.


All versions of symfony-bundle-plugins with dependencies

PHP Build Version
Package Version
Requires php Version >=5.3
symfony/http-kernel Version ^2.3|^3.0
symfony/dependency-injection Version ^2.3|^3.0
symfony/config Version ^2.3|^3.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package matthiasnoback/symfony-bundle-plugins contains the following files

Loading the files please wait ....