Re: "I don't use RuboCop in personal projects. In my consultant work some
clients do, some don't. Those that do have different configuration files
because no two Ruby teams have the same preferences"
This is a red herring. Most of the Rubocop failures against the standard
Rubocop config are due t
I like this idea. It would be nice newly generated rails app could pass the
rubocop checking with its default configuration. I also suggest adding two
more options to .rubocop.yml,
TargetRubyVersion and Rails/Enabled: true. Together this makes them default
configuration for new rails app rubocop
