-
-
Notifications
You must be signed in to change notification settings - Fork 515
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
Preserve the original request URL in "onUnhandledRequest" warnings #2125
Labels
bug
Something isn't working
good first issue
Good for newcomers
scope:browser
Related to MSW running in a browser
scope:node
Related to MSW running in Node
Comments
kettanaito
added
bug
Something isn't working
scope:node
Related to MSW running in Node
needs:triage
Issues that have not been investigated yet.
good first issue
Good for newcomers
and removed
needs:triage
Issues that have not been investigated yet.
labels
Apr 5, 2024
How to fix thisThe fix would be right here:
The reason we use
|
Hi, I made a change and raised the PR: #2128 |
Released: v2.2.14 🎉This has been released in v2.2.14! Make sure to always update to the latest version ( Predictable release automation by @ossjs/release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
good first issue
Good for newcomers
scope:browser
Related to MSW running in a browser
scope:node
Related to MSW running in Node
Prerequisites
Environment check
msw
versionNode.js version
v20.11.0
Reproduction repository
Always specify repros. Don't follow my lead.
Reproduction steps
onUnhandledRequest
callback:/fo/bar/?t=123
Current behavior
MSW prints a clean URL, making it hard to understand why my custom
onUnhandledRequest
logic is not matching this request:Expected behavior
MSW preserves the unhandled request URL as-is, which includes keeping its query parameters and fragments.
The text was updated successfully, but these errors were encountered: