Repository navigation
docs(learn): use async/await in JS examples - #2555
Open
MisbahAnsar wants to merge 1 commit into
Open
MisbahAnsar wants to merge 1 commit into
MisbahAnsar wants to merge 1 commit into
Conversation
|
@MisbahAnsar is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
|
MisbahAnsar
marked this pull request as ready for review
October 25, 2026 14:23
This branch has not been deployed
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 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.
Closes #1821
Switches the promise-chain resolver examples in the Learn pages to async/await, and adjusts the surrounding text in the Asynchronous resolvers section so it still explains where the Promise comes from.
Files changed:
src/pages/learn/execution.mdx:resolveHuman(both copies) andresolveHumanStarshipssrc/pages/learn/mutations.mdx:createReviewThe
/graphql-jspages are untouched, as discussed in the issue.