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.
Note: Changes dependent on #95
Resolves #93
This adds a new option which will determine whether or not to perform a "strict" JSON parse on the response's body. Strict in this sense essentially means
response.json().catch(() => null)
. This will be the default behavior, which matches how the behavior currently works inv4.1.9
. If the option is set tofalse
, then a failed parsing will default to returning the text of the body, which will be left to the client to handle appropriately.The use case that we're intending to solve for here is when a 3rd Party API doesn't escape a string response. E.g.,
The first response will fail
JSON.parse
, while the other will succeed.This implementation was inspired by Axios' implementation: