Improve list/map support for ObjectsAreEqual #1058
Open
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.
Summary
Function
ObjectsAreEqual
now compares two objects of type array/slice/map by iterating over each element. When two objects contain the same value but have different types, the function will now returntrue
.Changes
ObjectsAreEqualValues
inassertion.go
is changed.listsAreEqualValues
andmapsAreEqualValues
are added.Motivation
Currently,
assert.EqualValues
would fail when two objects are of type array/slice/map and contain values of different types.But,
assert.EqualValues
should always compare objects by value. So the above code should idealy pass.Related issues
Closes #1057