Download the PHP package nassau/registry-compiler without Composer

On this page you can find all versions of the php package nassau/registry-compiler. 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?

Example code of nassau/registry-compiler

Informations about the package registry-compiler

Tag your services to associate them with one common registry

Add the nassau.registry tag to a service and it will receive a collection of other services tagged with the name you chose. Similar to the event dispatcher, cache warmers, twig extensions, etc.

If you ever created a CompilerPass and used $containerBuilder->findTaggedServiceIds() inside you could probably replace it with nassau/registry-compiler.

Installation

Add the compiler pass to one of your bundles. Since it may be used in some of your dependencies, the recommended way is to use the register method of the Pass to ensure only one instance is registered.

Usage

Example

Given an interface:

You may need to split the implementation across multiple classes. Maybe it’s something like a monolog processor — each one does it’s thing and moves on. To simplify the usage, you create a chain implementation so the classes using FooBarInterface knows nothing about the details:

So far so good. So now you just need to wire every implementations together using the container. As long as you have a fixed number of implementations you may just use calls:

But this gets messy and there is no easy way to add more implementations, especially if you’re only making a library / architecture and it’s up to the developer to make the implementations.

This is where nassau.registry comes into play. Instead of manually connecting the implementations to the chain, you register a tag, so any service can hook itself up:

All versions of registry-compiler with dependencies

PHP Build Version
Package Version
Requires symfony/symfony Version ~2.3 | ~3.0
symfony/options-resolver 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 nassau/registry-compiler contains the following files

Loading the files please wait ....