summaryrefslogtreecommitdiff
path: root/doc/ale-scala.txt
diff options
context:
space:
mode:
authorJustin Searls <searls@gmail.com>2018-12-10 16:02:32 -0500
committerBjorn Neergaard <bjorn@neersighted.com>2018-12-10 14:02:32 -0700
commit2cfa09e02d65cd06649fb1ae5f988b7a110a124d (patch)
treed92176e4ddc7dfa5b42c7018ca568d0a73b156a5 /doc/ale-scala.txt
parentc899ff3523e716efb71907234d7ca2e740c9e761 (diff)
downloadale-2cfa09e02d65cd06649fb1ae5f988b7a110a124d.zip
Adds standardrb linter (#2133)
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?
Diffstat (limited to 'doc/ale-scala.txt')
0 files changed, 0 insertions, 0 deletions