LineTooLongRule - how to deal with it? about galaxy-lint-rules HOT 5 CLOSED

Note that the easiest fix is to break the thing to multiple lines, but when you do, if you just use the folded scalar > then it adds a newline character to the end:

docker_apt_repository: >
  deb [arch={{ docker_apt_arch }}]
  https://download.docker.com/linux/{{ ansible_distribution|lower }}
  {{ ansible_distribution_release }}
  {{ docker_apt_release_channel }}

So instead, you have to use an even weirder construct:

docker_apt_repository: >-
  deb [arch={{ docker_apt_arch }}]
  https://download.docker.com/linux/{{ ansible_distribution|lower }}
  {{ ansible_distribution_release }}
  {{ docker_apt_release_channel }}

from galaxy-lint-rules.

I see from previous conversations ansible/ansible uses 160 for pylint and pep8, and we want to match that, so we will change this from 100 to 160. Also ansible-lint supports excluding certain tasks from being linted, that might not be the best approach but is an option for the 193 character task.

from galaxy-lint-rules.

@awcrosby good to know, as 160 is a better gate in general (though I usually use 120, I know a lot of people have gone wider in recent years).

The task exclusion works great, but the rules also apply to vars files like role defaults, and you sadly can't tag a variable—it would be interesting if you were able to exclude a particular line (e.g. a variable line) using a comment like # skip-ansible-lint or something. I know you can do this with other linters I use, e.g. phpcs has // phpcs:disable

from galaxy-lint-rules.

See upstream closed issue: ansible/ansible-lint#132

from galaxy-lint-rules.

All right, looks like this is taken care of by the commit above, plus the fact that ansible lint currently doesn't lint vars files—see ansible/ansible-lint#354 for progress on that issue.

from galaxy-lint-rules.