Age | Commit message (Collapse) | Author |
|
They changed their logic to use related paths instead of absoluut paths (see [here](https://github.com/alecthomas/gometalinter/commit/a04df08be5899be3c7ad69aa379858dcb660c709#diff-04424ed7c660c10495a54e8d11be89eaR253))
This fixes the linter by also using relative paths…
|
|
* Vim scripts shouldn't have hyphens
Especially not ones that will be autoloaded. You can't have a hyphen in
a function name, so autoloading functions based on filename will fail.
* Add g:haskell_stack_build_options, default: --fast
If we're going to use the --fast option, we may as well go the whole 9
yards and let the user configure the 'stack build' flags.
* Create documentation for stack-build options
|
|
|
|
fix some missing escaping for the rubocop linter
|
|
* Add stack-build linter for Haskell
The stack-build linter works better than the other two linters when
you're working with an entire Haskell project. It builds the project
entirely and reports any errors.
The other two Haskell GHC linters only work on single files, which can
result in spurious errors (for example, not being able to find imports).
* Document all available Haskell linters
* Split GHC checkers into separate files
|
|
|
|
|
|
* Use rubocop's JSON output format (resolves #339)
Rubocop's emacs formatter seems to have changed format in some
not-so-ancient version. The JSON formatter should provide a more stable
interface than parsing lines with a regex.
The JSON formatter was introduced in mid-2013, so it should be safe to
assume available in any reasonably-modern environment. The oldest
currently-supported version of ruby (according to ruby-lang.org) was
not supported by rubocop until 2014.
* Rubocop: Use global function for GetType
* Rubocop: Use scope prefix in GetType
* Rubocop: Update command_callback test
* Rubocop: add end_col to Handle
|
|
* Use different reporter to support older versions of jscs
* Add test and make more consistent with other code
* Add documentation for jscs
* Add more test coverage
|
|
supported versions
|
|
|
|
|
|
|
|
* Fix option passing to cpplint
|
|
|
|
|
|
|
|
* Add documentation for hadolint (doc/ale-hadolint.txt)
* Allow `hadolint` linter to run via docker image
These changes enable the `hadolint` linter to run via the author's
docker image, if present. Three modes are supported:
* never use docker;
* always use docker; and
* use docker as a failback.
|
|
|
|
connections via programs
|
|
* linters/lua/luacheck: Show error code in message
|
|
|
|
* Add profile, other options to the perlcritic linter
|
|
like the other linters
|
|
* Adds an option to pass additional arguments to the verilog/verilator linter
The new otion is g:ale_verilog_verilator_options
+ doc
* Spell check verilog linter doc file
* Add entries to the verilog linters in the doc table of content
* Vader test for verilog/verilator linter args option verilog_verilator_options
|
|
Elm linter shows full error ranges
|
|
|
|
* Remove style classification from E999
* Update test_flake8_handler to reflect E999 changes
|
|
|
|
|
|
|
|
|
|
* Add display of the pylint symbol name after the message.
* Update test to pass.
|
|
* Improve elm linter
Some types of errors do not return nice JSON.
Show them on the first line instead of showing nothing.
* Remove unnecessary properties from elm linter
* Add a vader test for elm-make linter
* Test non-JSON elm-make errors are shown
|
|
instead of position for the columns
|
|
and handling of end line and column numbers
|
|
Add a clangcheck linter
|
|
Detect compille_commands.json files for clang-tidy
|
|
|
|
|
|
some reason
|
|
|
|
* Use locally-installed PHPCS if available
* Add author
* Add configuration options
* Escape executable
* Add tests
|
|
|
|
|
|
* handle column number in javac linter
* Updated tests with column number for javac errors.
* Updated tests with column number for javac errors.
|
|
|
|
* TSLint: distinguish warnings from errors
* Test for TSlint warning/error distinguishing code added.
|
|
* Strip color from Crystal compiler output
* Don't lint files if the file doesn't exist
* Lint files if they are readable
|
|
|