summaryrefslogtreecommitdiff
path: root/test/handler
AgeCommit message (Collapse)Author
2020-08-07Merge pull request #3191 from mostfunkyduck/masterw0rp
Fixes govet linter for go 1.13+, with tests
2020-08-06fix cppcheck for 1.89+, and add column support (#3030)tsjordan-eng
* 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
2020-07-31Support markdownlint rules with multiple slashesSebastian Blask
2020-07-30Support markdownlint 0.19.0 and 0.22.0Sebastian Blask
Fixes #2965
2020-07-21Merge pull request #3070 from hsanson/2732-add-bashate-supportw0rp
Fix 2732 - Add bashate support
2020-07-15Handling for puppet parser error at end of input.Mark Egan-Fuller
Add handling for `Syntax error at end of input` which doesn't give a line or column. Fixes #2656
2020-07-02Tests/puppet: add new test case for a heretofore unaccounted-for version of ↵Christopher Peterson
error message
2020-06-20Merge pull request #3158 from ulidtko/improve-dockerfile_lintHoracio Sanson
Improve :ALEDetail for dockerfile_lint [READY TO REVIEW]
2020-05-25Fixes govet linter for go 1.13+, with testsmostfunkyduck
2020-05-06Fix style and testmax ulidtko
2020-04-28Fix handler test, function name has changedIan2020
2020-04-18Adds column number to the verilator verilog linterTG
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
2020-03-23Fix 2732 - Add bashate supportHoracio Sanson
2020-01-02Fix the buildw0rp
2020-01-02Fix #2704 - Show mypy notes; can be disabledw0rp
2019-11-26Fix 2891 - eslint not showing errors.Horacio Sanson
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.
2019-11-07Merge pull request #2887 from tamago324/add-nimcheck-end_col-optionsw0rp
Add nimcheck end_col options
2019-11-07Merge pull request #2617 from robindar/masterw0rp
Fix crystal-lang non file-tied message handling
2019-11-07Add nimcheck end_col optionstamago324
nimcheck
2019-10-11Fix crystal-lang non file-tied message handlingDavid A. R. Robin
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.
2019-10-07fix tflint handler for 0.11+ (#2775)Jérôme Foray
* 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
2019-10-07Merge pull request #2813 from werneta/masterw0rp
Update vlog parser to handle new output format
2019-10-07Merge pull request #2694 from elebow/add-ruby-debridew0rp
Add ruby debride (closes #2471)
2019-10-05Add test for new vlog formatThomas A. Werne
2019-09-20Merge pull request #2691 from elebow/mdl-use-json-outputw0rp
mdl: Use JSON output instead of parsing text
2019-09-19Add support for `solc` Solidity compiler (#2648)Karl Bartel
* Add support for `solc` Solidity compiler * Set default value for `solidity_solc_options` * Add test for solc handler
2019-09-12Merge pull request #2693 from elebow/chmod-remove-xw0rp
Remove +x bit from some files that don't need it.
2019-08-31linter/sh: Improve parsing of error messages in different localesJeffrey Lau
Fixes #2687
2019-08-18mdl: Use JSON output instead of parsing textEddie Lebow
Also add test coverage for the mdl handler.
2019-08-13debride: Add debride linter (closes #2471)Eddie Lebow
2019-08-13Remove +x bit from some files that don't need it.Eddie Lebow
2019-07-02Support csc, update mcsc (#2586)hernot
* Added a new csc linter for C# code. * More output is now handled for mcsc.
2019-06-19Handle powershell unexpected token with newline (#2588)Jesse Harris
* Newline in unexpected token broke parser * fixed test to properly capture regressions * removed deprecated linter options for powershell
2019-06-08Merge pull request #2559 from nerdrew/rust-cargo-rendered-detailw0rp
show rendered cargo error in detail for clippy errors
2019-06-08Merge pull request #2551 from laino/eslint-jsonw0rp
Use JSON output for ESLint and fix tsserver column
2019-06-05Fix #2525 - Convert Windows paths in a Unix environmentw0rp
2019-06-04show rendered cargo error in detailAndrew Lazarus
2019-06-03Fix #1279 - Run cppcheck differently when modifiedChristoph Koehler
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.
2019-06-02Use JSON output for eslint and fix tsserver columnNils Kuhnhenn
2019-05-29Merge pull request #2529 from maxwell-k/terraform_linterw0rp
Add a terraform linter
2019-05-28Fix java checkstyle handler.Horacio Sanson
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.
2019-05-23Add a terraform linterKeith Maxwell
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
2019-05-20Close #2516 - Handle problems with inlined functionsw0rp
2019-05-19Add support for Erlang dialyzer (#2509)Antoine Gagné
* Add support for Erlang dialyzer * Add an option to specify rebar3 profile In doing so, the use of the `**` wildcard becomes unnecessary.
2019-05-14Close #908 - Report phpcs problems as style problemsw0rp
2019-05-13Close #791 - Handle exceptions for puglintw0rp
2019-05-12Make eslint respect the ale_warn_about_trailing_whitespace settingw0rp
2019-05-09Add option to show msg id when pylint is used (#2445)Katsuya Horiuchi
* 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
2019-05-08Merge pull request #2134 from oaue/masterw0rp
javac linter: fix handling of error messages containing ':' character
2019-05-01Better phpstan default configuration (#2444)Julien Deniau
* Use phpstan config file as default whenever possible + report as error
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 01:10:23 +0000