| Age | Commit message (Collapse) | Author |
|---|
|
This is the simplest way of getting the psalm language server to run
now.
|
|
Update Rust cargo linter to better integrate with Clippy
|
|
|
|
Show more candidates for Deoplete completion
|
|
|
|
* 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
|
|
|
|
|
|
|
|
* 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
|
|
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
|
|
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.
|
|
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.
|
|
|
|
show rendered cargo error in detail for clippy errors
|
|
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
|
|
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.
|
|
|
|
|
|
cppcheck is now run without the --project option and from the buffer's
directory instead when the buffer has been modified. Saving the buffer
will get results by linting the project instead.
|
|
Use ant files to load Java settings too.
|
|
|
|
|
|
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
|
|
|
|
add pgformatter fixer
|
|
Fix java checkstyle handler.
|
|
|
|
|
