| Age | Commit message (Collapse) | Author |
|---|
|
Add Apple's swift-format as a linter
|
|
Certain tests could break if you ran them separately from other tests.
They have been patched.
`run-tests` now has a `--fast` option which runs tests with only the
fastest Vim version ALE tests with, and the custom checks.
|
|
verilog: Add filename to vlog linter output
|
|
Fixes govet linter for go 1.13+, with tests
|
|
* fix cppcheck for 1.89+, and add column support
In cppcheck 1.89 the output changed to be more like GCC. This commit
forces any version of cppcheck to output in that same format. This also
allows for ALE to pick up the linter's column information
* Add parameters to tests. Vader passes.
* Fix c cppcheck for v1.89
|
|
|
|
Fixes #2965
|
|
Fix 2732 - Add bashate support
|
|
Add handling for `Syntax error at end of input` which doesn't give a
line or column.
Fixes #2656
|
|
error message
|
|
Improve :ALEDetail for dockerfile_lint [READY TO REVIEW]
|
|
|
|
|
|
|
|
|
|
Since version 4.032 (04/2020) verilator linter messages also contain the
column number, and look like:
%Error: /tmp/test.sv:3:1: syntax error, unexpected endmodule, expecting ';'
To stay compatible with old versions of the tool, the column number is
optional in the researched pattern regular expression.
See commit:
https://github.com/verilator/verilator/commit/81c659957e89f28861fde870f000cce2d5f76729
|
|
|
|
|
|
|
|
|
|
ESLint errors are contained in an array that can contain different
stuff other than JSON error messages. This patch iterates over the whole
array ignoring any non-json data.
|
|
Add nimcheck end_col options
|
|
Fix crystal-lang non file-tied message handling
|
|
nimcheck
|
|
Some messages of the crystal compiler are not tied to a file.
This causes a 'Key not present in Dictionnary' error (E716).
For the record, the json output on ```require "./nonexistent.cr"```
is the following :
```json
[
{ "file":"/tmp/file.cr", "line":1, "column":1, "size":0,
"message":"while requiring \"./nonexistent.cr\"" },
{ "message":"can't find file './nonexistent.cr' relative to '/tmp'" }
]
```
The second message does not have line/column attributes.
|
|
* 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
|
|
Add ruby debride (closes #2471)
|
|
|
|
mdl: Use JSON output instead of parsing text
|
|
* 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.
|
|
Fixes #2687
|
|
Also add test coverage for the mdl handler.
|
|
|
|
|
|
* Added a new csc linter for C# code.
* More output is now handled for mcsc.
|
|
* Newline in unexpected token broke parser
* fixed test to properly capture regressions
* removed deprecated linter options for powershell
|
|
show rendered cargo error in detail for clippy errors
|
|
Use JSON output for ESLint and fix tsserver column
|
|
|
|
|
|
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.
|
|
|
|
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
|
|
|
|
* Add support for Erlang dialyzer
* Add an option to specify rebar3 profile
In doing so, the use of the `**` wildcard becomes unnecessary.
|
|
|
