| /plugin/findologicxmlexport/vendor/twig/twig/doc/functions/ |
| H A D | date.rst | 10 Converts an argument to a date to allow date comparison:
20 You can pass a timezone as the second argument:
|
| H A D | dump.rst | 7 The ``dump`` function dumps information about a template variable. This is
8 mostly useful to debug a template that does not behave as expected by
29 information on a production server).
31 In an HTML context, wrap the output with a ``pre`` tag to make it easier to
42 Using a ``pre`` tag is not needed when `XDebug`_ is enabled and
43 ``html_errors`` is ``on``; as a bonus, the output is also nicer with
|
| H A D | include.rst | 7 The ``include`` function returns the rendered content of a template:
40 And if the expression evaluates to a ``\Twig\Template`` or a
60 You can also provide a list of templates that are checked for existence before
70 When including a template created by an end user, you should consider
|
| H A D | max.rst | 7 ``max`` returns the biggest value of a sequence or a set of values:
14 When called with a mapping, max ignores keys and only compares values:
18 {{ max({2: "e", 1: "a", 3: "b", 5: "d", 4: "c"}) }}
|
| H A D | min.rst | 7 ``min`` returns the lowest value of a sequence or a set of values:
14 When called with a mapping, min ignores keys and only compares values:
18 {{ min({2: "e", 3: "a", 1: "b", 5: "d", 4: "c"}) }}
19 {# returns "a" #}
|
| H A D | parent.rst | 4 When a template uses inheritance, it's possible to render the contents of the
5 parent block when overriding a block by using the ``parent`` function:
|
| H A D | random.rst | 13 The ``random`` function returns a random value depending on the supplied
16 * a random item from a sequence;
17 * a random character from a string;
18 * a random integer between 0 and the integer parameter (inclusive).
19 * a random integer between the integer parameter (when negative) and 0 (inclusive).
20 * a random integer between the first integer and the second integer parameter (inclusive).
|
| H A D | range.rst | 4 Returns a list containing an arithmetic progression of integers:
27 Note that if the start is greater than the end, ``range`` assumes a step of
39 function (with a step of ``1``, or ``-1`` if the start is greater than the end):
|
| H A D | source.rst | 10 The ``source`` function returns the content of a template without rendering it:
|
| H A D | template_from_string.rst | 7 The ``template_from_string`` function loads a template from a string:
27 takes a template as an argument (like the ``embed`` or ``extends`` tags).
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/ |
| H A D | installation.rst | 55 improvements. Note that the extension is not a replacement for the PHP
56 code; it only implements a small part of the PHP code to improve the
60 Twig comes with a C extension that enhances the performance of the Twig
|
| H A D | internals.rst | 12 The rendering of a Twig template can be summarized into four key steps:
19 * Then, the **parser** converts the token stream into a meaningful tree
29 The lexer tokenizes a template source code into a token stream (each token is
44 You can manually convert a source code into a token stream by calling the
53 As the stream has a ``__toString()`` method, you can have a textual
78 The parser converts the token stream into an AST (Abstract Syntax Tree), or a
82 You can manually convert a token stream into a node tree by calling the
87 Echoing the node object gives you a nice representation of the tree::
112 The last step is done by the compiler. It takes a node tree as an input and
115 You can manually compile a node tree to PHP code with the ``compile()`` method
[all …]
|
| H A D | intro.rst | 17 * *Secure*: Twig has a sandbox mode to evaluate untrusted template code. This
18 allows Twig to be used as a template language for applications where users
21 * *Flexible*: Twig is powered by a flexible lexer and parser. This allows the
26 Slim, Yii, Laravel, Codeigniter and Kohana — just to name a few.
52 This section gives you a brief introduction to the PHP API for Twig.
65 Twig uses a loader (``\Twig\Loader\ArrayLoader``) to locate templates, and an
68 The ``render()`` method loads the template passed as a first argument and
69 renders it with the variables passed as a second argument.
71 As templates are generally stored on the filesystem, Twig also comes with a
|
| H A D | recipes.rst | 60 process a lot.
81 When including a template, its name does not need to be a string. For
107 template it finds in a list of configured directories; a template found in a
111 (aka a template in a directory further in the list)?
201 When Twig encounters a variable like ``article.title``, it tries to find a
272 When a function (or a filter) is not defined, Twig defaults to throw a
274 valid PHP callable) which should return a function (or a filter).
303 When template code is provided by a third-party (through a web interface for
511 Loading a Template from a String
514 From a template, you can easily load a template stored in a string via the
[all …]
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/tags/ |
| H A D | autoescape.rst | 4 Whether automatic escaping is enabled or not, you can mark a section of a
|
| H A D | deprecated.rst | 7 Twig generates a deprecation notice (via a call to the ``trigger_error()``
8 PHP function) where the ``deprecated`` tag is used in a template:
16 Also you can deprecate a block in the following way:
|
| H A D | embed.rst | 11 included template, like when extending a template.
13 Think of an embedded template as a "micro layout skeleton".
34 Since the use case may not be obvious, let's look at a simplified example.
35 Imagine a base template shared by multiple HTML pages, defining a single block
71 While other pages ("boom" and "baz") share a different content structure -
99 These two solutions do not scale well because they each have a major drawback:
102 we add a sidebar, which may again contain different, recurring structures
112 In such a situation, the ``embed`` tag comes in handy. The common layout
113 code can live in a single base template, and the two different content structures,
174 instance, if you embed a CSS/JavaScript template into an HTML one). In that
|
| H A D | extends.rst | 4 The ``extends`` tag can be used to extend a template from another one.
12 Let's define a base template, ``base.html``, which defines a simple HTML
29 © Copyright 2011 by <a href="http://domain.invalid/">you</a>.
38 All the ``block`` tag does is to tell the template engine that a child
73 template. This limitation exists because a block tag works in "both"
74 directions. That is, a block tag doesn't just provide a hole to fill - it also
79 If you want to print a block multiple times you can however use the
156 If the variable evaluates to a ``\Twig\Template`` or a ``\Twig\TemplateWrapper``
173 first template that exists will be used as a parent:
196 A block provides a way to change how a certain part of a template is rendered
[all …]
|
| H A D | filter.rst | 4 Filter sections allow you to apply regular Twig filters on a block of template
|
| H A D | for.rst | 4 Loop over each item in a sequence. For example, to display a list of users
5 provided in a variable called ``users``:
21 If you do need to iterate over a sequence of numbers, you can use the ``..``
36 {% for letter in 'a'..'z' %}
44 {% for letter in 'a'|upper..'z'|upper %}
50 If you need a step different from 1, you can use the ``range`` function
56 Inside of a ``for`` loop block you can access some special variables:
82 looping with a condition.
87 Adding a condition
117 If no iteration took place because the sequence was empty, you can render a
[all …]
|
| H A D | if.rst | 45 <p>It's a nice day for a walk in the park.</p>
|
| H A D | import.rst | 8 into a variable or request specific macros from it.
10 Imagine we have a helper module that renders forms (called ``forms.html``):
22 The easiest and most flexible is importing the whole module into a variable.
|
| H A D | include.rst | 4 The ``include`` statement includes a template and returns the rendered content
17 same features with a bit more flexibility:
19 * The ``include`` function is semantically more "correct" (including a
20 template outputs its rendered contents in the current scope; a tag should
23 * The rendered template can be more easily stored in a variable when using
66 When including a template created by an end user, you should consider
77 And if the expression evaluates to a ``\Twig\Template`` or a
106 You can also provide a list of templates that are checked for existence before
|
| H A D | macro.rst | 13 Here is a small example of a macro that renders a form element:
21 Each argument can have a default value (here ``text`` is the default value for
35 Macros differ from native PHP functions in a few ways:
37 * Arguments of a macro are always optional.
39 * If extra positional arguments are passed to a macro, they end up in the
40 special ``varargs`` variable as a list of values.
62 macros, or a template and some macros), and import the functions as items of
83 When you define a macro in the template where you are going to use it, you
85 of importing it; even if seems to work, this is just a side-effect of the
88 When you want to use a macro in another macro from the same file, you need to
|
| H A D | sandbox.rst | 21 cannot be used to sandbox a section of a template. The following example
|