We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Our GraphQL errors have not customization while returning to the request. They're like NestJS returns it.
We should improve the format of GraphQL errors. We could follow this suggestion: nestjs/graphql#1053 (comment)
To move fast.
We can lose time debugging because our error is not formatted accordingly.
The text was updated successfully, but these errors were encountered:
Closed since we're now using ApolloErrors.
Sorry, something went wrong.
No branches or pull requests
💩 How it is currently developed
Our GraphQL errors have not customization while returning to the request. They're like NestJS returns it.
🌟 What is the optimal solution
We should improve the format of GraphQL errors. We could follow this suggestion: nestjs/graphql#1053 (comment)
😓 Why we did that way
To move fast.
💣 What are the possible impacts
We can lose time debugging because our error is not formatted accordingly.
The text was updated successfully, but these errors were encountered: