Skip to content

Refactor executeOperation #883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 26, 2017
Merged

Refactor executeOperation #883

merged 1 commit into from
May 26, 2017

Conversation

leebyron
Copy link
Contributor

This ensures failures related to buildExecutionContext() yield a GraphQL Result with errors rather than a thrown error from execute(), and handles top level error catching and nulling within executeOperation() instead of execute() for better alignment to spec text.

This helps align to the idea that internal errors throw and GraphQL user errors are returned within the GraphQL Result.

This ensures failures related to buildExecutionContext() yield a GraphQL Result with errors rather than a thrown error from execute(), and handles top level error catching and nulling within executeOperation() instead of execute() for better alignment to spec text.

This helps align to the idea that internal errors throw and GraphQL user errors are returned within the GraphQL Result.
@leebyron leebyron force-pushed the executeOperation branch from 820accf to 62619df Compare May 26, 2017 05:04
@leebyron leebyron merged commit 508aa3a into master May 26, 2017
@leebyron leebyron deleted the executeOperation branch May 26, 2017 05:12
leebyron added a commit that referenced this pull request May 26, 2017
leebyron added a commit that referenced this pull request May 26, 2017
leebyron added a commit that referenced this pull request May 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants