Added native support for XDocument, XElement and XAttribute properties and fields to BeEquivalentTo #1572
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
dennisdoomen
force-pushed
the
Feature/XElementEquivalency
branch
2 times, most recently
from
99fbb11
to
de2f23a
Compare
…s and fields to BeEquivalentTo
dennisdoomen
force-pushed
the
Feature/XElementEquivalency
branch
from
de2f23a
to
07711f6
Compare
dennisdoomen
changed the title
jnyrup
reviewed
May 23, 2021
jnyrup
approved these changes
May 23, 2021
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.
BeEquivalentTonow supports properties and fields of typeXDocument,XElementandXAttribute. This will make graphs with such type behave the same way as callingBeEquivalentToon anXElementdirectly. ForXAttribute, we use itsBemethod.DocumentationCan't think of a good place to mention thisFixed #1535