toHavePropertiesWithValues
matcher function provides confusing message, when assertion fails
#6
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.
Consider following code snippet.
Above I intentionally show erroneous scenario, and got this message, which makes me think that expected object is empty or not present at all.
What I expect to see is:
Looking inside
toHavePropertiesWithValues
function at https://github.com/uxebu/jasmine-matchers/blob/master/src/toHave.js#L114, I found, that when building message, you remove all falsy properties from the object. Instead, on actual object you should remove only those properties, which are not present on expected one.Fixed the issue.