-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
var-spacing rule triggers even if in warn_list #2301
Labels
Comments
---
exclude_paths:
- .git/
- .github/
- tests/
enable_list:
- fqcn-builtins
warn_list:
- jinja[spacing] # Rule that looks inside jinja2 templates.
- line-length # Violations reported by yamllint
- name[casing] # Rule for checking task names and their content.
- yaml[line-length] # Violations reported by yamllint
skip_list:
- var-spacing # Jinja2 variables and filters should have spaces before and after. $ ansible-lint | grep var-spacing
WARNING: PATH altered to include /usr/local/opt/python@3.9/bin
WARNING Listing 345 violation(s) that are fatal
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
var-spacing: Jinja2 variables and filters should have spaces before and after.
You can skip specific rules or tags by adding them to your configuration file:
# .config/ansible-lint.yml
warn_list: # or 'skip_list' to silence them completely
- var-spacing # Jinja2 variables and filters should have spaces before and after.
Finished with 13 failure(s), 332 warning(s) on 124 files. |
All $ cat .ansible-lint
---
exclude_paths:
- .git/
- .github/
- tests/
enable_list:
- fqcn-builtins
skip_list:
- jinja[spacing] # Rule that looks inside jinja2 templates.
- line-length # Violations reported by yamllint
- name[casing] # Rule for checking task names and their content.
- yaml[line-length] # Violations reported by yamllint
- var-spacing # Jinja2 variables and filters should have spaces before and after.
|
Probably not adding |
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 18, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 18, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 18, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 20, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 21, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 21, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 21, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 21, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
to ssbarnea/ansible-lint
that referenced
this issue
Aug 22, 2022
This change rewrites jinja2 rule to make it use jinaja lex parser and avoid use of regexes for parsing, as they cause too many false positives. Fixes: ansible#2301 ansible#2285 ansible#2241 ansible#2209 ansible#2208 ansible#2120
ssbarnea
added a commit
that referenced
this issue
Aug 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
var-spacing
rule triggers even if inwarn_list
,jinja[spacing]
does not.Issue Type
Ansible and Ansible Lint details
ansible-lint 6.4.1.dev27 using ansible 2.12.7
OS / ENVIRONMENT
macOS
Python 3.9.13
STEPS TO REPRODUCE
Desired Behavior
var-spacing
should behave as thejinja[spacing]
ruleThe text was updated successfully, but these errors were encountered: