You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A workaround does exist for this -- you can pass parseJsonStrictly: false as a configuration option. The response will still be attempted to be parsed as json, but when it fails the response body should be returned as text.
It's possible that for this case we shouldn't try to transform the body at all (even via .text()) so that the client can do whatever they want with it
The text was updated successfully, but these errors were encountered:
We should not try to transform responses that we know are not JSON. E.g.,
A workaround does exist for this -- you can pass
parseJsonStrictly: false
as a configuration option. The response will still be attempted to be parsed as json, but when it fails the response body should be returned as text.It's possible that for this case we shouldn't try to transform the body at all (even via
.text()
) so that the client can do whatever they want with itThe text was updated successfully, but these errors were encountered: