v2.2.0

With this version update, rubocop-bitcrowd adapts to RuboCop's new modularized architecture of having separate gems for different cop targets (Rails, Rspec, Performance).

rubocop-bitcrowd includes separate configuration files for each RuboCop gem. To continue using the previous configuration including rules for Rspec and Rails, add the respective gems to your Gemfile:

gem 'rubocop-rails', require: false
gem 'rubocop-rspec', require: false

And update the configuration in your .rubocop.yml to include the bitcrowd rules:

inherit_gem:
  rubocop-bitcrowd:
    - .rubocop.yml
    - .rubocop-rspec.yml
    - .rubocop-rails.yml

As a new addition, rubocop-bitcrowd now also includes rules for the rubocop-performance gem. To use them, add the gem to your Gemfile:

gem 'rubocop-performance', require: false

Then include the bitcrowd config in your .rubocop.yml:

inherit_gem:
  rubocop-bitcrowd:
    - .rubocop.yml
    - .rubocop-rspec.yml
    - .rubocop-rails.yml
    - .rubocop-performance.yml

Potentially breaking changes:

• #34 Extract rails cops into separate configuration based on rubocop-rails, following the modularization of rubocop itself.

New features:

• #32 add possibility to include rubocop-performance cops.

v2.1.3

This releases silences some deprecation warnings and locks down the minimal rubocop version rubocop-bitcrowd depends on.

Fixes:

• #31 Fix deprecation warning by moving LineLength cop from Metrics to Layout and lock the Rubocop version to >= 0.78.0 and < 0.79.
• #31 Lock down the minimal rubocop version we depend on. Similar to rubocop-rspec we're only setting the lower boundary now.