Searched refs:any (Results 751 – 775 of 1506) sorted by path
1...<<31323334353637383940>>...61
| /plugin/findologicxmlexport/vendor/twig/extensions/ |
| H A D | LICENSE | 3 Permission is hereby granted, free of charge, to any person obtaining a copy
|
| /plugin/findologicxmlexport/vendor/twig/extensions/doc/ |
| H A D | date.rst | 41 or ``diff.in.XXX`` where ``XXX`` can be any valid unit: second, minute, hour, day, month, year.
|
| H A D | i18n.rst | 16 Note that you must configure the ``gettext`` extension before rendering any
|
| /plugin/findologicxmlexport/vendor/twig/extensions/test/Twig/Tests/Extension/ |
| H A D | TextTest.php | 23 ->expects($this->any())
|
| /plugin/findologicxmlexport/vendor/twig/twig/ |
| H A D | CHANGELOG | 485 * added the ability to use any PHP callable to define filters, functions, and tests
595 * fixed a regression when a template only extends another one without defining any blocks
657 * allowed hash keys to be any expression
692 …nction/addGlobal/addTest/addNodeVisitor/addTokenParser/addExtension can now be called in any order)
874 * changed trans tag to accept any variable for the plural count
936 * changed the date filter to support any date format supported by DateTime
951 * fixed node visiting for macros (macros are now visited by visitors as any other node)
965 As for any new release, don't forget to remove all cached templates after
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/ |
| H A D | advanced.rst | 114 A global variable is like any other template variable, except that it's
255 the ``*`` can be any string::
814 any valid PHP callable:
938 precedence over any other registered extensions::
|
| H A D | advanced_legacy.rst | 115 A global variable is like any other template variable, except that it's
267 the ``*`` can be any string::
334 as the ``*`` can be any string::
|
| H A D | api.rst | 43 the evaluated templates. For such a need, you can use any available PHP
140 the template filename extension (this strategy does not incur any overhead at
270 ``\Twig\Loader\ChainLoader`` accepts any loader that implements
435 * Escaping is applied before printing, after any other filter is applied:
468 individual variables (so, the ``raw`` filter won't have any effect here).
|
| H A D | coding_standards.rst | 16 When using the whitespace control character, do not put any spaces between
45 * Do not put any spaces after an opening parenthesis and before a closing
52 * Do not put any spaces before and after string delimiters:
59 * Do not put any spaces before and after the following operators: ``|``,
69 * Do not put any spaces before and after the parenthesis used for filter and
77 * Do not put any spaces before and after the opening and the closing of arrays
|
| H A D | installation.rst | 61 runtime engine; install it like any other PHP extensions:
|
| H A D | intro.rst | 7 If you have any exposure to other text-based template languages, such as
|
| H A D | recipes.rst | 67 any valid expression, you can pass a variable that evaluates to ``true`` when
91 As a matter of fact, the template name can be any valid expression, such as
273 ``\Twig\Error\SyntaxError`` exception. However, it can also call a `callback`_ (any
335 This method won't catch any sandbox policy violations because the policy
495 filesystem, or any other loader for that matter: the template name should be a
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/filters/ |
| H A D | escape.rst | 50 applied to any string being inserted into CSS and escapes everything except
|
| H A D | slice.rst | 19 You can use any valid expression for both the start and the length:
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/functions/ |
| H A D | attribute.rst | 26 notation, except that the item can be any valid expression.
|
| H A D | cycle.rst | 15 The array can contain any number of values:
|
| H A D | dump.rst | 52 If you don't pass any value, all variables from the current context are
|
| H A D | template_from_string.rst | 26 with the ``include`` function, you can use it with any tag or function that
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/tags/ |
| H A D | embed.rst | 10 does. But it also allows you to override any block defined inside the
108 consequences: any change involves finding and editing all affected copies
|
| H A D | extends.rst | 182 As the template name for the parent can be any valid Twig expression, it's
197 but it does not interfere in any way with the logic around it.
|
| H A D | for.rst | 40 The ``..`` operator can take any expression at both sides:
|
| H A D | include.rst | 34 * The ``include`` function does not impose any specific order for
70 The template name can be any valid Twig expression:
|
| H A D | macro.rst | 53 Macros can be defined in any template, and need to be "imported" before being
|
| H A D | set.rst | 14 any other ones:
21 The assigned value can be any valid :ref:`Twig expression
|
| H A D | use.rst | 69 The main template can also override any imported block. If the template
123 You can use as many ``use`` statements as you want in any given template.
|
1...<<31323334353637383940>>...61