| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
* Add support for actionlint options
* fix misaligned doc tags
|
|
* Allow customization of all floating window borders
Users may not necessarily want the same border character for top+bottom
or left+right, so allow all eight border characters to be configured in
g:ale_floating_window_border.
For backwards compatibility, the old rules are still applied if only six
elements are given.
* Reorder popup border array for compatibility
|
|
* Add zig fmt support
* Review changes
* Fix linter errors
|
|
(#4157)
* Fallback to summary field if detail exists but is empty in terraform linter
* Add test
* Update terraform.vim
* remove whitespaces
|
|
* Add support for HashiCorp Packer
* Add test for packer fmt
* Add doc for HCL/Packer
* Add link to Packer doc
* Also suggest packer fix for packer ft
* Add more links to TOC
|
|
|
|
* 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
|
|
We already check for mypy.ini, but the fallback .mypy.ini was ignored.
|
|
|
|
|
|
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>
|
|
* Fix 4177 set default yaml linters
* Fix 4177 set default yaml linters
|
|
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.
|
|
* Add go to implementation
* Add test cases for GoToImplementation
* Add documentation for GoToImplementation
|
|
|
|
* Advertise codeActionLiteralSupport to LSP server
Without this, rust-analyzer doesn't return any code actions. With it,
everything works properly.
* linter fixes
* test cases fixes
* Fix underflow of column in position.
Special values like for example -1 to denote the end of a line are not supported.
[reference](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position)
Co-authored-by: Brian Gernhardt <brian@gernhardtsoftware.com>
|
|
* 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
|
|
* Add primitive handling of ghc panic.
* PascalCase in function.
* Add simple test.
|
|
|
|
* Fix 4141 - Stop press enter prompt on long diagnostic messages
* Fix 4139 - Check for array before join truncated_echo
|
|
|
|
The previous linter rule about stray echo lines has been restored, and
now all problems for custom linting rules can be ignored by adding a
comment above problem lines.
|
|
* Problem messages no longer clutter `:messages`
* Messages are truncated better
|
|
Co-authored-by: w0rp <devw0rp@gmail.com>
|
|
* Update test scripts
* Remove neovim 0.3 and 0.4
* Add neovim 0.6.1
Co-authored-by: Horacio Sanson <horacio@allm.inc>
Co-authored-by: w0rp <devw0rp@gmail.com>
|
|
If the end of the error exceeds the file, set it to the last line,
similarly as it is done with the beginning of the error.
|
|
* rust-analyzer in non-cargo projects
rust-analyzer can also be used in non-cargo projects. This requires a
rust-project.json file in the project root [1].
Make the rust-analyzer linter search for a rust-project.json file if no
Cargo.toml file could be found.
[1]: https://rust-analyzer.github.io/manual.html#non-cargo-based-projects
* Document rust-analyzer without cargo
* Test rust-analyzer with non-cargo projects
Change the other rust tests to match the new directory structure of the
test files.
|
|
Currently, it's not possible to override the awk `--lint` option with
```viml
let g:ale_awk_gawk_options = '--lint=no-ext'
```
although this could be useful for those who only use gawk and don't want to get these lint errors:
> FEATURE X is a gawk extension
The idea is to move the default `--lint` option before the `awk_gawk_options` in the gawk.vim code to give the custom `--lint=...` option a higher precedence.
Co-authored-by: Barnabás Ágoston <barna@agoston.dev>
|
|
Fix :ALEImport column position so it works with more language servers.
Co-authored-by: w0rp <devw0rp@gmail.com>
|
|
|
|
|
|
|
|
|
|
This patch adds support for opening jdt:// links on "go to definition" requests returned by Java language servers.
Co-authored-by: w0rp <devw0rp@gmail.com>
|
|
|
|
Co-authored-by: cos <cos>
|
|
|
|
|
