Rubycritic VS rubocop

You should consider using RubyCritic if you want a single place to review code improvements for your project. Including RubyCritic in your development process will certainly reduce the time a development team spends working on technical debts. Most technical debts will be mapped out at development time.

It's also possible to write unit tests in order to better understand or surface your assumptions about a legacy application. I'd also consider running rubycritic against legacy code, to see where the code smells and other hot spots lie.

RubyCritic: a gem that wraps around static analysis gems such as Reek, Flay, and Flog to provide a quality report of your Ruby code.

Still kinda pissed about that. It's the same as with Bens. We will reach equality by removing representation, yay? At least rubocop didn't kneel

1) Many cops have configurable attributes. See for example Layout/SpaceInsideParens. You could open a merge request to add configurable attributes to other cops like Layout/SpaceInsidePercentLiteralDelimiters - as long as the default behaviour stays the same, it will probably get accepted. I do suggest opening an issue with a detailed list of what attributes you would like to add to which cops first, and getting a green light from a maintainer. Check the Contributing section on the website, which also contains a link to the contribution guidelines.

rubocop - a linter for Ruby code that helps you follow a style guide used by the Ruby community, or even apply your own code style. It's very useful to set standards in your team and avoid silly conflicts about spaces and tabs.

The default configuration for RuboCop is placed in its configuration home directory (~/.config/rubocop/default.yml), and all other config files inherit from it. This means that when setting up your project configuration, you only need to make changes that are different from the default. This could mean enabling or disable certain checks or altering their behavior if they accept any parameters.

No, it never has been, and there are no plans to make it so. It has been much discussed, but it seems intractable...

You might consider installing Rubocop. It’s a code analyzer and formatter that will give you suggestions based on the Ruby style guide. Note that any Ruby that works with the interpreter is “valid”, but Ruby is a highly aesthetic programming language.

Rails developers usually put all the deps in the Gemfile, including dev tools, such as RuboCop. RuboCop is a linter, and linters must be fast. RuboCop itself complies with this statement but running it via Bundler may not.

I maintain dozens of gems, with varying requirements for supporting Ruby releases from "ye olden tyme". Every time I dust off a gem to update it, deprecating old Rubies as I go, I have to keep the rubocop version in careful sync. Many times I have forgotten the need to keep rubocop pegged to an ancient version and have spent valuable time upgrading the code to newer Rubocop releases, and newer Ruby styles. Too often I remember the Ruby support requirement once the updates hit CI.

RuboCop