Define rspec matcher only when rspec is defined #529
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swelther
force-pushed
the
fix/define-rspec-matcher-when-rspec-is-defined
branch
from
86ee99f
to
ac7022a
Compare
karunkumar1ly
pushed a commit
to edcast/paranoia
that referenced
this pull request
Feb 6, 2024
Co-authored-by: Sebastian Welther <sebastian.welther@sumcumo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our CI tests run in a
CIenvironment, so the rspec matcher is not defined. This PR changes the definition of the matcher so it is always defined when RSpec itself is defined.Added no tests because not really possible. The gem itself does not use RSpec for tests.