feat: add Table column visibility, order, and resize options - #2036
feat: add Table column visibility, order, and resize options#2036mentonin wants to merge 1 commit into
Conversation
Give users control over the table layout with content-independent widths so columns no longer jump when sorting or paginating. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: Luiz Georg <luiz.georg@profusion.mobi>
|
Could you add screenshots and/or videos, please? |
There was a problem hiding this comment.
Both BootsTable.tsx and BuildsTable.tsx have the details column, which is the only column that allows navigation to the details page. Clicking on the other cells only opens the right drawer.
I'm wondering if it's okay to allow the user to hide the only way they have to navigate.
There was a problem hiding this comment.
I believe it might be safer to allow only for between cells resize, but leave the outter table size untouched.
There was a problem hiding this comment.
I'm wondering if it's okay to allow the user to hide the only way they have to navigate.
The user can also navigate by opening the right drawer and clicking on "show more details" at the botton of the drawer
| }: ColumnResizeHandleProps): JSX.Element => { | ||
| const intl = useIntl(); | ||
|
|
||
| const onMouseDown = useCallback( |
There was a problem hiding this comment.
Does not seem to be working on phone touch screen.
| </LayoutTableHead> | ||
| ); | ||
| }); | ||
| // sorting / extraHeaderDeps: force header re-render when table UI state |
There was a problem hiding this comment.
do we really need memoization here?
We should have only a few columns, it might be safe to just recompute.
4 participants
Summary
useLayoutTableentry point drives Tree, Hardware, Issues, Builds, Boots, and hardware tree picker tables.maxWidth.Test plan
stay leftmost and visible
Related Issues