Fix compatibility issues with rspec-rails #121
Merged
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.
With 0.6.0, requiring
super_diff/rspec-rails
in the context ofrspec-rails
suddenly started failing. We try to requirerspec/version
so that we can have access to RSpec::Version. However,rspec-rails
does not depend on therspec
metagem, so RSpec::Versionis not a constant when using
rspec-rails
. In addition, this was nevercaught because it turns out that integration with
rspec-rails
was notbeing properly tested.
This commit fixes
super_diff
to reference RSpec::Core::Version (sincewe can always assume
rspec-core
has been loaded) and makes sure thatwe are testing it so the aforementioned problem does not occur again.
Fixes #120.