This repository was archived by the owner on Sep 26, 2022. It is now read-only.
Add fragmentsAllowed option to JSONSerialization.jsonObject #254
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
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
fragmentsAllowedis 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.Note: The
npm run buildadded to thepreparescript inpackage.jsonallows us to install the capacitor plugin from a github repository, which we're doing in the meantime. This can be removed if desired, as it's not needed when the plugin is published in an npm registry.