Skip to content

ExecutionGraphQlService should handle early GraphQLExceptions #1118

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.

Sign up for GitHub

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

Jump to bottom
Closed
bclozel opened this issue Feb 4, 2025 · 0 comments
Closed

ExecutionGraphQlService should handle early GraphQLExceptions #1118

bclozel opened this issue Feb 4, 2025 · 0 comments
Assignees
@bclozel
Labels
in: core Issues related to config and core support type: bug A general bug
Milestone
1.3.4

Comments

@bclozel
Copy link
Member

bclozel commented Feb 4, 2025

In some cases, GraphQL requests are rejected early because of GraphQL document validation errors.
The DefaultExecutionGraphQlService should handle those consistently and use the relevant information in the "errors" response map if those are also GraphQLError instances.
@bclozel bclozel added in: core Issues related to config and core support type: bug A general bug labels Feb 4, 2025
@bclozel bclozel added this to the 1.3.4 milestone Feb 4, 2025
@bclozel bclozel self-assigned this Feb 4, 2025
@bclozel bclozel closed this as completed in af74edb Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bclozel bclozel

Labels
in: core Issues related to config and core support type: bug A general bug
Projects
None yet
Milestone
1.3.4
Development

No branches or pull requests
1 participant
@bclozel