Tables
Tables are essential in data-intensive applications, serving as the primary way for organizing and displaying data in a readable format using rows and columns. Their integration, however, is complex due to functionalities like sorting, filtering, and pagination. Refine's tables integration aims to make this process as simple as possible while providing as many real world features as possible out of the box. This guide will cover the basics of tables in Refine and how to use them.
Handling Data
useTable
allows us to fetch data according to the sorter, filter, and pagination states. Under the hood, it uses useList
for the fetch. Its designed to be headless, but Refine offers seamless integration with several popular UI libraries, simplifying the use of their table components.
- TanStack Table (for Headless, Chakra UI, Mantine) - Documentation) - Example
- Ant Design Table - Documentation - Example
- Material UI DataGrid - Documentation - Example
Basic Usage
The usage of the useTable
hooks may slightly differ between UI libraries, however, the core functionality of useTable
hook in @refinedev/core
stays consistent in all implementations. The useTable
hook in Refine's core is the foundation of all the other useTable
implementations.
- Refine's Core
- TanStack Table
- Ant Design
- Material UI
- MantineTanStack Table
- Chakra UITanStack Table
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest
Code Files
Check out Refine's useTable
reference page to learn more about the usage and see it in action.
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@tanstack/react-table@latest,@refinedev/react-table@latest
Code Files
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@refinedev/antd@latest,antd@latest
Code Files
Check out Ant Design's useTable
reference page to learn more about the usage and see it in action.
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@refinedev/mui@latest,@mui/x-data-grid@latest,@mui/material@latest,@mui/system@latest
Code Files
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@refinedev/mantine@latest,@refinedev/react-table@latest,@tanstack/react-table@latest,@mantine/core@^5.10.4,@tabler/icons-react@^3.1.0
Code Files
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@refinedev/react-table@latest,@tanstack/react-table@latest,@refinedev/chakra-ui@latest,@chakra-ui/react@^2.5.1,@tabler/icons-react@^3.1.0
Code Files
Pagination
useTable
has a pagination feature. The pagination is done by passing the current
, pageSize
and, mode
keys to pagination
object.
- current: The page index.
- pageSize: The number of items per page.
- mode: Whether to use server side pagination or not.
- When
server
is selected, the pagination will be handled on the server side. - When
client
is selected, the pagination will be handled on the client side. No request will be sent to the server. - When
off
is selected, the pagination will be disabled. All data will be fetched from the server.
- When
You can also change the current
and pageSize
values by using the setCurrent
and setPageSize
functions that are returned by the useTable
hook. Every change will trigger a new fetch.
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest
Code Files
Filtering
useTable
has a filter feature. The filter is done by using the initial
, permanent
, defaultBehavior
and mode
keys to filters
object.
These states are a CrudFilters
type for creating complex single or multiple queries.
- initial: The initial filter state. It can be changed by the
setFilters
function. - permanent: The default and unchangeable filter state. It can't be changed by the
setFilters
function. - defaultBehavior: The default behavior of the
setFilters
function.- When
merge
is selected, the new filters will be merged with the old ones. - When
replace
is selected, the new filters will replace the old ones. It means that the old filters will be deleted.
- When
- mode: Whether to use server side filter or not.
- When
server
is selected, the filters will be sent to the server. - When
off
is selected, the filters will be applied on the client side.
- When
useTable
will pass these states to dataProvider
for making it possible to fetch the data you need. Handling and adapting these states for API requests is the responsibility of the dataProvider
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest
Code Files
Sorting
useTable
has a sorter feature. The sorter is done by passing the initial
and permanent
keys to sorters
object. These states are a CrudSorter
type for creating single or multiple queries.
- initial: The initial sorter state. It can be changed by the
setSorters
function. - permanent: The default and unchangeable sorter state. It can't be changed by the
setSorters
function.
useTable
will pass these states to dataProvider
for making it possible to fetch the data you need. Handling and adapting these states for API requests is the responsibility of the dataProvider
You can change the sorters state by using the setSorters
function. Every change will trigger a new fetch.
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest
Code Files
Search
useTable
has a search feature with onSearch
. The search is done by using the onSearch
function with searchFormProps
. These feature enables you to easily connect form state to the table filters.
- onSearch: function is triggered when the
searchFormProps.onFinish
is called. It receives the form values as the first argument and expects a promise that returns aCrudFilters
type. - searchFormProps: Has necessary props for the
<form>
.
For example we can fetch product with the name that contains the search value.
- Ant Design
- Material UI
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@refinedev/antd@latest,antd@latest
Code Files
Check out Ant Design's useTable
reference page to learn more about the usage and see it in action.
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest,@refinedev/mui@latest,@mui/x-data-grid@latest,@mui/material@latest,@mui/system@latest
Code Files
Integrating with Routers
Resource Router IntegratedThis value can be inferred from the route. Click to see the guide for more information.
useTable
can infer current resource
from the current route based on your resource definitions. This eliminates the need of passing these parameters to the hooks manually.
useTable({
// When the current route is `/products`, the resource prop can be omitted.
resource: "products",
});
Sync with Location Router IntegratedThis value can be inferred from the route. Click to see the guide for more information. Globally ConfigurableThis value can be configured globally. Click to see the guide for more information.
When you use the syncWithLocation
feature, the useTable
's state (e.g., sort order, filters, pagination) is automatically encoded in the query parameters of the URL, and when the URL changes, the useTable
state is automatically updated to match. This makes it easy to share table state across different routes or pages, and to allow users to bookmark or share links to specific table views.
Relationships
Refine handles data relations with data hooks(eg: useOne
, useMany
, etc.). This compositional design allows you to flexibly and efficiently manage data relationships to suit your specific requirements.
For example imagine each post has a many category. We can fetch the categories of the post by using the useMany
hook.
Dependencies: @refinedev/core@latest,@refinedev/simple-rest@latest