f5a955d906
Fixes #10234. Some fields, such as focal point fields for upload enabled collections, were rendering in the condition selector despite being hidden from the column selector. This was because the logic for the column selector was filtering fields without labels, but the same was not being done for the filter conditions. This, however, is not a good way to filter these fields as it requires this specific logic to be written in multiple places. Instead, they need to explicitly check for `hidden` and `disabled` in addition to `disableListFilter` and `disableListColumn`. The actual filtering logic has been improved across the two instances as well, removing multiple duplicative loops. This change has also exposed a underlying issue with the way columns were handled within the table columns provider. When row selections were enabled, the selector columns were present in column state. This caused problems when interacting with column indices, such as when reordering columns. Instead of needing to manually filter these out every time we need to work with column state, they no longer appear there in the first place. Instead, we inject the row selectors directly into the table itself, completely isolating these row selectors from the column state.
16 lines
449 B
TypeScript
16 lines
449 B
TypeScript
import type { RequiredDataFromCollection } from 'payload/types'
|
|
|
|
import type { TextField } from '../../payload-types.js'
|
|
|
|
export const defaultText = 'default-text'
|
|
export const textFieldsSlug = 'text-fields'
|
|
|
|
export const textDoc: RequiredDataFromCollection<TextField> = {
|
|
text: 'Seeded text document',
|
|
localizedText: 'Localized text',
|
|
}
|
|
|
|
export const anotherTextDoc: RequiredDataFromCollection<TextField> = {
|
|
text: 'Another text document',
|
|
}
|