Conversation
**This is a breaking change. Existing uses of execute() outside of async functions which assume a promise response will need to wrap in Promise.resolve()** This allows `execute()` to return synchronously if all fields it encounters have synchronous resolvers. Notable this is the case for client-side introspection, querying from a cache, and other useful cases. Note that the top level `graphql()` function remains a Promise to minimize the breaking change, and that `validate()` has always been synchronous.
leebyron
force-pushed
the
sync-execute
branch
from
87e12b4 to
5996bce
Compare
Member
@leebyron Looks great 👍 and solves all the cases I encounter. One less promise to worry about 😄 |
Merged
martijnwalraven
added a commit
to apollographql/apollo-server
that referenced
this pull request
Dec 18, 2017
This fixes executing a query if all fields it encounters have synchronous resolvers, for which behavior changed in 0.12.x due to graphql/graphql-js#1115. Closes #718, closes #720
This was referenced Apr 10, 2018
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
3 participants
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.
This is a breaking change. Existing uses of execute() outside of async functions which assume a promise response will need to wrap in Promise.resolve()
This allows
execute()to return synchronously if all fields it encounters have synchronous resolvers. Notable this is the case for client-side introspection, querying from a cache, and other useful cases.Also introduces
graphqlSync()as a top level function which asserts sync behavior and includes validation.Note that the top level
graphql()function remains a Promise to minimize the breaking change, and thatvalidate()has always been synchronous.