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
{{ message }}
This repository has been archived by the owner on Sep 26, 2022. It is now read-only.
Describe the bug
We have a request to an API that is returning a JSON string (not an object). We'd like to have this response parsed, but the option for fragmentsAllowed is needed in order to parse non-object JSON. This change should allow those JSON strings, numbers, booleans, etc. to be parsed in addition to objects.
To Reproduce
Steps to reproduce the behavior:
Make a request to an API that returns a JSON string (not an object).
Expected behavior
The JSON string should be parsed as a string.
Screenshots
NA
Desktop (please complete the following information):
OS: NA
Browser: NA
Version: NA
Smartphone (please complete the following information):
Device: NA
OS: NA
Browser: NA
Version: NA
Additional context
I have a fix created, and a PR open. Please merge #254 and publish a new version.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
We have a request to an API that is returning a JSON string (not an object). We'd like to have this response parsed, but the option for fragmentsAllowed is needed in order to parse non-object JSON. This change should allow those JSON strings, numbers, booleans, etc. to be parsed in addition to objects.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The JSON string should be parsed as a string.
Screenshots
NA
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
I have a fix created, and a PR open. Please merge #254 and publish a new version.
The text was updated successfully, but these errors were encountered: