This repository was archived by the owner on Nov 30, 2024. It is now read-only.
Revert "Always verify mocks at the end of each example." #1988
Conversation
This file contains hidden or 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
This reverts commit f989168. This is necessary to avoid the issue discussed in rspec/rspec-mocks#203. I'm reverting it so we can release 3.3. We may bring this back for 3.4 if we can find a better solution.
warning: possible reference to past scope - dbl
|
LGTM |
JonRowe
added a commit
that referenced
this pull request
Jun 11, 2015
Revert "Always verify mocks at the end of each example."
MatheusRich
pushed a commit
to MatheusRich/rspec-core
that referenced
this pull request
Oct 30, 2020
Revert "Always verify mocks at the end of each example."
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This reverts commit f989168.
This is necessary to avoid the issue discussed in rspec/rspec-mocks#203. I'm reverting it so we can release 3.3. We may bring this back for 3.4 if we can find a better solution.