Context argument to GraphQL#execute() should be explicit in next breaking version
See original GitHub issueThe reference implementation now has an explicit context value that is separate from the root value. So in that implementation, GraphQL#execute()
now looks like:
export function execute(
schema: GraphQLSchema,
documentAST: Document,
rootValue?: mixed,
contextValue?: mixed,
variableValues?: ?{[key: string]: mixed},
operationName?: ?string
): Promise<ExecutionResult> {
We should probably follow in our next breaking version.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Resolvers - Apollo GraphQL Docs
A resolver is a function that's responsible for populating the data for a single field in your schema. It can populate that data...
Read more >Versioning fields in GraphQL - LogRocket Blog
Through versioning, breaking changes are added to a new version of the API, and since clients need to explicitly point to the new...
Read more >Execution - GraphQL
After being validated, a GraphQL query is executed by a GraphQL server which returns a result that mirrors the shape of the requested...
Read more >Resolver mapping template context reference - AWS AppSync
The $context variable is a map that holds all of the contextual information for your resolver invocation. It has the following structure: {...
Read more >DataFetchingEnvironment (graphql-java 15.0 API) - Javadoc.io
getLocalContext() which can be used to pass down extra information to fields ... Returns a context argument that is set up when the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is the proposal:
root
object: This will be presented asroot
toDataFetchers
root
will be thesource
object for the first queryThis is a breaking change.
the PR is merged and will be in the next release