| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
* 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
|
|
* Use phpstan config file as default whenever possible + report as error
|
|
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.
|
|
|
|
|
|
|
|
* Added psscriptanalyzer
* Added exclusions and documentation
* Added PSScriptAnalyzer handler test
|
|
|
|
The Rust compiler returns the first column that is _not_ part of the
current span as `column_end`, while Ale expects `end_col` to signify
the last column of the span.
|
|
Although using %t to lint changes was desirable, many pylama checks use
surrounding paths and file contents (e.g. C0103 module name, E0402
relative import beyond top, etc.) The more such errors I find during
testing, the less %t seems like a good idea. Switch to %s.
Also set `lint_file` to 1 and mark Pylama as a file linter in the docs.
Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
|
|
* Add pylama for python
* Consolidate python traceback handling
|
|
|
