| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
Add a terraform linter
|
|
|
|
The checkstyle handler is capable of parsing the new and old output
formats. Unfortunately there are some particular output messages that
matched both the new and old regular expressions:
[WARN] whatever:11:7: WhitespaceAround: ''if'' is not followed by whitespace. [WhitespaceAround]
This caused ALE to report extra errors since the message was being
matched twice, once as a warning and another (incorrect) old formatted
error.
This MR fixes this by stopping any parsing using the old format regexp
is any errors of the new format are correcly parsed. There is no reason
to expect checkstyle to output both styles in the same report.
|
|
This linter uses the check functionality built into terraform. ALE
already has a fixer using `terraform fmt` but this doesn't provide error
messages. ALE already has a linter using `tflint` but this requires an
extra application to be installed.
For example this linter will give a warning that ! is an illegal
character in the line below:
variable "example" !{}
This linter runs the buffer through the command below and parses the
output:
terraform fmt -no-color -check=true -
This commit includes a basic implementation, documentation and tests.
The only option is to control which executable is run.
Tested with:
$ terraform -version
Terraform v0.11.13
|
|
We were setting the -data parameter to the project root but this caused
the language server to fail initialization and synch of gradle
dependencies. As consequence ALE failed to work fully on gradle
projects.
This fix sets the workspace to the parent folder of the project root.
Normally this corresponds to the correct Eclipse workspace path.
When this is not the case, this fix also allows users to explicitly set
the absolute path to the workspace via configuration variable.
|
|
* Search eclipselsp jar and config files within system package path
* Allow setting an alternate eclipselsp configuration directory
* Add test for ale_java_eclipselsp_config_path
|
|
|
|
|
|
|
|
* Add support for Erlang dialyzer
* Add an option to specify rebar3 profile
In doing so, the use of the `**` wildcard becomes unnecessary.
|
|
|
|
|
|
|
|
|
|
* Add python_pylint_use_msg_id to tweak output of pylint
* Add test for ale_python_pylint_use_msg_id
* Add doc on ale_python_pylint_use_msg_id
|
|
javac linter: fix handling of error messages containing ':' character
|
|
- Set default value to $HOME/eclipse.jdt.ls
- Make JAR search regexp more specific.
- Allow to set the VSCode extensions folder as ale_java_eclipselsp_path.
|
|
|
|
|
|
* Use phpstan config file as default whenever possible + report as error
|
|
|
|
|
|
|
|
WIP Fix 1996 - Add eclipse LSP support.
|
|
feat: fecs support for js/html/css lint and format
|
|
* Linter for powershell syntax errors
|
|
|
|
|
|
`fecs` is a lint tool for HTML/CSS/JavaScript,
see http://fecs.baidu.com for more options.
|
|
|
|
|
|
|
|
|
|
|
|
* [linter] Add LSP support for Swift via sourcekit-lsp
|
|
|
|
|
|
make `gotype` return all errors
|
|
* Added psscriptanalyzer
* Added exclusions and documentation
* Added PSScriptAnalyzer handler test
|
|
support jsonlint local executable
|
|
Elm: Support for elm-lsp
|
|
* move php-langserver "test for .git dir" test-project to its own directory
* search for composer.json file in php-langserver first then .git dir
* add test for php-langserver composer.json
|
|
|
|
|
|
When using `gotype` without the `-e` option, it will only output the
first 10 errors. When working on a larger package that ofter means taht
those 10 errors are in other files then the one that you are currently
working on which then seems to indicate that there are no errors.
By adding the `-e` flag, all errors will be returned and shown properly
in the file that you are working on.
|
|
* Add credo --strict option
If a user sets 'let g:ale_elixir_credo_strict=1' it will run credo with
--strict instead of suggest. The default (0) is to run as suggest.
* Added credo docs
|
|
|
|
javac: Don't assume src/main/java always exists
|
