We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the https://axios-http.com/docs/req_config docs, the paramsSerializer usage says that it accepts a function in charge of serializing params,
params
however on the newest version of axios (I'm using 1.3.4) this will produce a TS error
1.3.4
That's because now paramsSerializer uses an object that accepts a encode and serialize configuration
paramsSerializer
encode
serialize
Update that portion of the paramsSerializer documentation for the new approach with {serialize,encode}
No response
The text was updated successfully, but these errors were encountered:
Giving you a text file can someone check will this change in documentation is valid, If yes then I will create a PR. paramsSerializer.txt
Sorry, something went wrong.
Hi, I've created a PR to resolve this in all of the languages. axios/axios-docs#177
@jasonsaayman would you mind reviewing and approving the pr?
Since v1.3.5 (#5633) paramsSerializer accepts both types (object & function).
No branches or pull requests
Section/Content To Improve
In the https://axios-http.com/docs/req_config docs, the paramsSerializer usage says that it accepts a function in charge of serializing
params
,however on the newest version of axios (I'm using
1.3.4
) this will produce a TS errorThat's because now
paramsSerializer
uses an object that accepts aencode
andserialize
configurationSuggested Improvement
Update that portion of the
paramsSerializer
documentation for the new approach with {serialize,encode}Relevant File(s)
No response
The text was updated successfully, but these errors were encountered: