Allow the ability to set GraphQL Playground settings #508
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
|
Thank you so much! 🙂 |
|
I have linted the code as that was causing the workflow failures. Hopefully, we can get this merged! |
|
Thank you, I forgot to merge it. 🙂 |
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.
In the GraphQL Playground UI, you can configure settings. This PR allows a default set of settings to be defined server-side similar to the default headers option that already exists in this package.
An example use case of this feature is setting the
request.credentialssetting toincludeorsame-siteinstead of its default valueomit. This allows cookies to be manipulated in the GraphQL request.