This repository was archived by the owner on Mar 20, 2023. It is now read-only.
Allow custom handling of runtime query errors#780
Open
MatthiasKunnen wants to merge 1 commit intographql:mainfrom
Open
Allow custom handling of runtime query errors#780MatthiasKunnen wants to merge 1 commit intographql:mainfrom
MatthiasKunnen wants to merge 1 commit intographql:mainfrom
Conversation
|
|
|
I am strongly in favor of this, I definitely need to be able to customize the error code. |
Contributor
Author
|
Also closes #808 |
|
What can we do to fix this? and have it in production ? Is there anything we can do to allow GraphQL specs 200 status code for error returning? This is fucking all clients , especially apollo client you cannot read body from the response ! |
Member
|
This package is deprecated. You can read more here #817 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Closes #427.
Closes #808.
Why
When runtime errors occur, tracing and logging is paramount to discern between incorrect user input or a faulty backend/frontend. To this end, tracing info can be added to response headers in order for proxies/frontends to log this error and update metrics.
Without this PR, achieving this goal is only possible using dirty solutions such as hijackresponse since
express-graphqlfinalizes the response which prevents later middleware from enhancing it.