ale/test/command_callback/ruby_paths at master - marc/ale

marc/ale

Archived

This repository has been archived on 2024-07-19. You can view files and clone it, but cannot push or open issues or pull requests.

History

Justin Searls 2cfa09e02d 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?	2018-12-10 14:02:32 -07:00
..
with_config	Adds standardrb linter (#2133 )	2018-12-10 14:02:32 -07:00
dummy.rb	Add ruby fixer using `rubocop --auto-correct` (#689 )	2017-06-25 20:04:14 +01:00

Justin Searls 2cfa09e02d 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?

2018-12-10 14:02:32 -07:00

with_config Adds standardrb linter (#2133 ) 2018-12-10 14:02:32 -07:00

dummy.rb Add ruby fixer using rubocop --auto-correct (#689 ) 2017-06-25 20:04:14 +01:00