Fix union & conditional directive (@skip and @include) not generating field types correctly - #10918
Merged
Conversation
🦋 Changeset detectedLatest commit: 54a4bfd The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
💻 Website PreviewThe latest changes are available as preview in: https://pr-10918.graphql-code-generator.pages.dev |
eddeee888
marked this pull request as ready for review
August 11, 2026 13:36
eddeee888
marked this pull request as draft
August 11, 2026 14:13
eddeee888
marked this pull request as ready for review
August 12, 2026 12:20
This was referenced Aug 12, 2026
negezor
pushed a commit
to senkuro-dev/graphql-code-generator
that referenced
this pull request
Aug 14, 2026
…ting field types correctly (dotansimha#10918) * Fix union and conditional directive types * Add changeset * Add test to ensure no double/tripple fragmentRefs/fragmentName * Fix double added fragment names
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.
Description
When updating Codegen packages in Console, we saw that there are issues with generated types:
Given a document like this:
In
@graphql-codegen/client-preset@5.1.1:This is incorrect because fields in inline fragments should be optional
In
@graphql-codegen/client-preset@6.1.2:This is definitely incorrect because fields in inline fragments should be optional, and they are all gone here
This PR fixes it by correctly applying optionality to fields of a fragment marked with conditional directives when used in a union:
Note: this might be an issue for interfaces as well, but let's solve this one first.
Type of change
How Has This Been Tested?