Update toStrictEqual failure message

[natealcedo]

Summary

This pull request updates the failure message returned by toStrictEqual so that it is more inline with what #7105 envisions.

Test plan

The matcher is tested with a snapshot test.

Here are a few screenshots of the before and after along with the test file.

Before: (I had to minimize the image to fit both tests in one screen)

After:

[codecov-io]

Codecov Report

Merging #7224 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #7224      +/-   ##
==========================================
+ Coverage   66.55%   66.59%   +0.03%     
==========================================
  Files         237      237              
  Lines        9317     9318       +1     
  Branches        3        4       +1     
==========================================
+ Hits         6201     6205       +4     
+ Misses       3115     3112       -3     
  Partials        1        1

Impacted Files	Coverage Δ
packages/expect/src/matchers.js	99.37% <100%> (+1.89%)	⬆️

---

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 cdf7a22...1eaf254. Read the comment docs.

[SimenB]

please include the URL as well, so it's clickable outside of github 🙂

[natealcedo]

Oops. Small hickup. Will do!

[pedrottimark]

Thank you very much. Left one suggestion (first time I used the new feature in GitHub :)

To document the goal:

• .toStrictEqual omit minified values because they distract from Differences
• .not.toStrictEqual align Expected and Received values

[natealcedo]

@pedrottimark I don't see any suggestions on my end.

Could you further explain both points? I don't quite understand the first point. Your second point, what do you mean by align Expected and Received values. Do you mean something like this?

Expected: 
  { "a": "a" }

Received:
  { "b": "b" }

I was just following the style on the right as per our previous discussion.

[pedrottimark]

Jest trims extra space in message, but let’s omit trailing newline for other dependents of expect package:

Suggested change

	`Received: ${printReceived(received)}\n`
	`Received: ${printReceived(received)}`

[natealcedo]

I've updated this in the code. I just did a commit --amend --no-edit and forced push to my branch. Hence, you're not gonna see a new commit. Just in case you get confused by the lack of commits. :)

[pedrottimark]

@natealcedo You have my apology if the comment was double confusing :)

1. Sorry such a new feature that I didn’t realize I had not submitted the comment:

#7224 (review)

2. What you did is correct for both positive and negative case.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.