Issue1092 #1097
Merged
Issue1092 #1097
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
dennisdoomen
approved these changes
Jul 25, 2019
Member
Author
|
I found another way to do it, which I believe to be better, simpler and more idiomatic. |
dennisdoomen
approved these changes
Jul 25, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reformatting a failure message that has already been formatted can throw a
FormatException.This PR avoids reformatting formatted failure messages in
SatisfyRespectively.In order to get the inner failure messages after "Expected collection to satisfy all inspectors..."
I introduced
WithPreFormattedFailure(string).I'm not sure if
formattedFailureMessageneeds to be cleared just asexpectationis withClearExpectation().This fixes #1092