Support lazy type references for Union members #1599
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
This change allows union member types to be defined using string references or functions, similar to how field, input field, or argument types can be declared. The actual type classes will be resolved only during schema construction.
ahter
approved these changes
Feb 12, 2026
ahter
left a comment
ahter
left a comment
There was a problem hiding this comment.
Thanks for the improvements @TomasBayer. This looks good to me.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fields, input fields, and arguments already support lazy type references via strings and lambdas to avoid circular imports. This PR adds the same support to member types of Unions. See this issue for details: #1600
Example:
This change is non-breaking.