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
> 🧠 Think of this option as an arbitrary "context" for your table. This is a great way to pass arbitrary data or functions to your table without having to pass it to every thing the table touches. A good example is passing a locale object to your table to use for formatting dates, numbers, etc or even a function that can be used to update editable data like in the [editable-data example](../examples/react/editable-data).
92
+
> 🧠 Think of this option as an arbitrary "context" for your table. This is a great way to pass arbitrary data or functions to your table without having to pass it to every thing the table touches. A good example is passing a locale object to your table to use for formatting dates, numbers, etc or even a function that can be used to update editable data like in the [editable-data example](../framework/react/examples/editable-data).
@@ -166,7 +166,7 @@ TanStack Table keeps track of an state object called `columnSizingInfo` that you
166
166
167
167
If you are creating large or complex tables (and using React 😉), you may find that if you do not add proper memoization to your render logic, your users may experience degraded performance while resizing columns.
168
168
169
-
We have created a [performant column resizing example](../examples/react/column-resizing-performant) that demonstrates how to achieve 60 fps column resizing renders with a complex table that may otherwise have slow renders. It is recommended that you just look at that example to see how it is done, but these are the basic things to keep in mind:
169
+
We have created a [performant column resizing example](../framework/react/examples/column-resizing-performant) that demonstrates how to achieve 60 fps column resizing renders with a complex table that may otherwise have slow renders. It is recommended that you just look at that example to see how it is done, but these are the basic things to keep in mind:
170
170
171
171
1. Don't use `column.getSize()` on every header and every data cell. Instead, calculate all column widths once upfront, **memoized**!
172
172
2. Memoize your Table Body while resizing is in progress.
Copy file name to clipboardexpand all lines: docs/guide/row-models.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -90,10 +90,10 @@ For normal rendering use cases, you will probably only need to use the `table.ge
90
90
- `getPaginationRowModel` - returns a row model that only includes the rows that should be displayed on the current page based on the pagination state.
91
91
- `getPrePaginationRowModel` - returns a row model without pagination applied (includes all rows).
92
92
93
-
- `getSelectedRowModel` - returns a row model of all selected rows (but only based on the `data` that was passed to the table). Runs after `getCoreRowModel`.
94
-
- `getPreSelectedRowModel` - returns a row model before row selection is applied (Just returns `getCoreRowModel`).
95
-
- `getGroupedSelectedRowModel` - returns a row model of selected rows after grouping. Runs after `getSortedRowModel`, which runs after `getGroupedRowModel`, which runs after `getFilteredRowModel`.
96
-
- `getFilteredSelectedRowModel` - returns a row model of selected rows after column filtering and global filtering. Runs after `getFilteredRowModel`.
93
+
- `getSelectedRowModel` - returns a row model of all selected rows (but only based on the data that was passed to the table). Runs after getCoreRowModel.
94
+
- `getPreSelectedRowModel` - returns a row model before row selection is applied (Just returns getCoreRowModel).
95
+
- `getGroupedSelectedRowModel` - returns a row model of selected rows after grouping. Runs after getSortedRowModel, which runs after getGroupedRowModel, which runs after getFilteredRowModel.
96
+
- `getFilteredSelectedRowModel` - returns a row model of selected rows after column filtering and global filtering. Runs after getFilteredRowModel.
97
97
98
98
### The Order of Row Model Execution
99
99
@@ -103,7 +103,7 @@ Internally, this is the order in which each of the row models are applied to the
If in any case the respective is disabled or turned off with a `"manual*"tableoption, the`getPre*RowModel`willbeusedinsteadinthatstepoftheprocess.
106
+
If in any case the respective feature is disabled or turned off with a `"manual*"` table option, the `getPre*RowModel` will be used instead in that step of the process.
107
107
108
108
As you can see above, first the data is filtered, then grouped, then sorted, then expanded, and then finally paginated as the final step.
0 commit comments