summaryrefslogtreecommitdiff
path: root/ale_linters/elixir
AgeCommit message (Collapse)Author
2017-04-18Add a function for getting matches, and use it to simplify a lot of codew0rp
2017-04-15Make code more consistentw0rp
2017-03-30Remove 'col' from linters where it is hardcoded to 1 (#434)Adriaan Zonnenberg
* Remove 'col' from linters where it is hardcoded to 1 When 'col' is 1, the first column will get highlighted for no reason. It should be 0 (which is the default). In the scalac linter there was also a check about the outcome of `stridx`. It would set l:col to 0 if it was -1, and then it uses `'col': l:col + 1` to convert the outcome of `stridx` to the actual column number. This will make 'col' equals 1 when there is no match. We can remove the check because `-1 + 1 = 0`. * Remove outdated comments about vcol vcol was added as a default, and the loclists that follow these comments do not contain 'vcol' anymore
2017-03-27Use the same formatting as other files for the dogma linter file, and cover ↵w0rp
the Handler function with tests
2017-03-23Add the dogma checker.Blaž Hrastnik
2017-02-26Copy all loclist items returned from handlers, and set up defaults for ↵w0rp
convenience
2017-02-22Fix Credo's line-matching pattern (#360)Jon Parise
* Fix Credo's line-matching pattern In d3e7d3d5, the line matching pattern was changed to handle filenames other than `stdin`. Unfortunately, this broke the pattern's ability to reliably extract both line and column numbers because the latter is an optional match and the filename portion was very greedy. This resulted in line numbers being discarded (treated as part of the filename) and column numbers being interpreted as line numbers. This change simplifies the pattern to only anchor on the line's suffix, ignoring the filename portion entirely. Alternatively, we could use vim's `\f` ("file name characters") class, but that could still run into problems when `:`'s naturally appear in the filename. * Add a Vader test case for the Credo handler
2017-02-09Pass the buffer's filename to CredoJon Parise
By default, Credo attributes input from STDIN as though it came from a file named `stdin`. This change passes the buffer's filename, too, so that Credo can use that information when applying its configuration. This is a nice improvement because files like `mix.exs` are normally excluded from Credo-based linting. Previously, ALE would show lint warnings for those files as they were edited. Now, they are correctly honor the Credo configuration and don't produce lint output.
2017-01-30Dockerfile linting via hadolint (#282)Łukasz Jan Niemier
* Add hadolint linter for Dockerfiles * Fix path * Fix typo * Update docs
2017-01-22Add a script for custom checks to enforce using the abort flag for functions ↵w0rp
and trailing whitespace, and fix existing issues.
2016-10-21Add support for dot-seperate linters, improve linter testsBjorn Neergaard
This PR first and formost implements support for dot-seperate filetypes, a very trivial change. This closes #132 But more importantly, this PR vastly improves the test quality for `ale#linter#Get`. It enables us to reset the state of ale's internal linter cache, to facilitate better testing, as well as making use of mocked linters instead of depending on linters on disk (which may change). In addition, a dummy linter is defined to test the autoloading behavior. Header guards were removed from all linters as: * A: ale won't try and load linters if they already exist in memory * B: we can't reset state for testing if they can't be loaded again
2016-10-16Add linters for Elixir (#113)Łukasz Jan Niemier
* Add Credo linter for Elixir * Add requested changes TODO: check if all message types are covered in `if` chain. * Add information about Credo linter to README * Add information about Credo linter to doc