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
Copy file name to clipboardExpand all lines: docs/guide/cells.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,15 @@ title: Cells Guide
4
4
5
5
## API
6
6
7
-
[Cell API](../../api/core/cell)
7
+
[Cell API](../api/core/cell)
8
8
9
9
## Cells Guide
10
10
11
11
This quick guide will discuss the different ways you can retrieve and interact with `cell` objects in TanStack Table.
12
12
13
13
### Where to Get Cells From
14
14
15
-
Cells come from [Rows](../rows). Enough said, right?
15
+
Cells come from [Rows](./rows). Enough said, right?
16
16
17
17
There are multiple `row` instance APIs you can use to retrieve the appropriate cells from a row depending on which features you are using. Most commonly, you will use the `row.getAllCells` or `row.getVisibleCells` APIs (if you are using column visibility features), but there are a handful of other similar APIs that you can use.
18
18
@@ -32,7 +32,7 @@ During grouping or aggregation features, the `cell.id` will have additional stri
32
32
33
33
#### Cell Parent Objects
34
34
35
-
Every cell stores a reference to its parent [row](../rows) and [column](../columns) objects.
35
+
Every cell stores a reference to its parent [row](./rows) and [column](./columns) objects.
> Note: This guide is about setting up column definitions for your table and NOT about the actual [`column`](../columns) objects that are generated within the table instance.
11
+
> Note: This guide is about setting up column definitions for your table and NOT about the actual [`column`](./columns) objects that are generated within the table instance.
12
12
13
13
Column defs are the single most important part of building a table. They are responsible for:
14
14
15
15
- Building the underlying data model that will be used for everything including sorting, filtering, grouping, etc.
16
16
- Formatting the data model into what will be displayed in the table
17
-
- Creating [header groups](../../../api/core/header-group), [headers](../../../api/core/header) and [footers](../../../api/core/column-def#footer)
17
+
- Creating [header groups](../api/core/header-group), [headers](../api/core/header) and [footers](../api/core/column-def#footer)
18
18
- Creating columns for display-only purposes, eg. action buttons, checkboxes, expanders, sparklines, etc.
@@ -31,7 +31,7 @@ TanStack table supports both client-side and manual server-side filtering. This
31
31
32
32
If you have a large dataset, you may not want to load all of that data into the client's browser in order to filter it. In this case, you will most likely want to implement server-side filtering, sorting, pagination, etc.
33
33
34
-
However, as also discussed in the [Pagination Guide](../pagination#should-you-use-client-side-pagination), a lot of developers underestimate how many rows can be loaded client-side without a performance hit. The TanStack table examples are often tested to handle up to 100,000 rows or more with decent performance for client-side filtering, sorting, pagination, and grouping. This doesn't necessarily mean that your app will be able to handle that many rows, but if your table is only going to have a few thousand rows at most, you might be able to take advantage of the client-side filtering, sorting, pagination, and grouping that TanStack table provides.
34
+
However, as also discussed in the [Pagination Guide](./pagination#should-you-use-client-side-pagination), a lot of developers underestimate how many rows can be loaded client-side without a performance hit. The TanStack table examples are often tested to handle up to 100,000 rows or more with decent performance for client-side filtering, sorting, pagination, and grouping. This doesn't necessarily mean that your app will be able to handle that many rows, but if your table is only going to have a few thousand rows at most, you might be able to take advantage of the client-side filtering, sorting, pagination, and grouping that TanStack table provides.
35
35
36
36
> TanStack Table can handle thousands of client-side rows with good performance. Don't rule out client-side filtering, pagination, sorting, etc. without some thought first.
0 commit comments