| Package Data | |
|---|---|
| Maintainer Username: | brightmachine |
| Maintainer Contact: | conar@welshlabs.com (Conar Welsh) |
| Package Create Date: | 2014-09-20 |
| Package Last Update: | 2017-12-12 |
| Language: | PHP |
| License: | MIT |
| Last Refreshed: | 2024-11-22 03:04:46 |
| Package Statistics | |
|---|---|
| Total Downloads: | 14,211 |
| Monthly Downloads: | 27 |
| Daily Downloads: | 0 |
| Total Stars: | 12 |
| Total Watchers: | 3 |
| Total Forks: | 7 |
| Total Open Issues: | 0 |
A Laravel wrapper for mustache.php, a PHP implementation of http://mustache.github.io/
This project is based entirely on the the mustache-l4 package by Conar Welsh and contributors.
Laravel 5
mustache/mustache 2.7+
Add laratash as a dependency to your composer.json file:
"require": {
"laravel/framework": "~5.0",
"brightmachine/laratash": "~5.0"
}
run composer update, or composer install if this is a brand new project
Open: config/app.php
...
'Laratash\LaratashServiceProvider',
...
You are all setup!
Laratash is merely a wrapper for the Mustache.php library that integrates it into Laravel 5+.
Laratash registers itself with the Laravel View class, providing seamless integration with Laravel. You can use Mustache just as you would Blade!
The Laravel View class will choose the right template engine to use based on the file extension of the view. So all you have to do to render Mustache files, is ensure that your view has a .mustache file extension. Laratash will take care of the rest.
You can even mix and match template engines. For instance maybe you have a Blade layout file, and you want to nest a Mustache view, that's fine! However just be aware of the fact that Mustache does not understand Block Sections like Blade does. The Mustache view will be rendered into a variable named whatever section you passed the view to. So for example if you were to do:
$view->nest('content', 'some.view');
$view->nest('sidebar', 'some.sidebar');
The contents of the parsed some.view file will be available in the template file under a variable called $content.
The contents of the parsed some.sidebar would be available in the template file, under a variable called $sidebar.
By default, Mustache partials are also loaded using Laravel's ViewFinder, so you can feel free to use dot-notation to specify a view.
{{#posts}}
{{> posts._post}}
{{/posts}}
Other than that it is business as usual!
Example using View::make()
app/views/test.mustache
<h1>{{ pageHeading }}</h1>
<div>
{{ pageContent }}
</div>
app/router.php
Route::get('/', function()
{
return View::make('test', array(
'pageHeading' => 'Rendered with Mustache.php',
'pageContent' => 'But still looks like Laravel!'
));
});
Example using a Blade controller layout
app/views/layouts/master.blade.php
<html>
<head></head>
<body>
{{-- since Mustache does not use sections, the nested section will instead
be rendered as a variable --}}
{{ content }}
</body>
</html>
app/views/test.mustache
<h1>{{ pageHeading }}</h1>
<div>
{{ pageContent }}
</div>
app/controllers/TestController.php
<?php
class TestController extends BaseController {
public $layout = 'layouts.master';
public function index()
{
$this->layout->nest('content', 'test', array(
'pageHeading' => 'Rendered with Mustache.php',
'pageContent' => 'But still looks like Laravel!'
));
}
}
Example using a Mustache layout
app/views/posts/_post.mustache
<article>
<h2>{{ title }}</h2>
<div>
{{ content }}
</div>
</article>
app/views/blog/index.mustache
<html>
<head></head>
<body>
<h1>My Blog</h1>
{{#posts}}
{{> posts._post}}
{{/posts}}
</body>
</html>
app/routes.php
Route::get('/', function()
{
$posts = array(
array(
'title' => 'This is a Title',
'content' => 'lorem ipsum...'
),
array(
'title' => 'This is a another title',
'content' => 'lorem ipsum...'
),
array(
'title' => 'This is yet another Title',
'content' => 'lorem ipsum...'
),
);
return View::make('blog.index', compact('posts));
});
Laravel expects view data to be be passed as an array.
Mustache PHP, however, also allows a Context object to be used.
If you wish to use a Context object, pass through an array with a __context key and this will be used. E.g.
`return view('my.view', ['__context' => new Context]);`
You can alter the configuration options that are passed to Mustache.php in your ConfigServiceProvider. E.g.
config([
'laratash.cache' => storage_path() . '/framework/views/mustache',
]);
All laratash. options are passed directly to the Mustache_Engine constructor, so you can use any of the options that you would use with Mustache.php