| Age | Commit message (Collapse) | Author |
|---|
|
Update test docs and output for linter tables checked
|
|
* feat: support sqlformat.
|
|
import support (tsserver) (#2709)
This commit adds support for renaming symbols in tsserver and with LSP tools, and for organising imports with tsserver. Completion results for symbols that can be imported are now suggested if enabled for tsserver completion done via ALE.
|
|
Options are now configurable for languagetools, and `--autoDetect` can be removed by changing the options.
|
|
* Add support for `dfmt`
|
|
|
|
* add g:ale_sign_highlight_linenr
* Fix tests. Change option default value
* Rename ale_sign_highlight_linenr to ale_sign_highlight_linenrs
* Default ale_sign_highlight_linenrs to 0
|
|
bugfix/c-lsp-build-dir-settings
|
|
Add gnatpp fixer for Ada
|
|
|
|
This makes some of the run-test output less misleading.
Also fix a minor shellcheck issue: "\*" and "\\*" are equivalent, but
the second one makes clear that the literal backslash is intentional.
|
|
|
|
Support $GO111MODULE with Go tooling
|
|
* Add setting for numhl highlights
* Add doc for numhl feature
|
|
Update elm-ls
|
|
|
|
|
|
Default executable for javalsp is empthy string.
|
|
* Added a new csc linter for C# code.
* More output is now handled for mcsc.
|
|
* Add clangtidy fixer
* Add extra_options to clangtidy fixer
* Also, use cpp variables in cpp filetypes
|
|
|
|
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.
|
|
|
|
Add support for javalsp configuration options.
|
|
`g:ale_lint_on_insert_leave` default has been changed from 0 to 1 in
168768b32667b244e0afdc8da851d91ab95d6e2f
|
|
This fixes documentation to match actual implementation.
|
|
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
|
|
Fix checkstyle default configuration.
|
|
prettier: Support experimental languages (Handlebars)
|
|
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.
|
|
b:ale_lint_on_insert_leave is now supported as tests need it.
These defaults are saner and cause fewer issues for users by default.
|
|
Add support for reorder-python-imports fixer
|
|
* add R markdown as filetype for styler
* Add rmarkdown as an alias for R
|
|
Fix javalsp command callback.
|
|
|
|
isort is great, but I've come to prefer reorder-python-imports. The tool
has a focus on smaller diffs than isort. reorder-python-imports is also
a little smarter than isort which is nice.
|
|
|
|
|
|
Run xml linters on xsd and xslt files
|
|
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
|
|
Both xsd and xslt are by definition written in XML, and thus the same
linter(s) can be run to check them for well-formedness.
|
|
Such as handlebars
|
|
The command used to invoke the language server is missing some options
to include additional java modules. Without these modules the server
was not working properly.
The correct command can be found in a `launcher` script on the same
directory the `java` executable for the language server is found.
This commit changes the docs to prefer the launcher script over the java
executable. For backward compatibility it also fixes the command
invocation in case the java executable is configured.
|
|
|
|
Allow to send custom notification mesages, that expect no response from
the server.
|
|
|
|
Implement a function `ale#lsp_linter#SendRequest` that allows to send
custom LSP requests to an enabled LSP linter.
Resolves #2474
|
|
Add a terraform linter
|
