Improve the formatting of descriptions of Types #1895
Closed
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 PR adds a new type
TypeDescriptionUtility
that includes some logic to improve the readability where type names are being included in test output. In particular, LINQ result sets are identified and made human-readable. This functionality was originally written for #1812 but was extracted to its own independent PR -- as such this functionality is initially used directly inDataTableCollection
,DataColumnCollection
andDataRowCollection
assertions. It has also been applied to formatting of the type name inTypeSelectorAssertions
. The new functionality is unit-tested, andreleases.md
has been updated to describe the change.IMPORTANT