useTable
useTable allows us to fetch data according to the sorter, filter, and pagination states. Under the hood it uses useList for the fetch. Since it is designed as headless, It expects you to handle the UI.
INFORMATION
If you're looking for a complete table library, Refine supports two table libraries out of the box.
- React Table (for TanStack Table users) - Documentation - Example
- Ant Design Table (for Ant Design users) - Documentation - Example
- Material UI Table (for Material UI users) - Documentation - Example
Basic Usage
In basic usage, useTable returns the data as it comes from the endpoint. By default, it reads resource from the URL.
Pagination
useTable has a pagination feature. The pagination is done by using the current and pageSize props. The current is the current page and the pageSize is the number of records per page.
It also syncs the pagination state with the URL if you enable the syncWithLocation.
By default, the current is 1 and the pageSize is 10. You can change default values by passing the initialCurrent and initialPageSize props to the useTable hook.
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.
If you want to disable pagination, you can use hasPagination property in useTable config and set it to false
INFORMATION
If hasPagination is set to false, current, setCurrent, pageSize, setPageSize, and pageCount will return undefined
Sorting
useTable has a sorter feature. The sorter is done by using the sorter state. The sorter state is a CrudSorting type that contains the field and the order of the sort. You can change the sorter state by using the setSorter function. Every change will trigger a new fetch.
It also syncs the sorting state with the URL if you enable the syncWithLocation.
Also, you can add an initial sorter state by passing the initialSorter prop and a permanent sorter state by passing the permanentSorter prop to the useTable hook. Even if you change the sorter state, the permanentSorter will be used together with the sorter state.
Filtering
useTable has a filter feature. The filter is done by using the filters state. The filters state is a CrudFilters type that contains the field, the operator, and the value of the filter. You can change the filter state by using the setFilters function. Every change will trigger a new fetch.
It also syncs the filtering state with the URL if you enable the syncWithLocation.
Also you can add an initial filter state by passing the initialFilter prop and a permanent filter state by passing the permanentFilter prop to the useTable hook. Even if you change the filter state, the permanentFilter will be used together with the filter state.
setFilters function can work in two different behaviors; merge (default) and replace. You can set the behavior by passing it as the 2nd parameter. You can change the default behavior with defaultSetFilterBehavior prop.
You can also call setFilters with a setter function.
INFORMATION
If you are using merge behavior and want to remove one of the filters; you should set the value to undefined or null. For or filters, you should set the value to an empty array [] to remove the filter.
Realtime Updates
This feature is only available if you use a Live Provider.
When the useTable hook is mounted, it will call the subscribe method from the liveProvider with some parameters such as channel, resource etc. It is useful when you want to subscribe to live updates.
Refer to the liveProvider documentation for more information →
Properties
resource
Default: It reads the
resourcevalue from the current URL.
It will be passed to the getList method from the dataProvider as parameter via the useList hook.
The parameter is usually used as an API endpoint path.
It all depends on how to handle the resource in the getList method.
See the creating a data provider section for an example of how resources are handled.
useTable({
resource: "categories",
});
dataProviderName
If there is more than one dataProvider, you should use the dataProviderName that you will use. It is useful when you want to use a different dataProvider for a specific resource.
useTable({
dataProviderName: "second-data-provider",
});
initialCurrent
Default:
1
Sets the initial value of the page index.
useTable({
initialCurrent: 2, // This will cause the table to initially display the data for page 2, rather than the default of page 1
});
initialPageSize
Default:
10
Sets the initial value of the page size.
useTable({
initialPageSize: 20, // This will cause the table to initially display 20 rows per page, rather than the default of 10
});
initialSorter
Sets the initial value of the sorter. The initialSorter is not permanent. It will be cleared when the user changes the sorter. If you want to set a permanent value, use the permanentSorter prop.
useTable({
initialSorter: [
{
field: "title",
order: "asc",
},
],
});
permanentSorter
Sets the permanent value of the sorter. The permanentSorter is permanent and unchangeable. It will not be cleared when the user changes the sorter. If you want to set a temporary value, use the initialSorter prop.
useTable({
permanentSorter: [
{
field: "title",
order: "asc",
},
],
});
initialFilter
Type:
CrudFilter[]
Sets the initial value of the filter. The initialFilter is not permanent. It will be cleared when the user changes the filter. If you want to set a permanent value, use the permanentFilter prop.
useTable({
initialFilter: [
{
field: "title",
operator: "contains",
value: "Foo",
},
],
});
permanentFilter
Type:
CrudFilter[]
Sets the permanent value of the filter. The permanentFilter is permanent and unchangeable. It will not be cleared when the user changes the filter. If you want to set a temporary value, use the initialFilter prop.
useTable({
permanentFilter: [
{
field: "title",
operator: "contains",
value: "Foo",
},
],
});
defaultSetFilterBehavior
Default:
merge
The filtering behavior can be set to either "merge" or "replace".
When the filter behavior is set to
"merge", it will merge the new filter with the existing filters. This means that if the new filter has the same column as an existing filter, the new filter will replace the existing filter for that column. If the new filter has a different column than the existing filters, it will be added to the existing filters.When the filter behavior is set to
"replace", it will replace all existing filters with the new filter. This means that any existing filters will be removed and only the new filter will be applied to the table.
You can also override the default value by using the second parameter of the setFilters function.
useTable({
defaultSetFilterBehavior: "replace",
});
hasPagination
Default:
true
Determines whether to use server-side pagination or not.
useTable({
hasPagination: false,
});
syncWithLocation
Default:
false
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.
Also you can set this value globally on <Refine> component.
useTable({
syncWithLocation: true,
});
queryOptions
useTable uses useList hook to fetch data. You can pass queryOptions.
useTable({
queryOptions: {
retry: 3,
},
});
metaData
metaData is used following two purposes:
- To pass additional information to data provider methods.
- Generate GraphQL queries using plain JavaScript Objects (JSON). Please refer GraphQL for more information.
In the following example, we pass the headers property in the metaData object to the create method. With similar logic, you can pass any properties to specifically handle the data provider methods.
useTable({
metaData: {
headers: { "x-meta-data": "true" },
},
});
const myDataProvider = {
//...
getList: async ({
resource,
pagination,
hasPagination,
sort,
filters,
metaData,
}) => {
const headers = metaData?.headers ?? {};
const url = `${apiUrl}/${resource}`;
//...
//...
const { data, headers } = await httpClient.get(`${url}`, { headers });
return {
data,
};
},
//...
};
successNotification
NotificationProvideris required for this prop to work.
After data is fetched successfully, useTable can call open function from NotificationProvider to show a success notification. With this prop, you can customize the success notification.
useTable({
successNotification: (data, values, resource) => {
return {
message: `${data.title} Successfully fetched.`,
description: "Success with no errors",
type: "success",
};
},
});
errorNotification
NotificationProvideris required for this prop to work.
After data fetching is failed, useTable will call open function from NotificationProvider to show an error notification. With this prop, you can customize the error notification.
useTable({
errorNotification: (data, values, resource) => {
return {
message: `Something went wrong when getting ${data.id}`,
description: "Error",
type: "error",
};
},
});
liveMode
LiveProvideris required for this prop to work.
Determines whether to update data automatically ("auto") or not ("manual") if a related live event is received. It can be used to update and show data in Realtime throughout your app. For more information about live mode, please check Live / Realtime page.
useTable({
liveMode: "auto",
});
onLiveEvent
LiveProvideris required for this prop to work.
The callback function is executed when new events from a subscription have arrived.
useTable({
onLiveEvent: (event) => {
console.log(event);
},
});
liveParams
LiveProvideris required for this prop to work.
Params to pass to liveProvider's subscribe method.
Return Values
tableQueryResult
Returned values from useList hook.
sorter
Current sorter state.
setSorter
(sorter: CrudSorting) => void;
A function to set current sorter state.
filters
Current filters state.
setFilters
((filters: CrudFilters, behavior?: SetFilterBehavior) => void) & ((setter: (prevFilters: CrudFilters) => CrudFilters) => void)
A function to set current filters state.
current
Current page index state. If pagination is disabled, it will be undefined.
setCurrent
React.Dispatch<React.SetStateAction<number>> | undefined;
A function to set the current page index state. If pagination is disabled, it will be undefined.
pageSize
Current page size state. If pagination is disabled, it will be undefined.
setPageSize
React.Dispatch<React.SetStateAction<number>> | undefined;
A function to set the current page size state. If pagination is disabled, it will be undefined.
pageCount
Total page count state. If pagination is disabled, it will be undefined.
createLinkForSyncWithLocation
(params: SyncWithLocationParams) => string;
A function creates accessible links for syncWithLocation. It takes SyncWithLocationParams as parameters.
FAQ
How can I handle relational data ?
You can use useMany hook to fetch relational data.
API
Properties
Type Parameters
| Property | Desription | Type | Default |
|---|---|---|---|
| TData | Result data of the query. Extends BaseRecord | BaseRecord | BaseRecord |
| TError | Custom error object that extends HttpError | HttpError | HttpError |
Return values
| Property | Description | Type |
|---|---|---|
| tableQueryResult | Result of the react-query's useQuery | QueryObserverResult<{`` data: TData[];`` total: number; },`` TError> |
| current | Current page index state (returns undefined if pagination is disabled) | number | undefined |
| pageCount | Total page count (returns undefined if pagination is disabled) | number | undefined |
| setCurrent | A function that changes the current (returns undefined if pagination is disabled) | React.Dispatch<React.SetStateAction<number>> | undefined |
| pageSize | Current pageSize state (returns undefined if pagination is disabled) | number | undefined |
| setPageSize | A function that changes the pageSize. (returns undefined if pagination is disabled) | React.Dispatch<React.SetStateAction<number>> | undefined |
| sorter | Current sorting state s | CrudSorting |
| setSorter | A function that accepts a new sorter state. | (sorter: CrudSorting) => void |
| filters | Current filters state | CrudFilters |
| setFilters | A function that accepts a new filter state | - (filters: CrudFilters, behavior?: "merge" \| "replace" = "merge") => void - (setter: (previousFilters: CrudFilters) => CrudFilters) => void |
| createLinkForSyncWithLocation | A function create accessible links for syncWithLocation | (params: SyncWithLocationParams) => string; |
- Basic Usage
- Pagination
- Sorting
- Filtering
- Realtime Updates
- Properties
resourcedataProviderNameinitialCurrentinitialPageSizeinitialSorterpermanentSorterinitialFilterpermanentFilterdefaultSetFilterBehaviorhasPaginationsyncWithLocationqueryOptionsmetaDatasuccessNotificationerrorNotificationliveModeonLiveEventliveParams- Return Values
tableQueryResultsortersetSorterfilterssetFilterscurrentsetCurrentpageSizesetPageSizepageCountcreateLinkForSyncWithLocation- FAQ
- How can I handle relational data ?
- API
- Properties
- Type Parameters
- Return values