fix: fix any() for symbols and bigints (#10179)

[ninevra]

Summary

Adds clauses to expect's Any.asymmetricMatch() to handle Symbol and BigInt analogously to other primitives, i.e., using typeof instead of instanceof. This makes expect.any()'s behavior more consistent across primitive types.

Adds a clause to Any.asymmetricMatch() to exclude null from expect.any(Object). This makes expect.any()'s behavior more consistent with its documentation; null is not created with the Object constructor, and so should not be matched.

Closes #10179.

Test plan

Added checks to the list in asymmetricMatchers.test.ts test('Any.asymmetricMatch())' to cover the changed behavior.

[thymikee]

LGTM, left a note on the null

[thymikee]

this is kinda breaking, null is and Object in JS after all. Please revert

[ninevra]

I've added a commit reverting the change to null handling, as requested.

If any(Object) matching null is intended, would there be interest in documenting that? It seems unlikely to me that someone asserting a value is an Object would intend to allow null. This is also an area where Jest differs from Jasmine's original implementation.

[thymikee]

@SimenB @jeysal thoughts? I don't have strong feelings about treating null as Object. It's valid from JS point of view, but it's also often confusing. If we're about to change it, we need to do it in a major version bump because it's technically breaking.

[SimenB]

typeof null === 'object' is one of my least favorite parts of the language, but I don't think we should deviate from that - I think that'll just cause more confusion

[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.