21 KiB
@refinedev/react-table
5.6.5
Patch Changes
- #5425
190af9fce2Thanks @aliemir! - Updated@refinedev/corepeer dependencies to latest (^4.46.1)
5.6.4
Patch Changes
-
#5022
80513a4e42fThanks @BatuhanW! - chore: update README.md- fix grammar errors.
- make all README.md files consistent.
- add code example code snippets.
5.6.3
Patch Changes
-
#5022
80513a4e42fThanks @BatuhanW! - chore: update README.md- fix grammar errors.
- make all README.md files consistent.
- add code example code snippets.
5.6.2
Patch Changes
- #4948
8e5efffbb23Thanks @aliemir! - Keep the hook and component names in builds for better debugging.
5.6.1
Patch Changes
- #4948
8e5efffbb23Thanks @aliemir! - Keep the hook and component names in builds for better debugging.
5.6.0
Minor Changes
- #4741
026ccf34356Thanks @aliemir! - AddedsideEffects: falsetopackage.jsonto help bundlers tree-shake unused code.
5.5.0
Minor Changes
- #4741
026ccf34356Thanks @aliemir! - AddedsideEffects: falsetopackage.jsonto help bundlers tree-shake unused code.
5.4.0
Minor Changes
-
#4194
8df15fe0e4eThanks @alicanerdurmaz! - feat:sorters.modeprop added touseTableanduseDataGridhooks. This prop handles the sorting mode of the table. It can be eitherserveroroff.- "off":
sortersare not sent to the server. You can use thesortersvalue to sort the records on the client side. - "server": Sorting is done on the server side. Records will be fetched by using the
sortersvalue.
feat:
filters.modeprop added touseTableanduseDataGridhooks. This prop handles the filtering mode of the table. It can be eitherserveroroff.- "off":
filtersare not sent to the server. You can use thefiltersvalue to filter the records on the client side. - "server": Filtering is done on the server side. Records will be fetched by using the
filtersvalue.
- "off":
5.3.0
Minor Changes
-
#4194
8df15fe0e4eThanks @alicanerdurmaz! - feat:sorters.modeprop added touseTableanduseDataGridhooks. This prop handles the sorting mode of the table. It can be eitherserveroroff.- "off":
sortersare not sent to the server. You can use thesortersvalue to sort the records on the client side. - "server": Sorting is done on the server side. Records will be fetched by using the
sortersvalue.
feat:
filters.modeprop added touseTableanduseDataGridhooks. This prop handles the filtering mode of the table. It can be eitherserveroroff.- "off":
filtersare not sent to the server. You can use thefiltersvalue to filter the records on the client side. - "server": Filtering is done on the server side. Records will be fetched by using the
filtersvalue.
- "off":
5.2.0
Minor Changes
-
#4113
1c13602e308Thanks @salihozdemir! - Added missing third generic parameter to hooks which are usinguseQueryinternally.For example:
import { useOne, HttpError } from "@refinedev/core"; const { data } = useOne<{ count: string }, HttpError, { count: number }>({ resource: "product-count", queryOptions: { select: (rawData) => { return { data: { count: Number(rawData?.data?.count), }, }; }, }, }); console.log(typeof data?.data.count); // number
Patch Changes
- #4113
1c13602e308Thanks @salihozdemir! - Updated the generic type name of hooks that useuseQueryto synchronize generic type names withtanstack-query.
5.1.4
Patch Changes
- #3827
c3e1a1b1c91Thanks @thiagotognoli! - Addedoperatorfield tocolumnFilterstate. This allows you to specify the filter operator without using column definition.
5.1.3
Patch Changes
- #3827
c3e1a1b1c91Thanks @thiagotognoli! - Addedoperatorfield tocolumnFilterstate. This allows you to specify the filter operator without using column definition.
5.1.2
Patch Changes
- #3941
d202e6ac17cThanks @salihozdemir! - Fixed an issue wherecurrentwas 1 whenfiltersandsorterswere in the URL whensyncWithLocationwas enabled.
5.1.1
Patch Changes
- #3941
d202e6ac17cThanks @salihozdemir! - Fixed an issue wherecurrentwas 1 whenfiltersandsorterswere in the URL whensyncWithLocationwas enabled.
5.1.0
Minor Changes
-
Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk! All
@tanstack/react-tableimports re-exported from@refinedev/react-tablehave been removed. You should import them from the@tanstack/react-tablepackage directly.If the package is not installed, you can install it with your package manager:
npm install @tanstack/react-table # or pnpm add @tanstack/react-table # or yarn add @tanstack/react-tableAfter that, you can import them from
@tanstack/react-tablepackage directly.- import { useTable, ColumnDef, flexRender } from "@refinedev/react-table"; + import { useTable } from "@refinedev/react-table"; + import { ColumnDef, flexRender } from "@tanstack/react-table"; -
Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk!
useTablereturn values and properties are updated.-
initialCurrentandinitialPageSizeprops are now deprecated. Usepaginationprop instead. -
To ensure backward compatibility,
initialCurrentandinitialPageSizeprops will work as before.useTable({ - initialCurrent, - initialPageSize, + pagination: { + current, + pageSize, + }, }) -
hasPaginationprop is now deprecated. Usepagination.modeinstead. -
To ensure backward compatibility,
hasPaginationprop will work as before.useTable({ refineCoreProps: { - hasPagination, + pagination: { + mode: "off" | "server" | "client", + }, }, }) -
initialSorterandpermanentSorterprops are now deprecated. Usesorters.initialandsorters.permanentinstead. -
To ensure backward compatibility,
initialSorterandpermanentSorterprops will work as before.useTable({ refineCoreProps: { - initialSorter, - permanentSorter, + sorters: { + initial, + permanent, + }, }, }) -
initialFilter,permanentFilter, anddefaultSetFilterBehaviorprops are now deprecated. Usefilters.initial,filters.permanent, andfilters.defaultBehaviorinstead. -
To ensure backward compatibility,
initialFilter,permanentFilter, anddefaultSetFilterBehaviorprops will work as before.useTable({ refineCoreProps: { - initialFilter, - permanentFilter, - defaultSetFilterBehavior, + filters: { + initial, + permanent, + defaultBehavior, + }, }, }) -
sorterandsetSorterreturn values are now deprecated. UsesortersandsetSortersinstead. -
To ensure backward compatibility,
sorterandsetSorterreturn values will work as before.const { refineCore: { - sorter, - setSorter, + sorters, + setSorters, }, } = useTable();
-
-
Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk! Moving to the
@refinedevscope 🎉🎉Moved to the
@refinedevscope and updated our packages to use the new scope. From now on, all packages will be published under the@refinedevscope with their new names.Now, we're also removing the
refineprefix from all packages. So, the@pankod/refine-corepackage is now@refinedev/core,@pankod/refine-antdis now@refinedev/antd, and so on.
Patch Changes
4.11.0
Minor Changes
- #3822
0baa99ba787Thanks @BatuhanW! - - refine v4 release announcement added to "postinstall". - refine v4 is released 🎉 The new version is 100% backward compatible. You can upgrade to v4 with a single command! See the migration guide here: https://refine.dev/docs/migration-guide/3x-to-4x
4.10.0
Minor Changes
- #3822
0baa99ba787Thanks @BatuhanW! - - refine v4 release announcement added to "postinstall". - refine v4 is released 🎉 The new version is 100% backward compatible. You can upgrade to v4 with a single command! See the migration guide here: https://refine.dev/docs/migration-guide/3x-to-4x
4.9.1
Patch Changes
- #3399
22b44a857a8Thanks @yildirayunlu! - FixuseTablehook error return type.
4.9.0
Minor Changes
-
Only
orwas supported as a conditional filter. Nowandandorcan be used together and nested. 🚀{ operator: "or", value: [ { operator: "and", value: [ { field: "name", operator: "eq", value: "John Doe", }, { field: "age", operator: "eq", value: 30, }, ], }, { operator: "and", value: [ { field: "name", operator: "eq", value: "JR Doe", }, { field: "age", operator: "eq", value: 1, }, ], }, ], }
4.8.0
Minor Changes
-
#2751
addff64c77Thanks @yildirayunlu! - Onlyorwas supported as a conditional filter. Nowandandorcan be used together and nested. 🚀{ operator: "or", value: [ { operator: "and", value: [ { field: "name", operator: "eq", value: "John Doe", }, { field: "age", operator: "eq", value: 30, }, ], }, { operator: "and", value: [ { field: "name", operator: "eq", value: "JR Doe", }, { field: "age", operator: "eq", value: 1, }, ], }, ], }
4.7.8
Patch Changes
-
Fix
@tanstack/react-tableexports -
Removed the old version of
react-tabledependency.
4.7.7
Patch Changes
-
#2746
f19369d911Thanks @omeraplak! - Fix@tanstack/react-tableexports -
#2740
8a4a96ac6aThanks @salihozdemir! - Removed the old version ofreact-tabledependency.
4.7.6
Patch Changes
-
Update
@tanstack/react-tableexports -
Fixed type exports for
UseTablePropsandUseTableReturnType. -
Update
@pankod/refine-react-tableexports
4.7.5
Patch Changes
- #2648
61db8c3800Thanks @omeraplak! - Update@pankod/refine-react-tableexports
4.7.4
Patch Changes
- #2648
61db8c3800Thanks @omeraplak! - Update@tanstack/react-tableexports
4.7.3
Patch Changes
- #2645
430c7a3d56Thanks @omeraplak! - Fixed type exports forUseTablePropsandUseTableReturnType.
4.7.2
Patch Changes
- Fixed version of react-router to
6.3.0
4.7.1
Patch Changes
- #2501
4095a578d4Thanks @omeraplak! - Fixed version of react-router to6.3.0
4.7.0
Minor Changes
- Update type declaration generation with
tscinstead oftsupfor better navigation throughout projects source code.
4.6.0
Minor Changes
- #2440
0150dcd070Thanks @aliemir! - Update type declaration generation withtscinstead oftsupfor better navigation throughout projects source code.
4.5.0
Minor Changes
- Add React@18 support 🚀
4.4.0
Minor Changes
- #1718
b38620d842Thanks @omeraplak! - Add React@18 support 🚀
4.3.0
Minor Changes
-
All of the refine packages have dependencies on the
@pankod/refine-corepackage. So far we have managed these dependencies withpeerDependencies+dependenciesbut this causes issues like #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)Managing as
peerDependencies+devDependenciesseems like the best way for now to avoid such issues.
4.2.0
Minor Changes
-
#2217
b4aae00f77Thanks @omeraplak! - All of the refine packages have dependencies on the@pankod/refine-corepackage. So far we have managed these dependencies withpeerDependencies+dependenciesbut this causes issues like #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)Managing as
peerDependencies+devDependenciesseems like the best way for now to avoid such issues.
4.1.0
Minor Changes
- Upgrade the package accordingly to Tanstack Table v8.
4.0.0
Major Changes
- #2160
d9cac36454Thanks @salihozdemir! - Upgrade the package accordingly to Tanstack Table v8.
3.27.0
Minor Changes
-
Add
hasPaginationproperty touseTablehook to enable/disable pagination.Implementation
Updated the
useTablehook accordingly to the changes in theuseTableof@pankod/refine-core.hasPaginationproperty is being send directly to theuseTableof@pankod/refine-coreto disable pagination.Use Cases
In some data providers, some of the resources might not support pagination which was not supported prior to these changes. To handle the pagination on the client-side or to disable completely, users can set
hasPaginationtofalse.
Patch Changes
- Updated dependencies []:
3.26.0
Minor Changes
-
#2050
635cfe9fdbThanks @ozkalai! - AddhasPaginationproperty touseTablehook to enable/disable pagination.Implementation
Updated the
useTablehook accordingly to the changes in theuseTableof@pankod/refine-core.hasPaginationproperty is being send directly to theuseTableof@pankod/refine-coreto disable pagination.Use Cases
In some data providers, some of the resources might not support pagination which was not supported prior to these changes. To handle the pagination on the client-side or to disable completely, users can set
hasPaginationtofalse.
Patch Changes
- Updated dependencies [
ecde34a9b3,635cfe9fdb]:
3.22.2
Patch Changes
- Updated dependencies [
2deb19babf]: