Table
@rockshin/tao-uiDisplays structured row and column data with selection, sorting, filtering, and pagination hooks.
When to use
Use Table for dense, comparable records that benefit from aligned columns.
Recommended
- Keep columns focused on the task.
- Use stable row keys.
- Control sorting and pagination when data is remote.
- Gate secondary columns with column.responsive (e.g. ['lg']) instead of hand-rolled media queries.
Avoid
- Do not use Table for card-like content where comparison is not important.
Examples
Basic usage
Name | Role |
|---|---|
| Ada Lovelace | Engineer |
| Grace Hopper | Scientist |
Variants
Name | Role |
|---|---|
| Ada | Engineer |
| Grace | Scientist |
Name | Role |
|---|---|
| Ada | Engineer |
| Grace | Scientist |
Name | Role |
|---|---|
| Ada | Engineer |
| Grace | Scientist |
Name | Role |
|---|---|
| Ada | Engineer |
| Grace | Scientist |
Sizes and borders
Name | Status |
|---|---|
| Build | Passing |
Name | Status |
|---|---|
| Build | Passing |
Name | Status |
|---|---|
| Build | Passing |
Loading, empty, and pagination
Name |
|---|
| No Data |
Name |
|---|
| No matching users. |
Name |
|---|
| User 1 |
| User 2 |
| User 3 |
| User 4 |
| User 5 |
Fixed header, expandable rows, and summary
scroll.y caps the body height and pins the header; expandable renders details under a row (the expand column sits before the selection column); summary returns Table.Summary.Row / Table.Summary.Cell footer rows — Cell.index counts from the expand/selection columns to sync fixed columns, and `` pins the footer while the body scrolls.
Name | Team | Score | |
|---|---|---|---|
| User 1 | Design | 60 | |
| User 2 | Engineering | 67 | |
| User 3 | Sales | 74 | |
| User 4 | Design | 81 | |
| User 5 | Engineering | 88 | |
| User 6 | Sales | 95 | |
| User 7 | Design | 62 | |
| User 8 | Engineering | 69 | |
| User 9 | Sales | 76 | |
| User 10 | Design | 83 | |
| User 11 | Engineering | 90 | |
| User 12 | Sales | 97 | |
| User 13 | Design | 64 | |
| User 14 | Engineering | 71 | |
| User 15 | Sales | 78 | |
| User 16 | Design | 85 | |
| User 17 | Engineering | 92 | |
| User 18 | Sales | 99 | |
| User 19 | Design | 66 | |
| User 20 | Engineering | 73 | |
| User 21 | Sales | 80 | |
| User 22 | Design | 87 | |
| User 23 | Engineering | 94 | |
| User 24 | Sales | 61 | |
| User 25 | Design | 68 | |
| User 26 | Engineering | 75 | |
| User 27 | Sales | 82 | |
| User 28 | Design | 89 | |
| User 29 | Engineering | 96 | |
| User 30 | Sales | 63 | |
| Total | 2365 | ||
Sorting
Configure sorting on columns and click a header to switch the sort direction.
Role | ||
|---|---|---|
| Alice | 22 | admin |
| Eve | 22 | viewer |
| Alice | 22 | editor |
| Bob | 23 | editor |
| Frank | 23 | admin |
| Bob | 23 | viewer |
| Charlie | 24 | viewer |
| Grace | 24 | editor |
| Charlie | 24 | admin |
| Diana | 25 | admin |
Column filtering
Provide filter choices and a predicate, then select items in the column menu.
Name | Age | Role | Department |
|---|---|---|---|
| Alice | 22 | admin | Engineering |
| Bob | 23 | editor | Design |
| Charlie | 24 | viewer | Marketing |
| Diana | 25 | admin | Sales |
| Eve | 26 | editor | Engineering |
| Frank | 27 | viewer | Design |
| Grace | 28 | admin | Marketing |
| Hank | 29 | editor | Sales |
| Alice | 30 | viewer | Engineering |
| Bob | 31 | admin | Design |
Controlled row selection
Use a stable record ID for rowKey, such as a database ID. Keep selected keys in rowSelection.selectedRowKeys and update them from rowSelection.onChange.
Return { disabled: true } from rowSelection.getCheckboxProps(record) for rows that cannot be selected. The header checkbox applies to eligible rows on the current page and preserves selection on other pages. Since 0.0.49, Table also uses the current disabled state when rows change and the callback stays the same.
Selected: none
ID | Name | Age | Email | Role | |
|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | |
| 2 | Bob | 23 | user2@example.com | editor | |
| 3 | Charlie | 24 | user3@example.com | viewer | |
| 4 | Diana | 25 | user4@example.com | admin | |
| 5 | Eve | 26 | user5@example.com | editor | |
| 6 | Frank | 27 | user6@example.com | viewer | |
| 7 | Grace | 28 | user7@example.com | admin | |
| 8 | Hank | 29 | user8@example.com | editor | |
| 9 | Alice | 30 | user9@example.com | viewer | |
| 10 | Bob | 31 | user10@example.com | admin |
Horizontal scrolling and fixed columns
Combine column widths with scroll.x; fixed columns preserve context while scrolling.
ID | Name | Age | Email | Role | Department | Actions |
|---|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | Engineering | |
| 2 | Bob | 23 | user2@example.com | editor | Design | |
| 3 | Charlie | 24 | user3@example.com | viewer | Marketing | |
| 4 | Diana | 25 | user4@example.com | admin | Sales | |
| 5 | Eve | 26 | user5@example.com | editor | Engineering | |
| 6 | Frank | 27 | user6@example.com | viewer | Design | |
| 7 | Grace | 28 | user7@example.com | admin | Marketing | |
| 8 | Hank | 29 | user8@example.com | editor | Sales |
Fixed header
scroll.y creates a bounded scrolling body while retaining the table header.
ID | Name | Age | Email | Role | Department |
|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | Engineering |
| 2 | Bob | 23 | user2@example.com | editor | Design |
| 3 | Charlie | 24 | user3@example.com | viewer | Marketing |
| 4 | Diana | 25 | user4@example.com | admin | Sales |
| 5 | Eve | 26 | user5@example.com | editor | Engineering |
| 6 | Frank | 27 | user6@example.com | viewer | Design |
| 7 | Grace | 28 | user7@example.com | admin | Marketing |
| 8 | Hank | 29 | user8@example.com | editor | Sales |
| 9 | Alice | 30 | user9@example.com | viewer | Engineering |
| 10 | Bob | 31 | user10@example.com | admin | Design |
| 11 | Charlie | 32 | user11@example.com | editor | Marketing |
| 12 | Diana | 33 | user12@example.com | viewer | Sales |
| 13 | Eve | 34 | user13@example.com | admin | Engineering |
| 14 | Frank | 35 | user14@example.com | editor | Design |
| 15 | Grace | 36 | user15@example.com | viewer | Marketing |
| 16 | Hank | 37 | user16@example.com | admin | Sales |
| 17 | Alice | 38 | user17@example.com | editor | Engineering |
| 18 | Bob | 39 | user18@example.com | viewer | Design |
| 19 | Charlie | 40 | user19@example.com | admin | Marketing |
| 20 | Diana | 41 | user20@example.com | editor | Sales |
| 21 | Eve | 22 | user21@example.com | viewer | Engineering |
| 22 | Frank | 23 | user22@example.com | admin | Design |
| 23 | Grace | 24 | user23@example.com | editor | Marketing |
| 24 | Hank | 25 | user24@example.com | viewer | Sales |
| 25 | Alice | 26 | user25@example.com | admin | Engineering |
| 26 | Bob | 27 | user26@example.com | editor | Design |
| 27 | Charlie | 28 | user27@example.com | viewer | Marketing |
| 28 | Diana | 29 | user28@example.com | admin | Sales |
| 29 | Eve | 30 | user29@example.com | editor | Engineering |
| 30 | Frank | 31 | user30@example.com | viewer | Design |
| 31 | Grace | 32 | user31@example.com | admin | Marketing |
| 32 | Hank | 33 | user32@example.com | editor | Sales |
| 33 | Alice | 34 | user33@example.com | viewer | Engineering |
| 34 | Bob | 35 | user34@example.com | admin | Design |
| 35 | Charlie | 36 | user35@example.com | editor | Marketing |
| 36 | Diana | 37 | user36@example.com | viewer | Sales |
| 37 | Eve | 38 | user37@example.com | admin | Engineering |
| 38 | Frank | 39 | user38@example.com | editor | Design |
| 39 | Grace | 40 | user39@example.com | viewer | Marketing |
| 40 | Hank | 41 | user40@example.com | admin | Sales |
| 41 | Alice | 22 | user41@example.com | editor | Engineering |
| 42 | Bob | 23 | user42@example.com | viewer | Design |
| 43 | Charlie | 24 | user43@example.com | admin | Marketing |
| 44 | Diana | 25 | user44@example.com | editor | Sales |
| 45 | Eve | 26 | user45@example.com | viewer | Engineering |
| 46 | Frank | 27 | user46@example.com | admin | Design |
ID | Name | Age | Email | Role | Department |
|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | Engineering |
| 2 | Bob | 23 | user2@example.com | editor | Design |
| 3 | Charlie | 24 | user3@example.com | viewer | Marketing |
| 4 | Diana | 25 | user4@example.com | admin | Sales |
| 5 | Eve | 26 | user5@example.com | editor | Engineering |
| 6 | Frank | 27 | user6@example.com | viewer | Design |
| 7 | Grace | 28 | user7@example.com | admin | Marketing |
| 8 | Hank | 29 | user8@example.com | editor | Sales |
| 9 | Alice | 30 | user9@example.com | viewer | Engineering |
| 10 | Bob | 31 | user10@example.com | admin | Design |
| 11 | Charlie | 32 | user11@example.com | editor | Marketing |
| 12 | Diana | 33 | user12@example.com | viewer | Sales |
| 13 | Eve | 34 | user13@example.com | admin | Engineering |
| 14 | Frank | 35 | user14@example.com | editor | Design |
| 15 | Grace | 36 | user15@example.com | viewer | Marketing |
| 16 | Hank | 37 | user16@example.com | admin | Sales |
| 17 | Alice | 38 | user17@example.com | editor | Engineering |
| 18 | Bob | 39 | user18@example.com | viewer | Design |
| 19 | Charlie | 40 | user19@example.com | admin | Marketing |
| 20 | Diana | 41 | user20@example.com | editor | Sales |
| 21 | Eve | 22 | user21@example.com | viewer | Engineering |
| 22 | Frank | 23 | user22@example.com | admin | Design |
| 23 | Grace | 24 | user23@example.com | editor | Marketing |
| 24 | Hank | 25 | user24@example.com | viewer | Sales |
| 25 | Alice | 26 | user25@example.com | admin | Engineering |
| 26 | Bob | 27 | user26@example.com | editor | Design |
| 27 | Charlie | 28 | user27@example.com | viewer | Marketing |
| 28 | Diana | 29 | user28@example.com | admin | Sales |
| 29 | Eve | 30 | user29@example.com | editor | Engineering |
| 30 | Frank | 31 | user30@example.com | viewer | Design |
| 31 | Grace | 32 | user31@example.com | admin | Marketing |
| 32 | Hank | 33 | user32@example.com | editor | Sales |
| 33 | Alice | 34 | user33@example.com | viewer | Engineering |
| 34 | Bob | 35 | user34@example.com | admin | Design |
| 35 | Charlie | 36 | user35@example.com | editor | Marketing |
| 36 | Diana | 37 | user36@example.com | viewer | Sales |
| 37 | Eve | 38 | user37@example.com | admin | Engineering |
| 38 | Frank | 39 | user38@example.com | editor | Design |
| 39 | Grace | 40 | user39@example.com | viewer | Marketing |
| 40 | Hank | 41 | user40@example.com | admin | Sales |
| 41 | Alice | 22 | user41@example.com | editor | Engineering |
| 42 | Bob | 23 | user42@example.com | viewer | Design |
| 43 | Charlie | 24 | user43@example.com | admin | Marketing |
| 44 | Diana | 25 | user44@example.com | editor | Sales |
| 45 | Eve | 26 | user45@example.com | viewer | Engineering |
| 46 | Frank | 27 | user46@example.com | admin | Design |
ID | Name | Age | Email | Role | Department |
|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | Engineering |
| 2 | Bob | 23 | user2@example.com | editor | Design |
| 3 | Charlie | 24 | user3@example.com | viewer | Marketing |
| 4 | Diana | 25 | user4@example.com | admin | Sales |
| 5 | Eve | 26 | user5@example.com | editor | Engineering |
| 6 | Frank | 27 | user6@example.com | viewer | Design |
| 7 | Grace | 28 | user7@example.com | admin | Marketing |
| 8 | Hank | 29 | user8@example.com | editor | Sales |
| 9 | Alice | 30 | user9@example.com | viewer | Engineering |
| 10 | Bob | 31 | user10@example.com | admin | Design |
| 11 | Charlie | 32 | user11@example.com | editor | Marketing |
| 12 | Diana | 33 | user12@example.com | viewer | Sales |
| 13 | Eve | 34 | user13@example.com | admin | Engineering |
| 14 | Frank | 35 | user14@example.com | editor | Design |
| 15 | Grace | 36 | user15@example.com | viewer | Marketing |
| 16 | Hank | 37 | user16@example.com | admin | Sales |
| 17 | Alice | 38 | user17@example.com | editor | Engineering |
| 18 | Bob | 39 | user18@example.com | viewer | Design |
| 19 | Charlie | 40 | user19@example.com | admin | Marketing |
| 20 | Diana | 41 | user20@example.com | editor | Sales |
| 21 | Eve | 22 | user21@example.com | viewer | Engineering |
| 22 | Frank | 23 | user22@example.com | admin | Design |
| 23 | Grace | 24 | user23@example.com | editor | Marketing |
| 24 | Hank | 25 | user24@example.com | viewer | Sales |
| 25 | Alice | 26 | user25@example.com | admin | Engineering |
| 26 | Bob | 27 | user26@example.com | editor | Design |
| 27 | Charlie | 28 | user27@example.com | viewer | Marketing |
| 28 | Diana | 29 | user28@example.com | admin | Sales |
| 29 | Eve | 30 | user29@example.com | editor | Engineering |
| 30 | Frank | 31 | user30@example.com | viewer | Design |
| 31 | Grace | 32 | user31@example.com | admin | Marketing |
| 32 | Hank | 33 | user32@example.com | editor | Sales |
| 33 | Alice | 34 | user33@example.com | viewer | Engineering |
| 34 | Bob | 35 | user34@example.com | admin | Design |
| 35 | Charlie | 36 | user35@example.com | editor | Marketing |
| 36 | Diana | 37 | user36@example.com | viewer | Sales |
| 37 | Eve | 38 | user37@example.com | admin | Engineering |
| 38 | Frank | 39 | user38@example.com | editor | Design |
| 39 | Grace | 40 | user39@example.com | viewer | Marketing |
| 40 | Hank | 41 | user40@example.com | admin | Sales |
| 41 | Alice | 22 | user41@example.com | editor | Engineering |
| 42 | Bob | 23 | user42@example.com | viewer | Design |
| 43 | Charlie | 24 | user43@example.com | admin | Marketing |
| 44 | Diana | 25 | user44@example.com | editor | Sales |
| 45 | Eve | 26 | user45@example.com | viewer | Engineering |
| 46 | Frank | 27 | user46@example.com | admin | Design |
Expandable rows
Expand a record for additional details instead of placing everything in columns.
ID | Name | Age | Email | Role | ||
|---|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | ||
Alice works in Engineering as admin. | ||||||
| 2 | Bob | 23 | user2@example.com | editor | ||
| 3 | Charlie | 24 | user3@example.com | viewer | ||
| 4 | Diana | 25 | user4@example.com | admin | ||
| 5 | Eve | 26 | user5@example.com | editor | ||
| 6 | Frank | 27 | user6@example.com | viewer | ||
Expansion with scrolling
Combine expandable detail with a fixed body height and inspect scrolling and alignment.
Name | Email | Department | Role | |
|---|---|---|---|---|
| Alice | user1@example.com | Engineering | admin | |
| Bob | user2@example.com | Design | editor | |
Bob works in Design as editor; this text stays inside the visible area while the table scrolls sideways. | ||||
| Charlie | user3@example.com | Marketing | viewer | |
| Diana | user4@example.com | Sales | admin | |
| Eve | user5@example.com | Engineering | editor | |
Summary rows
Render totals with Table.Summary and align summary cells with table columns.
Name | Department | Email | Age |
|---|---|---|---|
| Alice | Engineering | user1@example.com | 22 |
| Bob | Design | user2@example.com | 23 |
| Charlie | Marketing | user3@example.com | 24 |
| Diana | Sales | user4@example.com | 25 |
| Eve | Engineering | user5@example.com | 26 |
| Frank | Design | user6@example.com | 27 |
| Grace | Marketing | user7@example.com | 28 |
| Hank | Sales | user8@example.com | 29 |
| Alice | Engineering | user9@example.com | 30 |
| Bob | Design | user10@example.com | 31 |
| Charlie | Marketing | user11@example.com | 32 |
| Diana | Sales | user12@example.com | 33 |
| Eve | Engineering | user13@example.com | 34 |
| Frank | Design | user14@example.com | 35 |
| Grace | Marketing | user15@example.com | 36 |
| Hank | Sales | user16@example.com | 37 |
| Alice | Engineering | user17@example.com | 38 |
| Bob | Design | user18@example.com | 39 |
| Charlie | Marketing | user19@example.com | 40 |
| Diana | Sales | user20@example.com | 41 |
| Total | 20 people | 630 | |
Custom pagination
Control pagination in application state when working with server totals and page data.
ID | Name | Age | Email | Role |
|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin |
| 2 | Bob | 23 | user2@example.com | editor |
| 3 | Charlie | 24 | user3@example.com | viewer |
| 4 | Diana | 25 | user4@example.com | admin |
| 5 | Eve | 26 | user5@example.com | editor |
Combined features
Combine sorting, filtering, and selection and observe how they affect the current data.
ID | Email | Role | Dept | Actions | |||
|---|---|---|---|---|---|---|---|
| 1 | Alice | 22 | user1@example.com | admin | Engineering | ||
| 2 | Bob | 23 | user2@example.com | editor | Design | ||
| 3 | Charlie | 24 | user3@example.com | viewer | Marketing | ||
| 4 | Diana | 25 | user4@example.com | admin | Sales | ||
| 5 | Eve | 26 | user5@example.com | editor | Engineering | ||
| 6 | Frank | 27 | user6@example.com | viewer | Design | ||
| 7 | Grace | 28 | user7@example.com | admin | Marketing | ||
| 8 | Hank | 29 | user8@example.com | editor | Sales | ||
| 9 | Alice | 30 | user9@example.com | viewer | Engineering | ||
| 10 | Bob | 31 | user10@example.com | admin | Design |
Responsive columns
Use responsive column settings on smaller screens while retaining identifying fields.