PNG Rubocop Logo, Copyright (c) 2014 Bozhidar Batsov, MIT License, SVG Rubocop Logo, Gil Barbara, CC0 SVG Rubocop Logo, Copyright (c) 2014 Bozhidar Batsov, MIT License, SVG Rubocop Logo, Roberto Huertas, MIT Yukihiro Matsumoto, Ruby Visual Identity Team, CC BY-SA 2.5 SemVer.org Logo by @maxhaz SemVer.org Logo by @maxhaz

Rubocop::Ruby20

See the intro blog post!

This gem requires no other gems. It depends on rubocop, but does not require 'rubocop'.

Awareness of rubocop's lack of SemVer adherence isn't evenly dispersed in the Ruby community.

The Rubocop team has real reasons for not following SemVer, but if you've found this project their reasons likely weigh less, in your context (e.g. running rubocop from command line), than what brought you here.

Explanation of non-SemVer compliance, @bbatsov

The purpose of this gem is to constrain the rubocop dependency of a project in a SemVer compliant (Semantic Versioning) way that aligns with the the desired minimum compatible/supported Ruby version.

Adding this gem will facilitate the best practice of adding a ~> version constrained rubocop dependency, while minimizing the risk of a rubocop minor / patch upgrade breaking the build. See the official compatibility matrix (Rubocop documentation)

Stable

All releases of this gem are stable releases. The first version is 1.0.0.

Installation

Without bundler execute:

$ gem install 

Add this line to your application's Gemfile:

gem 'rubocop-ruby2_0', '~> 1.0', require: false

And then execute:

$ bundle

Or install it yourself as:

$ gem install rubocop-ruby2_0

Usage

The following is optional. We'll discuss why you might want to do this after you see what it does.

Add to the top of your project's .rubocop.yml configuration file:

inherit_gem:
  rubocop-ruby2_0: rubocop.yml

This has the same effect as you declaring the following in your .rubocop.yml:

AllCops:
  # remove if already present in your `.rubocop.yml` to gain the full benefit of this gem!
  TargetRubyVersion: 2.0
  # The sibling gems for newer versions of Ruby support the NewCops directive as soon as Rubocop adds it.
  # NewCops: enable

Let's talk about these settings.

TargetRubyVersion

Allowing this gem to manage the target ruby version means you can switch to a different gem within the family when you upgrade to the next version of Ruby, and have nothing else to change. A single line in the Gemfile, and you are done.

NewCops: enable

If you want to use this you'll have to upgrade to Ruby >= 2.4 and use the appropriate sibling gem, e.g. rubocop-ruby2_4.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Contributing

See CONTRIBUTING.md

Contributors

Contributors

Made with contributors-img.

License

The gem is available as open source under the terms of the MIT License License: MIT. See LICENSE for the official Copyright Notice.

Project Logos (rubocop-ruby3_1) See [docs/images/logo/README.txt][project-logos]
Organization Logo (rubocop-semver) Author: [Yusuf Evli][org-logo-author] Source: [Unsplash][org-logo-source] License: [Unsplash License][org-logo-license]

Code of Conduct

Everyone interacting in the Rubocop::Ruby20 project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

Versioning

This library aims to adhere to Semantic Versioning 2.0.0. Violations of this scheme should be reported as bugs. Specifically, if a minor or patch version is released that breaks backward compatibility, a new version should be immediately released that restores compatibility. Breaking changes to the public API will only be introduced with new major versions.

As a result of this policy, you can (and should) specify a dependency on this gem using the Pessimistic Version Constraint with two digits of precision.

For example:

spec.add_dependency "rubocop-ruby2_0", "~> 1.0"