feat(toHaveValue): Enhanced error message with type information on loose equality

[maltebaer]

What:

As discussed in #218 the error message of toHaveValue was enhanced by type information if the received and expected value have loose equality.

Why:

To improve DX.

How:

The expected and received values are checked for loose equality and enhanced by type information if loose equality is given.

Checklist:

• Documentation (N/A)
• Tests
• Updated Type Definitions (sorry, not so sure where to do that)
• Ready to be merged (once updating of Type Definitions is done)

If you could point me to where I can update the Type Definitions, I would be happy to do so.

[codecov]

Codecov Report

Merging #219 into master will not change coverage by %.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #219   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           19        19           
  Lines          240       245    +5     
  Branches        58        59    +1     
=========================================
+ Hits           240       245    +5     

Impacted Files	Coverage Δ
src/to-have-value.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c80448f...4ab63bd. Read the comment docs.

[maltebaer]

Hey guys, could you give me some advice regarding the Type Definitions and why the checks are failing? When I run npm run validate locally everything passes and I'm don't really know what to get from the Job log on Travis CI.

[eps1lon]

Looks like this only fails with node 13. The branch is also out of date. Try updating it with master.

Then you can investigate by using node 13 locally. Should throw the same error.

[maltebaer]

I updated to node 13.11.0 and it still doesn't fail locally. Updated with master too.

[maltebaer]

Sorry to bother again, but when I try to commit the changes the husky > pre-commit hook fails.
I don't fully understand why or how to resolve this. To me it seems as if it is due to the formatting of the console output.

Can you give me a hint on how to solve this? Or is it okay to use the --no-verify flag in this case?

[eps1lon]

No idea. I have husky disabled globally anyway.

[eps1lon]

@all-contributors please add @mfelmy for code

[allcontributors]

@eps1lon

I've put up a pull request to add @mfelmy! 🎉

[eps1lon]

@mfelmy Nice work, thanks!

[gnapse]

🎉 This PR is included in version 5.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[maltebaer]

Thank you very much for helping me on my first pull request.

[gnapse]

@all-contributors please add @mfelmy for code, test

[allcontributors]

@gnapse

I've put up a pull request to add @mfelmy! 🎉

[gnapse]

@all-contributors please add @mfelmy for code, test

[allcontributors]

@gnapse

I've put up a pull request to add @mfelmy! 🎉