64e19e8a74
fix: filter None to exclude them
3 years ago
3561a77070
tests: testing skipping warn with None level
3 years ago
0354c335c4
ci: add ddt to the tests requirements and update the contributing file accordingly
3 years ago
e018da186e
feat: fixed some isues
3 years ago
48b5e2b404
tests: tested formats with errors
3 years ago
418952cc5c
refactor: match flake requirements
3 years ago
4ae5487e3e
feat: add the possibility to pass the level as argument
3 years ago
d666308eb6
tests: use ddt to parametrize tests
3 years ago
b42ac81594
chore: rm coverage
3 years ago
1f6adf64f8
test: Class to test all fmt
3 years ago
eb48e1d908
test: Base class test
3 years ago
32de447205
test: severity_from_level
3 years ago
b1ce2f290b
test: escape_xml
3 years ago
dab7a8089b
fix: test_run_with_user_global_config_file patched
3 years ago
40574518ba
feat: changed json format according to @adrienverge comment
3 years ago
e04f03a76c
feat: auto infer formats
3 years ago
4baaf1200d
feat: add message to the json format
3 years ago
d24519c941
feat: add codeclimate output
3 years ago
2839489337
typo
3 years ago
6a06e8d512
feat: changed json output file name to path
...
https://github.com/adrienverge/yamllint/pull/442#issuecomment-1030572919
3 years ago
805b9a9739
feat: junitxml formater
3 years ago
fbf8108b97
feat: json formater
3 years ago
6217241fec
refactor: use object inheritance for the formaters
3 years ago
c4463c706f
feat: max_level as separate function
3 years ago
46a12a83a8
fix: missed return statement
3 years ago
3601817dd2
refactor: moved output at the end of the tests
3 years ago
b858cbbb82
refactor: moved formater inside another file
3 years ago
81951b3230
chore: ignore venv
3 years ago
4f1bbc33dc
docs: Fix link syntax on integration.rst
3 years ago
bb567ba395
comments: Allow whitespace after the shebang marker
...
Basically, any character is now allowed after the shebang marker.
Closes #428 .
Whitespace after the #! marker on shebang lines is authorized and
optional, as explained on Wikipedia's entry for shebang line as can be
seen from the extracts below :
> White space after #! is optional
and
> It has been claimed[20] that some old versions of Unix expect the
> normal shebang to be followed by a space and a slash (#! /), but this
> appears to be untrue;[21] rather, blanks after the shebang have
> traditionally been allowed, and sometimes documented with a space
3 years ago
d0392b34ca
github format: Update output to utilize groups
...
Resolves #421
Update the github formatting to utilize groups in the output and provide
the line/column number for the error in the output log.
3 years ago
7246a0c800
cli: Separate --format=auto logic
...
Moved the auto arg_format selection out of the main if block into a
separate logic section to improve readability.
No logic changes.
3 years ago
9e6dfacceb
Fix github actions workflow
...
- install correct python version
- set `fail-fast: false` to run all jobs
- remove hard-coded value for HOME directory
3 years ago
11e8d8ff37
Add support for Python 3.10, drop Python 3.5
...
- Add support for Python 3.10 released on 2021-10-04
- Drop support for Python 3.5 since it has reached end-of-life
3 years ago
f2e2e0c366
docs: Update CONTRIBUTING.rst
...
Be more precise in contributing instructions.
3 years ago
058fef7559
yamllint version 1.26.3
3 years ago
f47d5318cf
Restore setuptools requirement for Python < 3.8
...
This reverts commit 8f68248https://github.com/adrienverge/yamllint/issues/380 .
3 years ago
33ce0fa960
yamllint version 1.26.2
4 years ago
43744902e9
setup: update python_requires to comply with PEP 345/440
...
According to PEP 345 Requires-Python
(https://www.python.org/dev/peps/pep-0345/#requires-python ), the value
of this field must be a valid Version Specifier
(https://www.python.org/dev/peps/pep-0345/#version-specifiers ). Which
in turn expects this to comply with PEP 440
(https://www.python.org/dev/peps/pep-0440/ ).
While not an issue for those that directly use `pip`, this will cause
issues for `poetry` users in the next release (if their current stance
is maintained). Discussion of the issue and there stance can be found
here: https://github.com/python-poetry/poetry/issues/4095 .
4 years ago
85ccd625a3
yamllint version 1.26.1
4 years ago
e53ea093e2
line_length: skip all hash signs starting comment
4 years ago
5d8ef2ea23
CI: Simplify 'pip' commands
4 years ago
4515269233
CI: Fix failing 'coverage' command because of $PATH
...
Very probably due to:
https://github.com/actions/virtual-environments/issues/2455#issuecomment-787511010
4 years ago
66bf76a362
CI: Switch to GitHub Actions
...
Because Travis CI is dead.
4 years ago
8f682481c7
Remove runtime dep 'setuptools' for Python < 3.8
...
> In recent versions of setuptools and Python, console-script entry
points are using stdlib importlib by default, thus setuptools is no
longer needed as a runtime dependency.
https://github.com/pypa/setuptools/pull/2197
https://github.com/pypa/setuptools/blob/main/CHANGES.rst#v4730
https://docs.python.org/3/library/importlib.metadata.html
4 years ago
0fff4e29e4
yamllint version 1.26.0
4 years ago
1b378ed5b9
quoted-strings: Fix explicit octal recognition
...
PyYAML implements YAML spec version 1.1, not 1.2. Hence, values starting
with `0o` are not considered as numbers: they are just strings, so they
need quotes when `quoted-strings: {required: true}`.
>>> import yaml
>>> yaml.resolver.Resolver().resolve(yaml.nodes.ScalarNode, '100', (True, False))
'tag:yaml.org,2002:int'
>>> yaml.resolver.Resolver().resolve(yaml.nodes.ScalarNode, '0100', (True, False))
'tag:yaml.org,2002:int'
>>> yaml.resolver.Resolver().resolve(yaml.nodes.ScalarNode, '0o100', (True, False))
'tag:yaml.org,2002:str'
Let's try to prevent that.
Fixes https://github.com/adrienverge/yamllint/issues/351 .
4 years ago
a3fc64d134
End support for Python 2
...
As planned and advertized, yamllint drops support for Python 2 on 2021.
4 years ago
ee4d163ff8
Allow only non-empty brackets/braces
...
We'd like to disallow brackets and braces in our YAML, but there's a
catch: the only way to describe an empty array or hash in YAML is to
supply an empty one (`[]` or `{}`). Otherwise, the value will be null.
This commit adds a `non-empty` option to `forbid` for brackets and
braces. When it is set, all flow and sequence mappings will cause errors
_except_ for empty ones.
4 years ago
22335b294d
Add support for Python 3.9, drop Python 3.4
...
Add support for Python 3.9 since it was officially released in October
and drop support for Python 3.4 since it is end-of-life (EOL).
4 years ago
QuentinN42
Madison Swain-Bowden
Jérôme Alet
Trevor Royer
Dmytro Bondar
Adrien Vergé
Kyle Finley
Patryk Małek
Daniel M. Capella
Rusty Geldmacher
Jason Mobarak