Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Improve fetchBaseQuery content json verification
See original GitHub issueCurrently in the docs regarding the body it says:
// fetchBaseQuery automatically adds 'content-type: application/json' to the Headers and calls JSON.stringify(patch)
However it doesn’t state that it only “stringifies” if the content-type is strictly application/json, I use application/vnd.api+json for example and it was not very easy to figure what was wrong.
My proposal is to check if the content-type contains the json extension, so it will cover all json cases, if no one sees any issues with this proposal I’d be glad to push a PR for it, otherwise we could at least update the docs to avoid any confusion.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ShaunDychko @phryneas I ran into this recently with a custom fetch wrapper based around
fetchBaseQuery, and added the solution as proposed here: https://github.com/reduxjs/redux-toolkit/pull/2331. I’d recommend we go with this approach as it’s a simple opt-in mechanism for JSON API users (like me, sometimes! 😂)This is handled in #2331 which I just merged into the 1.9 branch.