refine

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies [db9756e7908]:

• @refinedev/[email protected]

• @refinedev/[email protected]

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies [db9756e7908]:

• @refinedev/[email protected]

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies [db9756e7908]:

• @refinedev/[email protected]
• @refinedev/[email protected]
• @refinedev/[email protected]

#5925 b840c4b224e Thanks @aliemir! - chore: update superplate-cli dependency to latest

This updates the superplate-cli and includes a fix for the re-initializing git repository issue. Now when a new project is created, it will check if the current directory is a git repository and if it is, it will not re-initialize it.

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies [db9756e7908]:

• @refinedev/[email protected]

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies []:

• @refinedev/[email protected]

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies [db9756e7908]:

• @refinedev/[email protected]
• @refinedev/[email protected]

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

Updated dependencies [db9756e7908]:

• @refinedev/[email protected]

#5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

#5881 ba719f6ea26 Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions

Updated dependencies [1c9a95f22ab, 0a76576da0f, 8d2dd4376f6, 1c9a95f22ab, ba719f6ea26, 9a0c1c8414a]:

• @refinedev/[email protected]

#5881 ba719f6ea26 Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions

Updated dependencies [1c9a95f22ab, 0a76576da0f, 8d2dd4376f6, 1c9a95f22ab, ba719f6ea26, 9a0c1c8414a]:

• @refinedev/[email protected]
• @refinedev/[email protected]

#5841 7b13515b3c0 Thanks @issa012! - fix: in methods update, updateMany, create, createMany, meta.select changed to "*". Resolves #5679

#5881 ba719f6ea26 Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions

#5850 c2ef59bf82f Thanks @aliemir! - fix: replace imports of qs with default imports

Updated qs imports and usage to prevent issues with ESM builds and to ensure correctly importing the module.

#5881 ba719f6ea26 Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions

#5850 c2ef59bf82f Thanks @aliemir! - fix: replace imports of qs with default imports

Updated qs imports and usage to prevent issues with ESM builds and to ensure correctly importing the module.

#5881 ba719f6ea26 Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions

#5862 7c22b8eaca0 Thanks @aliemir! - fix: updated column filter transformation logic to handle conditional filters

useTable hook was ignoring the conditional filters with "and" and "or" operators, causing custom filtering logic inside the table to not work as expected and omitting the filters from the query. This PR enables working with conditionenal filters and fixes the disappearing filters issue.

To customize the key value of the conditional filter, you can use the filterKey property in the column's meta property. This property will be used as the key for the filter when setting the filter value to the table from @refinedev/core's filter state and when setting the filter value to the filter state from the table.

// An example of how to use the `filterKey` property in the column's `meta` property
const columns: ColumnDef<IPost> = [
  {
    id: "title",
    header: "Title",
    accessorKey: "title",
    meta: {
      // This is optional, if not defined column id will be used as the key
      filterKey: "titleFilter",
      // If operator is not `'eq'` or `'in'`, make sure to set the `filterOperator` property
      filterOperator: "and",
    },
  },
];

Resolves #5856

#5881 ba719f6ea26 Thanks @aliemir! - fix: declaration files in node10, node16 and nodenext module resolutions