add more control through configuration @ ParseJSONResultsPlugin.
#1170
Conversation
This file contains 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
igalklebanov
added
built-in plugin
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
igalklebanov
changed the title
ParseJSONResultsPlugin.
igalklebanov
force-pushed
the
parse-json-omit-keys
branch
from
d3cbb64
to
3a1825e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey 👋
This PR revisits
ParseJSONResultsPluginand attempts to provide more fine-grained control to consumers.skipKeysallows you to specify columns to not parse in a result object.reviverallows passing a custom reviver function to theJSON.parseinvocations. This can allow you to instantiate native Dates, or omit keys.__proto__keys are always deleted to deny prototype pollution.isJSONallows overriding what is or what isn't considered a JSON string before attempting toJSON.parseit.