Overwrite JSON.stringify instead of JSON.parse for newer GraphiQL
#29
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
nshelly
changed the title
nshelly
force-pushed
the
nick/use-stringify
branch
from
0533ba2 to
da51f6e
Compare
nshelly
changed the title
JSON.stringify instead of JSON.parse for newer GraphiQL
nshelly
force-pushed
the
nick/use-stringify
branch
from
da51f6e to
d3bad7b
Compare
nshelly
force-pushed
the
nick/use-stringify
branch
from
d3bad7b to
d85ded2
Compare
|
This is very exciting, @nshelly! Does anyone know how likely it is to be merged? |
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.
GraphiQL has changed its core fetch logic, and so we need to overwrite JSON.stringify instead in order to update the sidebar with the most recent query.