From 4b3229a89ccd65ad57cd853dd7e1ca751fcd4760 Mon Sep 17 00:00:00 2001 From: Kevin Van Cott Date: Mon, 4 Mar 2024 20:46:32 -0600 Subject: [PATCH] docs: fix some links and typos --- docs/config.json | 2 +- docs/framework/react/guide/table-state.md | 4 ++-- docs/guide/pagination.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/config.json b/docs/config.json index 6d8f34d60e..26fe083c51 100644 --- a/docs/config.json +++ b/docs/config.json @@ -238,7 +238,7 @@ "label": "Core Guides", "children": [ { - "label": "Table State (React)", + "label": "Table State", "to": "framework/react/guide/table-state" } ] diff --git a/docs/framework/react/guide/table-state.md b/docs/framework/react/guide/table-state.md index 6c2a342587..302e43c2f7 100644 --- a/docs/framework/react/guide/table-state.md +++ b/docs/framework/react/guide/table-state.md @@ -6,8 +6,8 @@ title: Table State (React) Guide Want to skip to the implementation? Check out these examples: -- [kitchen sink](../examples/kitchen-sink) -- [fully controlled](../examples/fully-controlled) +- [kitchen sink](../framework/react/examples/kitchen-sink) +- [fully controlled](../framework/react/examples/fully-controlled) ## Table State (React) Guide diff --git a/docs/guide/pagination.md b/docs/guide/pagination.md index b900926e73..17ff9ee931 100644 --- a/docs/guide/pagination.md +++ b/docs/guide/pagination.md @@ -63,11 +63,11 @@ const table = useReactTable({ If you decide that you need to use server-side pagination, here is how you can implement it. -No pagination row model is needed for server-side pagination, but if you have provided it for other tables that do need it in a shared component, you can still turn off the client-side pagination by setting the `manualPagination` option to `true`. Setting to the `manualPagination` option to `true` will tell the table instance to use the `table.getPrePaginationRowModel` row model under the hood, and it will make the table instance assume that the `data` that you pass in is already paginated. +No pagination row model is needed for server-side pagination, but if you have provided it for other tables that do need it in a shared component, you can still turn off the client-side pagination by setting the `manualPagination` option to `true`. Setting the `manualPagination` option to `true` will tell the table instance to use the `table.getPrePaginationRowModel` row model under the hood, and it will make the table instance assume that the `data` that you pass in is already paginated. #### Page Count and Row Count -Also, the table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case. +The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case. ```jsx import { useReactTable, getCoreRowModel, getPaginationRowModel } from '@tanstack/react-table';