CHANGELOG.md

@refinedev/react-table

5.6.8

Patch Changes

• #5765 0c197d82393 Thanks @aliemir! - refactor: package bundles and package.json configuration for exports

  Previously, Refine packages had exported ESM and CJS bundles with same .js extension and same types for both with .d.ts extensions. This was causing issues with bundlers and compilers to pick up the wrong files for the wrong environment. Now we're outputting ESM bundles with .mjs extension and CJS bundles with .cjs extension. Also types are now exported with both .d.mts and .d.cts extensions.

  In older versions ESM and CJS outputs of some packages were using wrong imports/requires to dependencies causing errors in some environments. This will be fixed since now we're also enforcing the module type with extensions.

  Above mentioned changes also supported with changes in package.json files of the packages to support the new extensions and types. All Refine packages now include exports fields in their configuration to make sure the correct bundle is picked up by the bundlers and compilers.

• #5754 56ed144a0f5 Thanks @alicanerdurmaz! - chore: TypeScript upgraded to v5.x.x. #5752

• #5755 404b2ef5e1b Thanks @BatuhanW! - fix: incorrect type imports

5.6.7

Patch Changes

• #5695 79865affa1c Thanks @BatuhanW! - chore: apply biome format and fix lint errors.

5.6.6

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

5.6.5

Patch Changes

• #5425 190af9fce2 Thanks @aliemir! - Updated @refinedev/core peer dependencies to latest (^4.46.1)

5.6.4

Patch Changes

• #5022 80513a4e42f Thanks @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 80513a4e42f Thanks @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 8e5efffbb23 Thanks @aliemir! - Keep the hook and component names in builds for better debugging.

5.6.1

Patch Changes

• #4948 8e5efffbb23 Thanks @aliemir! - Keep the hook and component names in builds for better debugging.

5.6.0

Minor Changes

• #4741 026ccf34356 Thanks @aliemir! - Added sideEffects: false to package.json to help bundlers tree-shake unused code.

5.5.0

Minor Changes

• #4741 026ccf34356 Thanks @aliemir! - Added sideEffects: false to package.json to help bundlers tree-shake unused code.

5.4.0

Minor Changes

• #4194 8df15fe0e4e Thanks @alicanerdurmaz! - feat: sorters.mode prop added to useTable and useDataGrid hooks. This prop handles the sorting mode of the table. It can be either server or off.

  • "off": sorters are not sent to the server. You can use the sorters value to sort the records on the client side.
  • "server": Sorting is done on the server side. Records will be fetched by using the sorters value.

  feat:filters.mode prop added to useTable and useDataGrid hooks. This prop handles the filtering mode of the table. It can be either server or off.

  • "off": filters are not sent to the server. You can use the filters value to filter the records on the client side.
  • "server": Filtering is done on the server side. Records will be fetched by using the filters value.

5.3.0

Minor Changes

• #4194 8df15fe0e4e Thanks @alicanerdurmaz! - feat: sorters.mode prop added to useTable and useDataGrid hooks. This prop handles the sorting mode of the table. It can be either server or off.

  • "off": sorters are not sent to the server. You can use the sorters value to sort the records on the client side.
  • "server": Sorting is done on the server side. Records will be fetched by using the sorters value.

  feat:filters.mode prop added to useTable and useDataGrid hooks. This prop handles the filtering mode of the table. It can be either server or off.

  • "off": filters are not sent to the server. You can use the filters value to filter the records on the client side.
  • "server": Filtering is done on the server side. Records will be fetched by using the filters value.

5.2.0

Minor Changes

• #4113 1c13602e308 Thanks @salihozdemir! - Added missing third generic parameter to hooks which are using useQuery internally.

  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 1c13602e308 Thanks @salihozdemir! - Updated the generic type name of hooks that use useQuery to synchronize generic type names with tanstack-query.

5.1.4

Patch Changes

• #3827 c3e1a1b1c91 Thanks @thiagotognoli! - Added operator field to columnFilter state. This allows you to specify the filter operator without using column definition.

5.1.3

Patch Changes

• #3827 c3e1a1b1c91 Thanks @thiagotognoli! - Added operator field to columnFilter state. This allows you to specify the filter operator without using column definition.

5.1.2

Patch Changes

• #3941 d202e6ac17c Thanks @salihozdemir! - Fixed an issue where current was 1 when filters and sorters were in the URL when syncWithLocation was enabled.

5.1.1

Patch Changes

• #3941 d202e6ac17c Thanks @salihozdemir! - Fixed an issue where current was 1 when filters and sorters were in the URL when syncWithLocation was enabled.

5.1.0

Minor Changes

• Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk! All @tanstack/react-table imports re-exported from @refinedev/react-table have been removed. You should import them from the @tanstack/react-table package 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-table

  After that, you can import them from @tanstack/react-table package 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! useTable return values and properties are updated.

  • initialCurrent and initialPageSize props are now deprecated. Use pagination prop instead.

  • To ensure backward compatibility, initialCurrent and initialPageSize props will work as before.

    useTable({
    -    initialCurrent,
    -    initialPageSize,
    +    pagination: {
    +        current,
    +        pageSize,
    +    },
    })

  • hasPagination prop is now deprecated. Use pagination.mode instead.

  • To ensure backward compatibility, hasPagination prop will work as before.

    useTable({
        refineCoreProps: {
    -      hasPagination,
    +       pagination: {
    +           mode: "off" | "server" | "client",
    +       },
        },
    })

  • initialSorter and permanentSorter props are now deprecated. Use sorters.initial and sorters.permanent instead.

  • To ensure backward compatibility, initialSorter and permanentSorter props will work as before.

    useTable({
        refineCoreProps: {
    -      initialSorter,
    -      permanentSorter,
    +      sorters: {
    +          initial,
    +          permanent,
    +      },
        },
    })

  • initialFilter, permanentFilter, and defaultSetFilterBehavior props are now deprecated. Use filters.initial, filters.permanent, and filters.defaultBehavior instead.

  • To ensure backward compatibility, initialFilter, permanentFilter, and defaultSetFilterBehavior props will work as before.

    useTable({
        refineCoreProps: {
    -      initialFilter,
    -      permanentFilter,
    -      defaultSetFilterBehavior,
    +      filters: {
    +          initial,
    +          permanent,
    +          defaultBehavior,
    +      },
        },
    })

  • sorter and setSorter return values are now deprecated. Use sorters and setSorters instead.

  • To ensure backward compatibility, sorter and setSorter return values will work as before.

    const {
        refineCore: {
    -        sorter,
    -        setSorter,
    +        sorters,
    +        setSorters,
        },
    } = useTable();

• Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk! Moving to the @refinedev scope 🎉🎉

  Moved to the @refinedev scope and updated our packages to use the new scope. From now on, all packages will be published under the @refinedev scope with their new names.

  Now, we're also removing the refine prefix from all packages. So, the @pankod/refine-core package is now @refinedev/core, @pankod/refine-antd is now @refinedev/antd, and so on.

Patch Changes

4.11.0

Minor Changes

• #3822 0baa99ba787 Thanks @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 0baa99ba787 Thanks @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 22b44a857a8 Thanks @yildirayunlu! - Fix useTable hook error return type.

4.9.0

Minor Changes

• Only or was supported as a conditional filter. Now and and or can 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 addff64c77 Thanks @yildirayunlu! - Only or was supported as a conditional filter. Now and and or can 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-table exports

• Removed the old version of react-table dependency.

4.7.7

Patch Changes

• #2746 f19369d911 Thanks @omeraplak! - Fix @tanstack/react-table exports

• #2740 8a4a96ac6a Thanks @salihozdemir! - Removed the old version of react-table dependency.

4.7.6

Patch Changes

• Update @tanstack/react-table exports

• Fixed type exports for UseTableProps and UseTableReturnType.

• Update @pankod/refine-react-table exports

4.7.5

Patch Changes

• #2648 61db8c3800 Thanks @omeraplak! - Update @pankod/refine-react-table exports

4.7.4

Patch Changes

• #2648 61db8c3800 Thanks @omeraplak! - Update @tanstack/react-table exports

4.7.3

Patch Changes

• #2645 430c7a3d56 Thanks @omeraplak! - Fixed type exports for UseTableProps and UseTableReturnType.

4.7.2

Patch Changes

• Fixed version of react-router to 6.3.0

4.7.1

Patch Changes

• #2501 4095a578d4 Thanks @omeraplak! - Fixed version of react-router to 6.3.0

4.7.0

Minor Changes

• Update type declaration generation with tsc instead of tsup for better navigation throughout projects source code.

4.6.0

Minor Changes

• #2440 0150dcd070 Thanks @aliemir! - Update type declaration generation with tsc instead of tsup for better navigation throughout projects source code.

4.5.0

Minor Changes

• Add React@18 support 🚀

4.4.0

Minor Changes

• #1718 b38620d842 Thanks @omeraplak! - Add React@18 support 🚀

4.3.0

Minor Changes

• All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems like the best way for now to avoid such issues.

4.2.0

Minor Changes

• #2217 b4aae00f77 Thanks @omeraplak! - All of the refine packages have dependencies on the @pankod/refine-core package. So far we have managed these dependencies with peerDependencies + dependencies but this causes issues like #2183. (having more than one @pankod/refine-core version in node_modules and creating different instances)

  Managing as peerDependencies + devDependencies seems 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 d9cac36454 Thanks @salihozdemir! - Upgrade the package accordingly to Tanstack Table v8.

3.27.0

Minor Changes

• Add hasPagination property to useTable hook to enable/disable pagination.

  Implementation

  Updated the useTable hook accordingly to the changes in the useTable of @pankod/refine-core. hasPagination property is being send directly to the useTable of @pankod/refine-core to 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 hasPagination to false.

Patch Changes

• Updated dependencies []:
  • @pankod/refine-core@3.36.0

3.26.0

Minor Changes

• #2050 635cfe9fdb Thanks @ozkalai! - Add hasPagination property to useTable hook to enable/disable pagination.

  Implementation

  Updated the useTable hook accordingly to the changes in the useTable of @pankod/refine-core. hasPagination property is being send directly to the useTable of @pankod/refine-core to 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 hasPagination to false.

Patch Changes

• Updated dependencies [ecde34a9b3, 635cfe9fdb]:
  • @pankod/refine-core@3.35.0

3.22.2

Patch Changes

• Updated dependencies [2deb19babf]:
  • @pankod/refine-core@3.23.2