-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Array matching #15091
Fix Array matching #15091
Conversation
Fixes matching type Array for arrays created in a new context.
|
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome, thanks!
Oh, can you sign the CLA? |
No. |
That's unfortunate, I don't think we'll be able to merge the PR in that case 🤔 https://github.com/jestjs/jest/blob/b7ae0b85e981eae0e373d98ab2ae8fe497d90027/CONTRIBUTING.md#contributor-license-agreement-cla
|
That is quite unfortunate, but I will not be sharing my full name, address, and all the other information you should not share with random organizations to contribute a few lines of code. Hopefully someone else willing to give this information away will be able to fix this issue! |
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. |
Fixes matching type Array for arrays created in a new context.
Summary
Fixes #15025
Jest does not correctly match arrays created in different contexts. This causes it to incorrectly match arrays from HTTP requests made by native fetch, failing tests when they should be passing.
Test plan
Added a unit test to asymmetricMatchers for arrays created in a new context.
Before:
After: