Add require: false
to Gemfile example
#123
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you run
require 'rspec/core'
before the appropriate timing,Kernel.#context
would be defined unexpectedly and you will get a warning when you load irb. The following Issue provides more information on this issue.This Gem executes
require 'rspec/core'
when loaded, so if it is loaded in a Rails app withBundler.require
it will cause this problem. This pull request solves this problem.rspec-retry/lib/rspec/retry.rb
Line 1 in 06a9595
Since the README already explains to write
require 'rspec/retry'
, there is no problem to explain to addrequire: false
like this.