XMDEV-545: Fixes issue with depth limit plugin when dealing with fragments#52
Merged
devxiongmao merged 1 commit intorelease-fixesfrom Dec 24, 2025
Merged
Conversation
devxiongmao
added a commit
that referenced
this pull request
Dec 27, 2025
devxiongmao
added a commit
that referenced
this pull request
Dec 27, 2025
devxiongmao
added a commit
that referenced
this pull request
Dec 30, 2025
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.
Description
While testing, when using a fragment within a graphQL query, our depth limit plugin wouldn't calculate it correctly.
Approach Taken
Updated the plugin to handle the depth calculations correctly when using fragments in queries.
What Could Go Wrong?
This is a bug fix, so things technically already have gone wrong!
Remediation Strategy
NA