fix: collections matchers should display type of expectation #408
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.
The collections matchers ConsistOf() and ContainElements() are often
used with collections of consistent type, for example:
Expect(t).To(ConsistOf(1, 2, 3))
When this fails, it's more helpful to report:
...to contain elements <[]int | len:3, cap:3>: [1, 2, 3]
Than the previous behavior:
...to contain elements <[]interface {} | len:3, cap:3>: [1, 2, 3]
By using []interface{} only where there's no other option we make it
easier to debug issues - especially for types that display identically.