enzyme/laravel-binder

A service container contextual binding helper for Laravel 5.

v1.0.0 2016-04-03 07:55 UTC

Requires

• php: >=5.5.0
• illuminate/contracts: ^5.2

Requires (Dev)

• mockery/mockery: ^0.9.4
• phpunit/phpunit: ^4.8
• satooshi/php-coveralls: ^0.6.1

MIT

• Tristan Strathearn

• container
• php
• service
• laravel
• contextual
• binding
• enzyme

README

A contextual binding helper for Laravel 5.

Example

From the service provider.

use Enzyme\LaravelBinder\Binder;

// Inside the app service provider...
public function register()
{
    $binder = new Binder($this->app);

    $binder->setAlias(
        'controller.listing',
        'App\Http\Controllers\ListingController'
    );

    $binder->setAlias(
        'repos.interface',
        'Acme\Repositories\RepositoryInterface'
    );

    // Option 1 for binding, using aliases.
    $binder->setBinding(
        'repos.listing',
        'repos.interface',
        'Acme\Repositories\ListingRepository'
    );

    // Option 2 for binding, using FQNs.
    $binder->setBinding(
        'factories.listing',
        'Acme\Factories\FactoryInterface',
        'Acme\Factories\ListingFactory'
    );

    // Tell the service container that the ListingController
    // needs the ListingRepository & ListingFactory.
    $binder->setNeeds(
        'controller.listing',
        ['repos.listing', 'factories.listing']
    );

    $binder->register();
}

From the controller

// You don't need to inject the specific concrete classes, just the
// interfaces. The Binder + Service Container has taken care of it for you.
public function __construct(RepositoryInterface $repo, FactoryInterface $factory)
{
    $this->repo = $repo;
    $this->factory = $factory;
}

What's the purpose?

With your service provider(s) now being the sole authority for which classes get what implementations, if you ever need to switch those implementations, it's dead simple and in one spot!