0f073f7a09
Before, it was required to specify all the options when customizing a
rule. For instance, one could use `empty-lines: enable` or `empty-lines:
{max: 1, max-start: 2, max-end: 2}`, but not just `empty-lines: {max:
1}` (it would fail with *invalid config: missing option "max-start" for
rule "empty-lines"*).
This was a minor problem for users, but it prevented the addition of new
options to existing rules, see [1] for an example. If a new option was
added, updating yamllint for all users that customize the rule would
produce a crash (*invalid config: missing option ...*).
To avoid that, let's embed default values inside the rules themselves,
instead of keeping them in `conf/default.yaml`.
This refactor should not have any impact on existing projects. I've
manually checked that it did not change the output of tests, on
different projects:
- ansible/ansible: `test/runner/ansible-test sanity --python 3.7 --test yamllint`
- ansible/molecule: `yamllint -s test/ molecule/`
- Neo23x0/sigma: `make test-yaml`
- markstory/lint-review: `yamllint .`
[1]: https://github.com/adrienverge/yamllint/pull/151
89 lines
1.9 KiB
Python
89 lines
1.9 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright (C) 2016 Adrien Vergé
|
|
#
|
|
# This program is free software: you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation, either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
"""
|
|
Use this rule to control the number of spaces after hyphens (``-``).
|
|
|
|
.. rubric:: Options
|
|
|
|
* ``max-spaces-after`` defines the maximal number of spaces allowed after
|
|
hyphens.
|
|
|
|
.. rubric:: Examples
|
|
|
|
#. With ``hyphens: {max-spaces-after: 1}``
|
|
|
|
the following code snippet would **PASS**:
|
|
::
|
|
|
|
- first list:
|
|
- a
|
|
- b
|
|
- - 1
|
|
- 2
|
|
- 3
|
|
|
|
the following code snippet would **FAIL**:
|
|
::
|
|
|
|
- first list:
|
|
- a
|
|
- b
|
|
|
|
the following code snippet would **FAIL**:
|
|
::
|
|
|
|
- - 1
|
|
- 2
|
|
- 3
|
|
|
|
#. With ``hyphens: {max-spaces-after: 3}``
|
|
|
|
the following code snippet would **PASS**:
|
|
::
|
|
|
|
- key
|
|
- key2
|
|
- key42
|
|
|
|
the following code snippet would **FAIL**:
|
|
::
|
|
|
|
- key
|
|
- key2
|
|
- key42
|
|
"""
|
|
|
|
|
|
import yaml
|
|
|
|
from yamllint.rules.common import spaces_after
|
|
|
|
|
|
ID = 'hyphens'
|
|
TYPE = 'token'
|
|
CONF = {'max-spaces-after': int}
|
|
DEFAULT = {'max-spaces-after': 1}
|
|
|
|
|
|
def check(conf, token, prev, next, nextnext, context):
|
|
if isinstance(token, yaml.BlockEntryToken):
|
|
problem = spaces_after(token, prev, next,
|
|
max=conf['max-spaces-after'],
|
|
max_desc='too many spaces after hyphen')
|
|
if problem is not None:
|
|
yield problem
|