Skip to content
This repository was archived by the owner on Mar 20, 2023. It is now read-only.

Allow custom handling of runtime query errors #696

Merged
merged 1 commit into from
Dec 8, 2020

Conversation

MatthiasKunnen
Copy link
Contributor

Since the earlier PRs were either not ready or not flexible enough I decided to take another shot at this issue.

Closes #427.

Replaces the following PRs:
Closes #471.
Closes #443.

@anthonydito
Copy link

I really like this change. Many "batteries included" hosting solutions such as AWS Elastic Beanstalk use the status code for monitoring health. Being able to distinguish between a user error and a network error in the status code would be awesome to make this more accurate.

Copy link
Member

@acao acao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you @MatthiasKunnen! implementation, tests and documentation all look good to me.

@acao acao merged commit 43ba606 into graphql:master Dec 8, 2020
@nclsndr
Copy link

nclsndr commented Dec 8, 2020

That's a great addition to the options! Thx you guys! When do you plan to release it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Queries returning only errors are forced to be a 500
4 participants