-
Notifications
You must be signed in to change notification settings - Fork 3k
feat: adds new experimental.allLocaleStatus flag #13509
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
Conversation
📦 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.
|
0f32cc8
to
903d235
Compare
We are no longer adding/changing by default. For users using any SQL DB adapter this could be considered breaking as taking a new version and deploying without migrating will cause errors. |
packages/payload/src/fields/baseFields/baseAllLocaleStatusField.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just consolidate and use localizeStatus, instead of adding a new property? I can't grasp why we would even support them individually.
Combining them into one property makes sense to me. Initially we were looking at |
This should be flattened with whatever we do for Also, we should not make queries in server components in the list view. That will be horribly slow. If you have 100 rows, you'll make 100 queries. Instead, we should evaluate lifting the |
Also if we do indeed want to render these things in the list view, we need to go through some design exploration here. At the very least, I don't want to render just the I think there may be a better option in general. If we can't come up with a clear design pattern, I think this column maybe should be disabled across the board and if someone wants to enable it they can, now that they have the data. |
Closing in favor of #13939 |
What?
Adds a new experimental flag,
allLocaleStatus
. When enabled, this adds an_allLocaleStatus
field to localized documents, providing access to the status of all locales from a single property. In list views, this field is rendered with a custom cell component that displays status indicators using colored pills.Why?
Payload currently has no out-of-the-box way to access document statuses across all locales. This feature has been requested by a client and approved as part of our upcoming localization enhancements.
How?
Adds a new field called

_allLocaleStatus
that stores the status of all locales.In list views, this field is paired with a custom cell component that provides a clear and quick view of each locale's status using colored indicator pills:
Feature request: #13440
NOTE
This flag will be updated in the near future to include a document view all-locale status indicator. That work is planned here, it is being rolled out in 2 parts because the document view indicator will be more comprehensive.