bapcat/facade

Pseudo-static accessors for Phi bindings

, _(*1)

Phi Facades

Facades are a way to make Phi bindings feel more natural., _(*2)

Installation

Composer

Composer is the recommended method of installation for Facade., _(*3)

$ composer require bapcat/facade

GitHub

Facade may be downloaded from GitHub., _(*4)

Features

Pseudo-Static Access To Phi Singletons

A common use-case for Phi Facades is logging:, _(*5)

namespace Vendor\Package\Logging;

class Logger {
  public function warning($text) {
    // ...
  }
}

$logger = new Vendor\Package\Logging\Logger;

$phi = BapCat\Phi\Phi::instance();
$phi->bind('core.log', $logger);

use BapCat\Facade\Facade;

class Log extends Facade {
  protected static $_binding = 'core.log';
}

Once the facade is set up, the Vendor\Package\Logging singleton can be accessed like this:, _(*6)

Log::warning('Something bad happened!');

Phi Facades can even be used to create a facade for Phi:, _(*7)

$phi = BapCat\Phi\Phi::instance();
$phi->bind('phi', $phi);

use BapCat\Facade\Facade;

class Phi extends Facade {
  protected static $_binding = 'phi';
}

This will allow Phi to be accessed as such:, _(*8)

Phi::bind('Bar', 'Foo');
$foo = Phi::make('Bar');

Phi Custom Resolvers

If you are using Phi 1.2.0 or greater, Phi facades will work seamlessly with custom resolvers., _(*9)