| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* fix tflint handler for 0.11+
* fixup! fix tflint handler for 0.11+
* maintain compatibility with previous tflint output format
* fixup! maintain compatibility with previous tflint output format
* Add comment about tflint's output format accross versions
|
|
Update vlog parser to handle new output format
|
|
Use Makefile output with clang-tidy when useful
|
|
andys8/improvement/elm-language-server-elm-analyse-trigger-param
Elm language server params update
|
|
Add linter for Scala Metals
|
|
Use the psalm executable with the LS option
|
|
Add ruby debride (closes #2471)
|
|
|
|
In the case where neither a build directory nor a compile_commands.json
file is found, use the output of `make -n` to provide options to
clang-tidy.
|
|
|
|
Re #2812, the parser now takes a second pass through the output using an
updated regex.
|
|
Add support for ink-language-server
|
|
|
|
mdl: Use JSON output instead of parsing text
|
|
Fix bug with detection of the PLT in Erlang Dialyzer
|
|
* Add support for `solc` Solidity compiler
* Set default value for `solidity_solc_options`
* Add test for solc handler
|
|
Remove +x bit from some files that don't need it.
|
|
Move ale#handlers#ruby#EscapeExecutable to ale#ruby#EscapeExecutable
|
|
* There is a new param 'elmAnalyseTrigger' (change|save|never)
* Empty path default to let the language server search for binary
|
|
Fixes #2687
|
|
https://scalameta.org/metals/
|
|
Also add test coverage for the mdl handler.
|
|
|
|
This function is generally applicable to Ruby, not just handling linter
output.
|
|
|
|
|
|
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.
|
|
Previously, it did not detect the PLT inside the `_build` directory and
would always default to the default PLT or the one from the `kerl` tool.
|
|
Update Rust cargo linter to better integrate with Clippy
|
|
|
|
Previous name of `elm-language-server` was `elm-lsp`
|
|
* 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.
|
|
* Newline in unexpected token broke parser
* fixed test to properly capture regressions
* removed deprecated linter options for powershell
|
|
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.
|
|
Fix javalsp command callback.
|
|
The default binary "launcher" is too generic and can get mixed with
other tools. To use this linter user must explicitly set the absolute
path of the launcher path.
|
|
|
|
|
|
Use JSON output for ESLint and fix tsserver column
|
|
The existing option setting handles setting additional compile flags to
pass to clang-tidy. The new option setting added here allows setting
additional clang-tidy specific flags to be passed as well.
Fixes #2324
|
