Check Jinja2 templates for syntax, formatting and documentation issues. The following aspects are being looked at:
* Variable spacing: Variable tags should be padded with one space on each side, like this: {{ var_name }}. This can be set to any number of spaces via the setting variable_spacing. Malformatted variable tags are detected and fixes suggested. * Control spacing: Like variable spacing, but for control blocks, i.e. if and for constructs. Looks at both start and end block. * Control labels: It is good practice to label the end of an if or for construct with a comment equal to the content of the start, like so::
{% for x in y %} do something {% endfor %}{# for x in y %}
Mising or differing labels are detected and fixes suggested. Constructs with start and end on the same line are being ignored. * unbalanced blocks: Each opening tag for a for or if construct must be closed by a corresponding end tag. An unbalanced number of opening and closing tags is invalid syntax and will be reported with MAJOR severity by the bear.
- Jinja2
| Setting | Meaning |
|---|---|
control_spacing |
The number of spaces a control block should be spaced with. Default is 1. (Optional, defaults to '1'.) |
variable_spacing |
The number of spaces a variable block should be spaced with. Default is 1. (Optional, defaults to '1'.) |
- Documentation
- Formatting
- Syntax
- Documentation
- Formatting
AGPL-3.0
- The coala developers ([email protected])