-
Notifications
You must be signed in to change notification settings - Fork 2.9k
fix: admin.hidden not respected for RSCs, render-field server function not respecting field-overrides client-side #13869
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+114
−63
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
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
DanRibbens
approved these changes
Sep 22, 2025
PatrikKozak
added a commit
that referenced
this pull request
Sep 24, 2025
…n field changes (#13917) ### What? - Fixes collectionSlug field not being populated, breaking export downloads - Works around recent UI changes that prevent custom components from rendering for `admin.hidden` fields - Removes `admin.hidden: true` - as the component already ensures a hidden state by returning `null` ### Why? - This merged [PR](#13869) changed how `admin.hidden` fields are rendered, causing them to bypass custom field components entirely. The `collectionSlug` field relied on a custom `CollectionField` component to set its value from the ImportExportProvider context. ### How? - Removes `admin.hidden: true` - Field remains visually hidden with `null` return but custom component logic now executes properly
🚀 This is included in version v3.57.0 |
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.
This PR fixes 2 issues:
fieldConfig.admin.hidden
property had no effect for react server components, because the RSC was returned before we're checking foradmin.hidden
in RenderFieldsrender-field
server function did not propagate fieldConfig overrides to the clientProps. This means overridingadmin.Label
had no effectAdds e2e tests for both issues