Skip undefined fragments in depth_limit_validator#1603
Open
Hassad674 wants to merge 1 commit intographql-python:masterfrom
Open
Skip undefined fragments in depth_limit_validator#1603Hassad674 wants to merge 1 commit intographql-python:masterfrom
Hassad674 wants to merge 1 commit intographql-python:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #1538
When a query references an undefined fragment, depth_limit_validator raises a KeyError because it tries to look up the fragment name in the fragments dict. Other validators already catch undefined fragments and report proper errors, so depth_limit_validator should just skip them.
Changed the dict access to use .get() and return depth 0 for undefined fragments. Added a test verifying that undefined fragments don't crash the validator.