summaryrefslogtreecommitdiff
path: root/ale_linters/ruby/standardrb.vim
AgeCommit message (Collapse)Author
2019-08-13Move ale#handlers#ruby#EscapeExecutable to ale#ruby#EscapeExecutableEddie Lebow
This function is generally applicable to Ruby, not just handling linter output.
2019-02-22#2132 - Replace all uses of foo_callback with foow0rp
2018-12-10Adds standardrb linter (#2133)Justin Searls
See: https://github.com/testdouble/standard StandardRB is to RuboCop what StandardJS is to ESLint. This commit naively copies the RuboCop linter and fixer to point at the standardrb executable. Any other adjustments are very minor (the only I can think of is that standardrb takes a `--fix` option instead of `--auto-correct`). This raises a confusing point to me as both developer and a user: since ale enables all linters by default, won't this run both RuboCop and StandardRB (the results of which will almost always be in conflict with one another)? How does ale already solve for this for the similar case of StandardJS and ESLint?