You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we accept a "columns" option (string[]) against each collection to influence table columns within the list page. This enhancement would add support for a more complete "columns definition", allowing consumers to optimise column behaviour depending on the expected values of field types.
Proposal
The TableView component already supports column configuration props, so this work would largely be surfacing that to consumers.
Omit defaultSort from config and always use the slug for initial load. Keep user sort preferences in local storage (and URL?), per collection.
Width definitions could yield poor experiences for users esp. on small devices. Ensure that TableView supports adequate scroll behaviour.
Spec
typeColumns<Key>={/** The default field and direction used to initially sort the data. */defaultSort: SortDescriptor<Key>;/** Defines which fields to render. */definition: Column<Key>[];};typeColumn<Key>={/** * The alignment of the column's contents relative to its allotted width. * @default 'start' */align?: 'start'|'center'|'end'|'left'|'right';/** Whether the column allows sorting. */allowsSorting?: boolean;/** The key of the column. */key: Key;/** The maximum width of the column. */maxWidth?: ColumnWidth;/** The minimum width of the column. */minWidth?: ColumnWidth;/** The width of the column. */width?: ColumnWidth;};typeColumnWidth=number| `${number}%`;typeSortDescriptor<Key>={/** The key of the column to sort by. */column: Key;/** The direction to sort by. */direction: 'ascending'|'descending';}
The text was updated successfully, but these errors were encountered:
Overview
Currently we accept a "columns" option (
string[]
) against each collection to influence table columns within the list page. This enhancement would add support for a more complete "columns definition", allowing consumers to optimise column behaviour depending on the expected values of field types.Proposal
The
TableView
component already supports column configuration props, so this work would largely be surfacing that to consumers.Usage
Considerations
defaultSort
behaviour:defaultSort
from config and always use the slug for initial load. Keep user sort preferences in local storage (and URL?), per collection.TableView
supports adequate scroll behaviour.Spec
The text was updated successfully, but these errors were encountered: