fix(graphql): virtual fields should be nullable in GraphQL schema (#16112)#16193
Open
deepshekhardas wants to merge 3 commits intopayloadcms:mainfrom
Open
fix(graphql): virtual fields should be nullable in GraphQL schema (#16112)#16193deepshekhardas wants to merge 3 commits intopayloadcms:mainfrom
deepshekhardas wants to merge 3 commits intopayloadcms:mainfrom
Conversation
added 3 commits
April 7, 2026 07:18
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 #16112 - Virtual field marked as required in GraphQL schema
Problem: Virtual fields that are marked as
equired: true are still required in GraphQL mutation inputs, but they shouldn't be since they're computed by hooks, not stored.
Solution: Added a check for virtual fields in withNullableType.ts to ensure virtual fields are always nullable in GraphQL inputs, regardless of their
equired setting.