-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
add example to reproduce defect of serializeQueryArgs with skipToken #4708
add example to reproduce defect of serializeQueryArgs with skipToken #4708
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 586144b:
|
@@ -125,6 +125,12 @@ const api = createApi({ | |||
return true | |||
}, | |||
}), | |||
queryWithDeepArg: build.query<string, { param: {nested: string} }>({ | |||
query: ({param: {nested}}) => nested, | |||
serializeQueryArgs: ({queryArgs}) => { |
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.
Here queryArgs have { param: { nested: string } }
type. But called with skip token.
So queryArgs.param
is undefined and then queryArgs.param.nested
throws Cannot read property of undefined
9384f72
to
586144b
Compare
Thanks! |
Test that reproduce the defect described in #3151