Package Data | |
---|---|
Maintainer Username: | gencer |
Maintainer Contact: | barryvdh@gmail.com (Barry vd. Heuvel) |
Package Create Date: | 2014-08-04 |
Package Last Update: | 2014-08-04 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-17 03:05:47 |
Package Statistics | |
---|---|
Total Downloads: | 28 |
Monthly Downloads: | 1 |
Daily Downloads: | 0 |
Total Stars: | 0 |
Total Watchers: | 2 |
Total Forks: | 0 |
Total Open Issues: | 0 |
Allows you to use Twig seamlessly in Laravel 4.
NOTE: This is a fork of current TwigBridge by Robert Crowe. I maintained this because the current beta stage forces us to use dev branch of all repos. I do not want to use dev branch for all components, personally :)
Add gencer/twigbridge-laravel-4
as a requirement to composer.json:
{
"require": {
"gencer/twigbridge-laravel-4": "0.6.*"
}
}
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\ServiceProvider'
You can add the TwigBridge Facade, to have easier access to the TwigBridge (or Twig_Environment).
'Twig' => 'TwigBridge\Facade\Twig',
Twig::addExtension('TwigBridge\Extension\Loader\Functions');
Twig::render('mytemplate', $data);
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" %}
You can call functions with parameters:
{{ link_to_route('tasks.edit', 'Edit', task.id, {'class': 'btn btn-primary'}) }}
And output variables, escaped by default. Use the raw
filter to skip escaping.
{{ some_var }}
{{ html_var | raw }}
{{ long_var | str_limit(50) }}
Sometimes you want to extend / add new functions for use in Twig templates. Add to the enabled
array in config/extensions.php 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 enabled by default:
To enable '0.5.x' style Facades, enable the Legacy Facades extension:
These loader extensions exposes Laravel helpers as both Twig functions and filters.
Check out the config/extensions.php file to see a list of defined function / filters. You can also add your own.
The FacadeLoader extension allows you to call any facade you have configured in config/extensions.php. 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), just add your facades to the config and call them like URL.to(link)
(instead of URL::to($link)
)
The following helpers/filters are added by the default Extensions. They are based on the helpers and/or facades, so should be self explaining.
Functions:
Filters:
Global variables:
TwigBridge offers a command for CLI Interaction.
Empty the Twig cache:
$ php artisan twig:clean
Lint all Twig templates:
$ php artisan twig:lint