Prettier Plugin for Twig

Forked from trivago/prettier-plugin-twig-melody with focus on twig template only.

!Prettier Twig Banner
!Prettier Twig Banner

!GitHub Actions Workflow Status
!GitHub License

---

This Plugin enables Prettier to format .twig files, as well as .html.twig.

Installation

``bash
yarn add --dev @zackad/prettier-plugin-twig
`

Configuration

Add the plugin explicitly into your Prettier configuration (e.g., .prettierrc.json) using the plugins key:

`json
{
"plugins": ["@zackad/prettier-plugin-twig"]
}
`

Usage

`bash
./node_modules/.bin/prettier --write "*/.twig"
`

Options

This Prettier plugin comes with some options that you can add to your Prettier configuration (e.g., prettierrc.json).

$3

Values can be true or false. If true, single quotes will be used for string literals in Twig files.

$3

If set to true, objects will always be wrapped/broken, even if they would fit on one line:

`html
class="{{ {
base: css.prices
} | classes }}"
>
`

If set to false, this would be printed as:

`html



`

$3

Follow the standards described in https://twig.symfony.com/doc/2.x/coding_standards.html exactly. If set to false, some slight deviations might occur, such as spaces around the filter | operator (s | upper instead of s|upper).

$3

Choose whether to output the block name in {% endblock %} tags (e.g., {% endblock content %}) or not. The default is not to output it.

$3

An array of coherent sequences of non-standard Twig tags that should be treated as belonging together. Example (inspired by Craft CMS):

`json
{
"twigMultiTags": [
"nav,endnav",
"switch,case,default,endswitch",
"ifchildren,endifchildren",
"cache,endcache"
]
}
`

Looking at the case of nav,endnav, this means that the Twig tags {% nav %} and {% endnav %} will be treated as a pair, and everything in between will be indented:

`twig
{% nav entry in entries %}



{{ entry.title }}



{% endnav %}
`

If we did not list the "nav,endnav" entry in twigMultiTags, this code example would be printed without indentation, because {% nav %} and {% endnav %} would be treated as unrelated, individual Twig tags:

`twig
{% nav entry in entries %}



{{ entry.title }}



{% endnav %}
`

Note that the order matters: It has to be "nav,endnav", and it must not be "endnav,nav". In general, the first and the last tag name matter. In the case of "switch,case,default,endswitch", the order of case and default does not matter. However, switch has to come first, and endswitch has to come last.

$3

Make custom Twig tests known to the parser.

`json
{
"twigTestExpressions": [
"snake_case_test",
"camelCaseTest"
]
}
`

__Example__
`twig
{{ a is snake_case_test }}
{{ a is not snake_case_test }}
{{ a is camelCaseTest }}
{{ a is not camelCaseTest }}
`

Features

$3

When you are not happy with how Prettier formats a certain element or section in the code, you can tell it to leave it in peace:

`
{# prettier-ignore #}



`

You can also tell Prettier to leave entire regions as they are:

`
{# prettier-ignore-start #}
...
{# prettier-ignore-end #}
`

Testing

- You can call yarn test`to test against all regular tests

Credit

- Author: Tom Bartel