Showing 10 of 1,214 results.

Parser Nodes Overview

The document parser returns a list of nodes as a result of parsing. There are many different types available, depending on the input template. The most basic node type is the LiteralNode , representing the template's non-Blade parts. If an input...

parse | The Document Parser

Parses the input document and returns an array of nodes. Argument Description $document The input document. 1 <?php 2 3 public function parse ( 4 string $ document 5 ) : array ;

Part Two: Creating a Custom Pagination View in Laravel

This is part two of two in a series of posts on how to create a custom pagination view in Laravel. Before reading this part, it is highly recommended that your first read Part One: Creating a Custom Pagination View in Laravel of this series. In...

Part One: Creating a Custom Pagination View in Laravel

Update You can view the completed part two of this article by visiting Part Two: Creating a Custom Pagination View in Laravel In this post we are going to look at building a custom paginator view in Laravel 4. There are quite a few posts are the...

se_capture Tag

The se_capture tag can be used to store the results of a template section, and output it later as a string. This is particularly helpful if you want to reuse the results of a partial, or navigation menu in multiple places without having to render...

Custom Component Tags

The document parser supports registering custom component tag prefixes. By default, the parser is configured to parse elements beginning with <x- , <x: , </x , or </x: as Blade component tags; this behavior cannot be changed. However, we can add...

Configuring the Blade Parser | Formatter Configuration and Usage

You may optionally configure the Blade parser by creating a file named .blade.format.json at the root of your project. The options that can be used currently are: customIfs, : A list of custom if statements. These provide hints to the parser and...

Comment Nodes | Parser Nodes Overview

The parser will emit Stillat\BladeParser\Nodes\CommentNode instances when it successfully parses a Blade comment. If a comment is not completed, the start of the comment will become part of a LiteralNode instance. The following sample document...

Filter Search