chore(tests): add test for directive extensions without flag enabled#4738
Merged
Conversation
The branch in parseTypeSystemExtension where the 'directive' keyword is encountered but the parsing option was not enabled was apparently NOT covered prior to addition to this test, falsely reported by our imperfect tooling as covered. At least it appears. This was uncovered by formatting changed of other pending work; the addition of this test should narrow the diff of any other changes.
yaacovCR
added
the
PR: polish 💅
|
@yaacovCR is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
yaacovCR
added a commit
that referenced
this pull request
May 14, 2026
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.
The branch in parseTypeSystemExtension where the 'directive' keyword is encountered but the parsing option was not enabled was apparently NOT covered prior to addition to this test, falsely reported by our imperfect tooling as covered.
At least it appears. This was uncovered by formatting changed of other pending work; the addition of this test should narrow the diff of any other changes.