Add parse_and_validate() for validating a query without executing it - #1392
Open
ChrisJr404 wants to merge 1 commit into
Open
Add parse_and_validate() for validating a query without executing it#1392ChrisJr404 wants to merge 1 commit into
ChrisJr404 wants to merge 1 commit into
Conversation
ChrisJr404
force-pushed
the
parse-and-validate
branch
from
August 25, 2026 16:14
2d01be7 to
b267309
Compare
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 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.
Resolves #726.
Right now there's no way to tell whether a request is a query, mutation or subscription without trying to execute it, which is why
juniper_graphql_wscurrently has to run bothexecuteandresolve_into_streamand see what works. This adds aparse_and_validate()that runs the same parsing and validation asexecute/execute_syncbut stops before resolving anything, and returns theOperationTypeof the operation that would run, so a caller can route to the right executor themselves.It's purely additive, the existing execute functions are untouched. Added tests covering the three operation types plus the parse, validation and multiple-operations error paths, and a CHANGELOG entry.