-
-
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: comparing different URL
objects now return false
#14398
Conversation
|
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
In Node test environment everything works as you expect. This is only an issue with Jsdom. Better open an issue, because it can be that Jest is not the cause of this problem. |
Seems like you are hitting #13936. That issue got missed and locked unfortunately. Just open a new ticket. |
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. |
Even if we look at symbol properties, I think we can have a fast path that just checks the href like this PR proposed. @tr1ckydev would you be willing to restore your fork? |
@SimenB Sure, should I open a new PR? |
Yeah, unless this one just reopens 🙂 |
Done #14672 |
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. |
Summary
Previously, jest would report this test as PASS.
In this pull request, this gets fixed and jest properly compares the two URL objects and reports FAIL.
Test plan