Move Including from EquivalencyAssertionOptions to SelfReferenceEquivalencyAssertionOptions #1495
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.
In 69c5231
SelfReferenceEquivalencyAssertionOptionswas split into a generic and non-generic part, where the non-generic is used for thedefaultsinAssertionOptions.Excluding(Expression<Func<IMemberInfo, bool>> predicate)was kept in the shared base class, butIncluding(Expression<Func<IMemberInfo, bool>> predicate)was moved to the generic child class, even though it does not rely on the generics.With the change in this PR one can now write a test like