[Bug]: toMatchObject incorectly handles nulls in lists of sets #14599
Comments
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
|
Is this a bug or expected behaviour? |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
|
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
|
Deffo a bug - PR welcome! 😀 |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
|
@SimenB |
|
@SimenB kindly reminder 😄 |
|
@bensternthal / @cpojer would appreciate a review on the PR 🙌 |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
|
bump |
Version
29.7.0
Steps to reproduce
For this match
Expected behavior
It should throw an exception
Actual behavior
But it doesn't throw an exception. What's interesting is that
behaves as expected.
Additional context
No response
Environment
System: OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm) CPU: (8) x64 Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz Binaries: Node: 20.6.1 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 9.8.1 - /usr/local/bin/npm pnpm: 8.7.5 - /usr/local/share/npm-global/bin/pnpm npmPackages: jest: ^29.7.0 => 29.7.0The text was updated successfully, but these errors were encountered: