Set tranformResponse property of axios req. config to an identity function #358
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
axios
changed the way it treats properties of the request config in0.19.0
. Previously we were settingtrasnformResponse
toundefined
. This would indicateaxios
to not transform (JSON.parse()
) the response body. In0.19.0
, they are setting the default response transformer if transformResponse is set toundefined
. This breaks our pasrsing logic where we are doingJSON.parse()
onoperationResponse.bodyAsText
. Moreover, we are exposing thebodyAsText
property in the generated clients.Not populating this property or setting the value of this property to a parsed JSON would be a breaking change for our users.
Hence we are setting the
transformResponse
property in the request config to an indentity function that returns the response body as-is.