-
-
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
Support a custom paramsSerializer on fetchBaseQuery #1594
Support a custom paramsSerializer on fetchBaseQuery #1594
Conversation
✔️ Deploy Preview for redux-starter-kit-docs ready! 🔨 Explore the source changes: 655d5ea 🔍 Inspect the deploy log: https://app.netlify.com/sites/redux-starter-kit-docs/deploys/61605f69cfde030008e9beb5 😎 Browse the preview: https://deploy-preview-1594--redux-starter-kit-docs.netlify.app |
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 c237581:
|
size-limit report 📦
|
seems very similar in spirit to the proposal in this issue: #1469 |
I didn't see that thread - I'll drop a comment there. |
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.
LGTM! Maybe this should go into the v1.7.0-integration branch though?
Remove excessive tag invalidation in examples which would otherwise interfere with the manual cache update
681adc1
to
ec5cfd0
Compare
ec5cfd0
to
8e14a98
Compare
I missed this when we originally built
fetchBaseQuery
, but ran into this yesterday at work. A lot of ruby/elixir/whatever APIs natively handle a bracket params format, so in order to support this, we'd need to allow for a custom paramsSerializer as proposed.