fix: add body stringification for application/json content-type #77
+18
−1
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.
Overview
When
Content-Type: application/jsonis explicitly specified, automatically applyJSON.stringifyto the objectbodyto resolve the issue where[object Object]is sent.For non-JSON Content-Types, existing behavior is preserved.
Background / Issue
issue: #76
In the current implementation, even when
application/jsonis specified, an object body is not serialized and is instead sent as[object Object].Key Changes
When the header includes
"content-type": "application/json",JSON.stringifyis applied.Expected Behavior
For requests that specify
application/json, payloads such as{ "foo": "bar" }are correctly sent as a JSON string.