Fix formatting inconsistencies for array values in MockException.Message #380
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 fixes #321.
Two inconsistencies have been reported in how arrays and arrays containing null references are reported in the "expected invocation" and "performed invocations" part of a
MockException
message:In "expected invocation", arrays are completely omitted in the message.
In "performed invocations", null references are omitted in an array value dump.
This commit fixes both issues, and additionally ensures that in case of non-terminating or long sequences, only the first 10 elements are printed and the rest gets abbreviated as
", ..."
.