-
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: false-positive in regexp #2285
Labels
Comments
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
Rather similar to #2208 but with variables.
The pipe in the
regexp: '({{ var1 }}|{{ var2 }})'
triggers a false-positive.Also related
Issue Type
Ansible and Ansible Lint details
OS / ENVIRONMENT
STEPS TO REPRODUCE
Desired Behavior
The regexp should not trigger a var-spacing warning
Actual Behavior
A minimal playbook might look like
The pipe triggers a var-spacing warning.
The text was updated successfully, but these errors were encountered: