Make toBe matcher error message more helpful for objects and arrays

[thymikee]

Do you want to request a feature or report a bug?
Enhancement

What is the current behavior?
Using expect(object).toBe(otherObject) fails with default message.

What is the expected behavior?
Since this is a common mistake, we could detect if the received entity is an object or an array and display helpful message like:

Looks like you wanted to test for object/array equity with strict `toBe` matcher. 
You probably need to use `toEqual` instead.

We can figure out better wording, this is just an idea :)

[rogeliog]

Would we always show that message for arrays/objects or would we also do a toEquals behind the scenes and then show the message?

[thymikee]

We may do this, but only to show, that this expectation would work with toEqual. It would still throw of course.

[rogeliog]

Correct! I'm happy to help with it

[github-actions]

This issue 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.