If you’re interested in translating or adapting this post, please email us first .

You will hardly find a Ruby developer who hasn’t heard about RuboCop, the Ruby linter and formatter. And still, it is not that hard to find a project where code style is not enforced. Usually, these are large, mature codebases, often successful ones. Fixing linting and formatting can be a challenge if it wasn’t set up correctly from the get-go. So, your RuboCop sees red! Here’s how to fix it.

Disclaimer: This article is being regularly updated with the best recommendations up to date; take a look at a Changelog section.

In this post, I will show you how we at Evil Martians touch up codebases of our customers in 2020: from quick and dirty hacks to proper Standard-enforced style guides, and our own patented way to use Standard and RuboCop configs together.

Style matters

Let’s pretend I have to convince you to follow code style guidelines (I know, I know I don’t have to!)

Here are the arguments I would use:

Developers understand each other much better when they speak write the same language.

write the same language. Onboarding new engineers becomes much easier when the code style is standardized.

Linters help to detect and squash bugs in time.

No more “single vs. double quotes” holy wars (double FTW)!

That was all the theory for today. Time for practice!

TODO or not TODO

So, you have joined a project with no style guide or with a .rubocop.yml that was added years ago. You run RuboCop, and you see something like:

$ bundle exec rubocop 3306 files inspected, 12418 offenses detected

Flocks of noble knights developers tried to slay the beast fix the offenses but gave up. But that doesn’t stop you—you know the magic spell:

$ bundle exec rubocop --auto-gen-config Added inheritance from ` .rubocop_todo.yml ` in ` .rubocop.yml ` . Created .rubocop_todo.yml. $ bundle exec rubocop 3306 files inspected, no offenses detected

That was simple! Toss the coin to your…

Let’s take a closer look at what --auto-gen-config flag does:

First, it collects all the offenses and their counts;

then, it generates a .rubocop_todo.yml where all the current offenses are ignored;

where all the current offenses are ignored; and finally, it makes .rubocop.yml inherit from .rubocop_todo.yml .

That is the way to set the status quo and only enforce style checks for new code. Sounds smart, right? Not exactly.

The way .rubocop_todo.yml handles “ignores” depends on the cop types and the total number of current offenses:

For metrics cops (such as Layout/LineLength ), the limit ( Max ) is set to the maximum value for the current codebase.

), the limit ( ) is set to the maximum value for the current codebase. All cops could be disabled if the total number of offenses hits the threshold (only 15 by default).

So, you end up with anything goes situation, and that defeats the purpose.

This article covers this problem in more detail.

What does it mean for a typical legacy codebase? Most of the new code would be ignored by RuboCop, too. We made the tool happy, but are we happy with it?

Hopefully, there is a way to generate a better TODO config by adding more options to the command:

bundle exec rubocop \ --auto-gen-config \ --auto-gen-only-exclude \ --exclude-limit = 10000

Where --auto-gen-only-exclude force-excludes metrics cops instead of changing their Max value, and --exclude-limit sets the threshold for the exclusion (set to some large enough number to avoid disabling cops completely).

Another approach for dealing with legacy codebases is to run RuboCop only for modified lines of code. Take a look at those tools: rubocop_lineup and Pronto RuboCop plugin.

Now your .rubocop_todo.yml won’t affect your new files or entirely new offenses in the old ones.

RuboCop doesn’t only help with style—it also saves you from common mistakes that can break your code in production. What if you had some bugs and ignored them in your TODO config? What are the cops that should never be ignored? Let me introduce the RuboCop strict configuration pattern.

You shall not pass: introducing .rubocop_strict.yml

There are a handful of cops that must be enabled for all the files independently of the .rubocop_todo.yml . For example:

Lint/Debugger —don’t leave debugging calls (e.g., binding.pry ).

—don’t leave debugging calls (e.g., ). RSpec/Focus (from rubocop-rspec )—don’t forget to clear focused tests (to make sure CI runs the whole test suite).

We put such cops into a .rubocop_strict.yml configuration file like this:

inherit_from : - .rubocop_todo.yml Lint/Debugger : # don't leave binding.pry Enabled : true Exclude : [] RSpec/Focus : # run ALL tests on CI Enabled : true Exclude : [] Rails/Output : # Don't leave puts-debugging Enabled : true Exclude : [] Rails/FindEach : # each could severely affect the performance, use find_each Enabled : true Exclude : [] Rails/UniqBeforePluck : # uniq.pluck and not pluck.uniq Enabled : true Exclude : []

Then, we replace the TODO config with the Strict config in our base .rubocop.yml configuration file:

inherit_from: - - .rubocop_todo.yml + - .rubocop_strict.yml

The Exclude: [] is crucial here: even if our .rubocop_todo.yml contained exclusions for strict cops, we nullify them here, thus, re-activating these cops for all the files.

One Standard to rule them all

One of the biggest problems in adopting a code style is to convince everyone on the team to always use double-quotes for strings, or to add trailing commas to multiline arrays, or ro <choose-your-own-controversal-style-rule>? We are all well familiar with bikeshedding.

Bozhidar Batsov launched a survey on RuboCop defaults to improve the configuration for the upcoming 1.0 release. Please, leave your feedback!

RuboCop provides a default configuration based on the Ruby Style Guide. And you know what? It’s hard to find a project which follows all of the default rules, there are always reconfigured or disabled cops in the .rubocop.yml .

That’s okay. RuboCop’s default configuration is not a golden standard; it was never meant to be the one style to fit them all.

Should Ruby community have the only style at all? It seems that yes, we need it.

I think the main reason for that is the popularity of auto-formatters in other programming languages: JavaScript, Go, Rust, Elixir. Auto-formatters are usually very strict and allow almost none or zero configuration. And developers got used to that! People like writing code without worrying about indentation, brackets, and spaces; robots would sort it all out!

Check out this lightning talk and let Justin Searls convince you to switch to Standard.

Thankfully, Ruby’s ecosystem has got you covered: there is a project called Standard, which claims to be the one and only Ruby style guide.

From the technical point of view, Standard is a wrapper over RuboCop with its custom configuration and CLI ( standard ).

Unfortunately, Standard lacks some RuboCop features that are essential at the early stages of a style guide’s adoption: it is not possible to use .rubocop_todo.yml or any other local configuration. It also doesn’t support RuboCop plugins or custom cops.

But we can still use Standard as a style guide while continuing to use RuboCop as a linter and formatter!

For that, we can use RuboCop’s inherit_gem directive:

# .rubocop.yml # We want Exclude directives from different # config files to get merged, not overwritten inherit_mode : merge : - Exclude require : # Performance cops are bundled with Standard - rubocop-performance # Standard's config uses this custom cop, # so it must be loaded - standard/cop/semantic_blocks inherit_gem : standard : config/base.yml inherit_from : - .rubocop_strict.yml # Sometimes we enable metrics cops # (which are disabled in Standard by default) # # Metrics: # Enabled: true

That is the configuration I use in most of my OSS and commercial projects. I can’t say I agree with all the rules, but I definitely like it more than the RuboCop’s default. That is a tiny trade-off if you think about the benefit of not arguing over the style anymore.

Don’t forget to add standard to your Gemfile and freeze its minor version to avoid unexpected failures during upgrades:

gem "standard" , "~> 0.2.0" , require: false

Although the approach above allows you to tinker with the Standard configuration, I would not recommend doing that. Use this flexibility to extend the default behavior, not change it!

Beyond the Standard

RuboCop has a lot of plugins distributed as separate gems: rubocop-rspec , rubocop-performance , rubocop-rails , rubocop-md , to name a few.

Standard only includes the rubocop-performance plugin. We usually add rubocop-rails and rubocop-rspec to our configuration.

For each plugin, we keep a separate YAML file: .rubocop_rails.yml , .rubocop_rspec.yml , etc.

Inside the base config we add these files to inherit_from :

inherit_from : - .rubocop_rails.yml - .rubocop_rspec.yml - .rubocop_strict.yml

Our .rubocop_rails.yml is based on the configuration that existed in Standard before they dropped Rails support.

There is no standard RSpec configuration, so we had to figure out our own: .rubocop_rspec.yml .

We also usually enable a select few custom cops, for example, Lint/Env .

In the end, our typical RuboCop configuration for Rails projects looks like this👇

# .rubocop.yml inherit_mode : merge : - Exclude require : - rubocop-performance - standard/cop/semantic_blocks - ./lib/cops/lint/env.rb inherit_gem : standard : config/base.yml inherit_from : - .rubocop_rails.yml - .rubocop_rspec.yml - .rubocop_strict.yml Lint/Env : Enabled : true Include : - ' **/*.rb' Exclude : - ' **/config/environments/**/*' - ' **/config/application.rb' - ' **/config/environment.rb' - ' **/config/puma.rb' - ' **/config/boot.rb' - ' **/spec/*_helper.rb' - ' **/spec/**/support/**/*' - ' lib/generators/**/*'

Feel free to use it as an inspiration for your projects that could use some RuboCop’s tough love.

RuboCop plays a vital role in the Ruby world and will stay TOP-1 for linting and formatting code for quite a long time (though competing formatters are evolving, for example, rubyfmt and prettier-ruby). Don’t ignore RuboCop; write code in style 😎

Don’t hesitate to drop us a line if you want us to take a look at your codebase and help you set up the best Ruby (or Go, or JavaScript, or TypeScript, or Rust…) practices.

Changelog

1.1.0 (2020-03-27)