Docs: Modifying the response data examples (async/await) #7332
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
|
@alichry: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/ |
I added 2 examples for response manipulation, one that is synchronous and the other requires async/await. This is important because I could not find any documentation on how to manipulate the response in an asynchronous manner, which led me to editing the docs. See #7328
|
Thanks @alichry! I've merged and will give it a separate editorial pass shortly. |
StephenBarlow
pushed a commit
that referenced
this pull request
Nov 18, 2020
benjamn
added a commit
that referenced
this pull request
Nov 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I added two examples for response manipulation, one that is synchronous and the other requires async/await. This is crucial since I could not find any documentation on how to manipulate the response in an asynchronous manner, which led me to edit the docs.
See #7328