| Age | Commit message (Collapse) | Author |
|---|
|
* Fix error from ansible-lint versions >=6.11.0.
The JSON output format of ansible-lint has changed since
6.11.0. Issue locations can have either a 'positions' or
a 'lines' member, rather than just a 'lines' member as it
was before. This fix checks which member is present, and
passes that member name to subsequent dictionary lookups.
The error was caused by the following change:
https://github.com/ansible/ansible-lint/pull/2897
* Add ansible-lint test to check each type of ansible-lint issue json.
* Change long single-line JSON in ansible test into multiline JSON.
* Fix linting errors in ansible_lint.vim.
|
|
* remove --enable-all from default golangci-lint options
* update golangci-lint options documentation
* update tests to use empty golangci-lint options
|
|
|
|
|
|
Automatically set `PATH` for some Python linters that seem to need it
when g:ale_python_auto_virtualenv or b:ale_python_auto_virtualenv is
`1`.
|
|
Add support for automatically detecting and running Pyright via poetry,
pipenv, and virtualenv directories just like we do with flake8.
|
|
|
|
* add eslint plugin html for linting js in html files
* fix linting
|
|
PHPStan will only detect a configuration file in the current working
directory, so set that to the directory in which ALE finds the
configuration file.
|
|
this commit adds pycln as a Python linter and fixer, together with some
tests and documentation. It addresses #4340
pycln repo: https://github.com/hadialqattan/pycln
|
|
|
|
What I should have done in 4394. Idea: @w0rp
|
|
|
|
Add functions to compute the cwd to be the same as the project root for
pylsp and Pyright to work around issues in each language server when
they encounter modules that share the same name as first or third party
libraries.
|
|
* Handle empty answer of ansible-lint
The variable a:lines might be empty if ansible-lint exited early, in
that case json_decode would trow an error.
* Use ales JSON decode function
|
|
this commit adds refurb as a Python linter, together with some tests
and documentation. it should fix issue: #4362
refurb repo: https://github.com/dosisod/refurb
|
|
|
|
* Account for no sqlfluff output
Avoid crashes when there isn't any output from sqlfluff.
* Add supplort for sqlfluff as a fixer
|
|
|
|
|
|
`checkmake` by default checks config file "in the same folder it's
executed in" unless `--config` option is set.
This commit allows setting the `--config` option with an option
variable (with documentation updated).
|
|
- Add this option so command line arguments can be supplied to hadolint
- This will be respected when running in docker and via the executable
- Preserve the --no-color and - flags, and add these to the list
- Add to docs and tests
|
|
this commit adds ruff as both a Python linter and fixer, together with
some tests and documentation.
ruff repo: https://github.com/charliermarsh/ruff
|
|
|
|
|
|
Gcc does not support `x c*-header` when using `-` as input filename,
which is what ALE does.
Rework the feature to only use `-x c*-header` flag when using Clang and
not GCC.
The feature is now also controlled with the variable
`g:ale_c_cc_use_header_lang_flag` and
`g:ale_cpp_cc_use_header_lang_flag`.
|
|
|
|
When linting an header file in C or C++, `-x c-header` or
`-x c++-header` should be used instead of `-x c` or `-x c++`.
Using `-x c` or `-x c++` for headers files can lead to unused variables
and functions marked as static inlined as seen in #4096.
Using `-x c-header` or `-x c++-header` solve these issues.
The list of file extensions that are considered as header files can be
configured with the variables `g:ale_c_cc_header_exts` and
`g:ale_cpp_cc_header_exts`.
|
|
This allows using linters like `:namespace-name-mismatch`.
This replaces: https://github.com/dense-analysis/ale/pull/4109
|
|
I discovered that references to other Bicep files (modules) will be
broken if running on a temporary file in a different location. I've
found no way of providing an alternate path when invoking the command.
|
|
* Add support for Microsoft's DSL Bicep
The compilation command 'bicep build' catches compilation errors as well
as providing some lint warnings.
Repository for Bicep: https://github.com/Azure/bicep
* Different null file on Windows & hardcode commands
|
|
see: johnsoncodehk/volar#876
see: johnsoncodehk/volar/blob/master/packages/vue-language-server/package.json#L11
|
|
|
|
* Allow to pass options to the buf linter
* Fix the callback of buf linter
|
|
|
|
* cairo support
* supported languages txt
* add cairo to ale.txt
|
|
|
|
* Add support for actionlint options
* fix misaligned doc tags
|
|
(#4157)
* Fallback to summary field if detail exists but is empty in terraform linter
* Add test
* Update terraform.vim
* remove whitespaces
|
|
* add opa fmt fixer for rego files
* add opa linter
* add basic tests for linter and fixer
* add cspell to the docs
|
|
* support ember-template-lint 4.x
* update ember-template-lint linter test
|
|
ansible-lint 6.0.0 removed the `--parseable-severity` option. Use the
JSON output in its place.
Fixes #4188
|
|
* Handle golangci_lint warning and error messages correctly
* Fix linter warning
Co-authored-by: Richard Jonas <richard.jonas@derivco.se>
|
|
When I added Selene as a linter, I wasn't aware it had the option to
process stdin using `-`.
|
|
Co-authored-by: bretello <bretello@distruzione.org>
|
|
Switched to `vscode-langservers-extracted` as it is the one most
up-to-date.
|
|
* vscode-json-languageserver-bin support
VSCode JSON languageserver has schema support for linting and
completions.
I have enabled snippets support (`snippetSupport`) even if it is not
fully supported. `label` that comes with completions response can be
used as well.
* Test fix.
* vscode-json-languageserver instead of vscode-json-languageserver-bin
vscode-json-languageserver is more up-to-date (about 1 year old),
vscode-json-languageserver-bin is 4 years old.
* Use git root.
* Documentation update.
* Trying to sort ordering issue.
* One more attempt
* One more attempt
* Uppercase seems to win.
* Clean-up
* Clean-up 2
* Test removed.
|
|
|
|
* Use JSON format for newer pylama version
https://github.com/klen/pylama/blob/develop/Changelog
The --format json option is added in pylama version 8.1.4.
* Fix linting warnings for pylama
|
|
* Add buf lint to linters
* Add buf format to fixers
* Fix test/linter/test_buf_lint.vader
* Fix test/fixers/test_buf_format_fixer_callback.vader
* Simplify test/test-files/proto/testfile.proto
* Add buf-lint alias and rename linter
|
