Breaking behavior in params serialization in 0.28.0 about axios HOT 6 OPEN

Might be a duplicate of #6262

from axios.

I think we can close this since #6263 which is to solve #6262 is merged and released in v0.28.1. See: 3021e0d

from axios.

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.
I've tried it on an client side (in a browser environment).

from axios.

@rchl I see, perhaps it is a different issue. v0.28.1 allows you to have a custom paramsSerializer.serialize options which you could use to achieve what you expected, otherwise I'd say this is just a standardization, i.e. stringified params vs params by key

from axios.

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).

from axios.

I can also confirm this is a breaking change in 0.28.0. Our axios get requests return a differently serialized request headers than in previous 0.27.2 version, resulting in 500 errors. Using a paramsSerializer.serialize options did not help in my case

from axios.