Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
* When deciding which directory to run mypy from, prefer a folder with mypy.ini in it
* Add a test for mypy.ini-finding behaviour
|
|
|
|
If checkstyle is configured with custom options that contain "-c" then
the checkstyle config file option is ignored. This PR modifies the
regular expression when creating the checkstyle command to avoid this.
|
|
Add StandardJS linter for TypeScript
|
|
This reverts commit f4070f6c43b3cb2e7463d8426a68d5a726991288.
|
|
Add the possiblity to add extra psalm options
|
|
* Add support for html-beautify
* Add html-beautify to the list of supported tools
* Update docs
|
|
clangcheck: Add -fno-color-diagnostics (closes #2188)
|
|
|
|
|
|
* Add support for nimlsp.vim
* Add test and docs for nimlsp
* Add nimlsp to supported-tools.md
* Add nimlsp to doc/ale-supported-languages-and-tools.txt
|
|
* Add definition of c/clangd's language as C
* Update tests for clangd to be called with '-x c'
* Change to use single quotes instead of double quotes
|
|
|
|
Fixes #2832
|
|
|
|
|
|
|
|
|
|
|
|
Use Makefile output with clang-tidy when useful
|
|
Add linter for Scala Metals
|
|
Use the psalm executable with the LS option
|
|
|
|
Also change to the modern --extra-arg syntax.
|
|
Add support for ink-language-server
|
|
mdl: Use JSON output instead of parsing text
|
|
|
|
Options are now configurable for languagetools, and `--autoDetect` can be removed by changing the options.
|
|
Use ale#handlers#elixir#FindMixUmbrellaRoot to determine project root
instead of ale#handlers#elixir#FindMixProjectRoot
|
|
https://scalameta.org/metals/
|
|
Also add test coverage for the mdl handler.
|
|
* black fixer should include --pyi for files with .pyi extension
|
|
This commit add support for ink-language-server, which it does by
largely copying and pasting from the pure-language-server PR that was
merged recently.
The most interesting things to note are:
- ink-language-server is distributed upstream via npm, which is why we
search through node_modules
- With some coaxing, it can be installed globally - which is why we
search for a global binary.
- Ink is a funky language, and users will likely need to add
initialization options.
- I am not incredibly familiar with vimscript; and I may not have done
some of the buffer searching correctly.
|
|
|
|
Support $GO111MODULE with Go tooling
|
|
Update elm-ls
|
|
This is the simplest way of getting the psalm language server to run
now.
|
|
Update Rust cargo linter to better integrate with Clippy
|
|
|
|
* Added a new csc linter for C# code.
* More output is now handled for mcsc.
|
|
Allows the user to override $GO111MODULE environment variable through
ale options. This gives control over the default behavior of Go module
resolution.
Golang documentation:
https://github.com/golang/go/wiki/Modules#how-to-use-modules
Add `ale#Go#EnvString()` function to make it easy to add similar Go
environment variables in the future.
Use the new `EnvString` function in all available Go tools callbacks
& update tests
Also add test of linter command callback for `gofmt`
|
|
|
|
|
|
* elm_lsp is now elm_ls
* The binary published by @elm-tooling is elm-language-server
Updates tests, docs and adds more options to the plugin.
|
|
This MR adds a new configuration variable `g:ale_java_javalsp_config`
that allows to configure external dependencies and class paths to the
language server.
The variable accepts a dictionary similar to the one supported by the
[vscode/settings.json](https://github.com/georgewfraser/java-language-server#settings)
file.
Deprecates: #2561
|
|
* Add support for purescript language server
* Update naming
* Add purescript language server tests
|
|
Checkstyle xml configuration is mandatory and not providing one causes
the tool to fail with the following error:
Must specify a config XML file.
Checkstyle itself contains a default configuration as part of its
assests named `/google_checks.xml`. Invoking checkstyle with this config
works even if such file does not exists in the file system:
checkstyle -c /google_checks.xml
This should be the default invocation to allow ALE to use checkstyle
with zero configuration.
Also when a user sets `g:ale_java_checkstyle_config` option, ALE should
use it to invoke checkstyle even such file does not exists in the
filesystem. This is because checkstyle is able to use configuration files
within JAR files defined in the CLASSPATH. The default `/google_checks.xml`
is an example of such configuration available within a JAR resource.
|