Fix deep equal comparison between promises #217
Merged
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.
Fix issue #216 by explicitly checking Promise instances
Background
I found that sinon spy
calledWith
does not properly check promises equality and always returns true.Reported here
Solution
Simple fix, I've just added explicit Promise instance checking similar to how
Error
orRegExp
are checked. I've also added a couple tests to verify it. I haven't added a test to check promises against other type of data as that was already working but I can add a explicit test for that case if you want.How to verify
npm t
(or just check the ci)