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
Breaking behavior in params serialization in 0.28.0 #6274
Comments
Might be a duplicate of #6262 |
No, it's not fixed. Just tested with 0.28.1. Feel free to test yourself by making a request like in the initial comment and checking brower network inspector for what is being sent. |
@rchl I see, perhaps it is a different issue. v0.28.1 allows you to have a custom |
Would make sense to keep the old behavior to prevent breaking changes unless there is a good reason to deviate. And if there is then it should be clearly marked as a breaking change and there should be good reason for it (standards compliance or similar). |
@butchtm I've tried to replicate the serialization behavior that was implemented in prior versions to 0.28 below
|
Describe the bug
In 0.28.0 there is a breaking change to params serialization that wasn't mentioned as such in the changelog.
Probably related to c05ad48 and 807918b
If this is an expected change then it should have been noted in the changelog as breaking. Otherwise it should be fixed.
@DigitalBrainJS
To Reproduce
Send a get request with one of the
params
values being an object with key/value properties.Code snippet
Expected behavior
Previously the
p
param would be serialized as such:&p={"a":"z"}
With 0.28.0:
&p[a]=z
Axios Version
0.28.0
Adapter Version
No response
Browser
No response
Browser Version
No response
Node.js Version
No response
OS
No response
Additional Library Versions
No response
Additional context/Screenshots
No response
The text was updated successfully, but these errors were encountered: