feat(Feat/error handling): Handled GraphQL errors according to the graphql error guide #41
Conversation
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
…-PostgresQL into feat/error-handling
…-PostgresQL into feat/error-handling
…d HTTP status plugin
…ion and update error handling across strategies and services
…Acceptable responses
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR implements error handling for GraphQL responses in compliance with the official GraphQL over HTTP specifications.
Specifically, the changes follow the recommendations and status code guidelines provided in the following resources:
Key updates include:
Proper usage of HTTP status codes (200, 400, 500, etc.) according to the type of GraphQL error.
Differentiation between transport-level errors and GraphQL execution errors.
Ensuring consistent response shape with appropriate errors and data fields.
These changes ensure our GraphQL API adheres more closely to industry standards and improves client-side error handling predictability.