fix: skip default validation for virtual fields#16015
Merged
DanRibbens merged 2 commits intoApr 1, 2026
Merged
Conversation
DanRibbens
approved these changes
Apr 1, 2026
Contributor
|
🚀 This is included in version v3.82.0 |
milamer
pushed a commit
to milamer/payload
that referenced
this pull request
Apr 20, 2026
### What? Virtual fields (`virtual: true` or `virtual: "path"`) no longer get a default type-based validator during field sanitization. They receive a noop validator instead. ### Why? Virtual fields are populated server-side (via hooks, built-in population, or plugins), so their value is `undefined` in form state. The default validator causes false validation errors in the admin UI that users cannot resolve. ### How? In `sanitize.ts`, when assigning a default validator, check if the field is virtual first. If so, assign `() => true` instead of the type-based validator. Explicit `validate` functions are still preserved. Fixes payloadcms#16012 Related payloadcms#16013 --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1213743778134481
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
3 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.
What?
Virtual fields (
virtual: trueorvirtual: "path") no longer get a default type-based validator during field sanitization. They receive a noop validator instead.Why?
Virtual fields are populated server-side (via hooks, built-in population, or plugins), so their value is
undefinedin form state. The default validator causes false validation errors in the admin UI that users cannot resolve.How?
In
sanitize.ts, when assigning a default validator, check if the field is virtual first. If so, assign() => trueinstead of the type-based validator. Explicitvalidatefunctions are still preserved.Fixes #16012
Related #16013