fix: preserve search params in "onUnhandledRequest" messages

[nagadevkrishna]

• Fixes Preserve the original request URL in "onUnhandledRequest" warnings #2125

[kettanaito]

This does solve the problem but it changes the other use cases we have for toPublicUrl.

I think a far better approach is to keep these changes scoped to the immediate problem area: the toPublic() usage in the onUnhandledRequest.ts.

msw/src/core/utils/request/onUnhandledRequest.ts

Lines 24 to 27 in e83a669

	const url = new URL(request.url)
	const publicUrl = toPublicUrl(url)
	const unhandledRequestMessage = `intercepted a request without a matching request handler:\n\n \u2022 ${request.method} ${publicUrl}\n\nIf you still wish to intercept this unhandled request, please create a request handler for it.\nRead more: https://mswjs.io/docs/getting-started/mocks`

Let's try something like this:

const url = new URL(request.url)
const publicUrl = toPublicUrl(url) + url.search

This way both relative and absolute URLs will be printed correctly but will also have any search parameters preserved.

Then, we can modify the tests in onUnhandledRequest.test.ts to include two new scenarios:

• Unhandled request with a relative URL and search params;
• Unhandled request with an absolute URL and search params.

[nagadevkrishna]

Thanks for the suggestion. Made changes now and pushed to PR again.

[kettanaito]

Thanks for tackling this, @nagadevkrishna! I left a suggestion, let me know what you think about it.

[kettanaito]

This looks fantastic!

[nagadevkrishna]

awesome!

[kettanaito]

Don't close it just yet. I need to merge it so it gets to MSW. Be patient.

[kettanaito]

Welcome to the contributors, @nagadevkrishna! 👏

[kettanaito]

Released: v2.2.14 🎉

This has been released in v2.2.14!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i msw@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.