Allows you to use Twig seamlessly in Laravel 4.

Add rcrowe\twigbridge as a requirement to composer.json:

{
    "require": {
        "rcrowe/twigbridge": "0.5.*"
    }
}

Update your packages with composer update or install with composer install.

Once Composer has installed or updated your packages you need to register TwigBridge with Laravel itself. Open up app/config/app.php and find the providers key towards the bottom and add:

'TwigBridge\TwigServiceProvider'

TwigBridge's configuration file can be extended by creating app/config/packages/rcrowe/twigbridge/config.php. You can find the default configuration file at vendor/rcrowe/twigbridge/src/config/config.php.

You can quickly publish a configuration file by running the following Artisan command.

$ php artisan config:publish rcrowe/twigbridge

You call the Twig template like you would any other view:

// Without the file extension
View::make('i_am_twig', array(...))

TwigBridge also supports views in other packages:

View::make('pagination::simple')

The above rules continue when extending another Twig template:

{% extend "parent" %}
{% extend "pagination::parent" %}

Sometimes you want to extend / add new functions for use in Twig templates. Add to the exensions array a list of extensions for Twig to load.

'extensions' => array(
    'TwigBridge\Extensions\Example'
)

TwigBridge supports both a string or a closure as a callback, so for example you might implement the Assetic Twig extension as follows:

'extensions' => array(
    function($app) {
        $factory = new Assetic\Factory\AssetFactory($app['path'].'/../some/path/');
        $factory->setDebug(false);
        // etc.....
        return new Assetic\Extension\Twig\AsseticExtension($factory);
    }
)

TwigBridge comes with the following extensions:

• TwigBridge\Extensions\AliasLoader
• TwigBridge\Extensions\HelperLoader

These extensions are configured by default:

• Twig_Extension_Debug
• TwigBridge\Extensions\AliasLoader
• TwigBridge\Extensions\HelperLoader

The AliasLoader extension allows you to call any class that has been aliased in your app/config/app.php file. This gives your Twig templates integration with any Laravel class as well as any other classes you alias.

To use the Laravel integration (or indeed any aliased class and method), your function in Twig must use the format class_method(...). So the Twig function {{ url_to(...) }} will call the class and method URL::to(...).

You can define shortcuts to these by changing the alias_shortcuts config parameter. For example, calling url(...) is actually an alias to url_to(...).

The HelperLoader extension exposes Laravel helpers as both Twig functions and filters.

Check out the config file to see a list of defined function / filters. You can also add your own.

TwigBridge fires the twigbridge.twig event just before the TwigEngine is registered, this gives other packages or your application time to alter Twigs behaviour; maybe another package wants to add an extension or change the lexer used. To do this just register and event handler:

Event::listen('twigbridge.twig', function($twig) {
    $twig->addExtension( new TwigBridge\Extensions\Example );
});

TwigBridge offers a number of CLI interactions.

List Twig & Bridge versions:

$ php artisan twig

Empty the Twig cache:

$ php artisan twig:clean

Pre-compile Twig templates:

$ php artisan twig:compile

Check syntax of Twig templates:

$ php artisan twig:lint