-
-
Notifications
You must be signed in to change notification settings - Fork 518
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
Request in worker.events.on('response:mocked', {request} is always null #2014
Comments
Hi, @canrozanes. I've already tackled this issue in #1992. Please update MSW to get the fix: npm i msw@latest Released in v2.1.5 (Release notes). Thanks. |
Hey @kettanaito sorry for the duplicate. Thanks for the fix. Also, is there a reason url is not properly populated in the response object? |
@canrozanes, do you mean the |
@kettanaito yes exactly! |
Discussed in #1991
Just converting it to an issue so that it can be tracked.
Originally posted by canrozanes January 22, 2024
Hi,
I was following the docs on life-cycle events and I was trying to assert on a response after making an API call.
I have the following piece of code that saves all the requests so that I can assert on the responses later.
I can clearly see that MSW sends a response in the browser network tab but when I add a debugger inside the 'response:mocked' callback, I see that all the request are null.
What could I be missing?
The text was updated successfully, but these errors were encountered: