OpenPanel/packages/strapi-v4/CHANGELOG.md
Stefan Pejcic 8595a9f4e5 back
2024-05-08 19:58:53 +02:00

22 KiB

@refinedev/strapi-v4

6.0.1

Patch Changes

6.0.0

Major Changes

Patch Changes

5.2.5

Patch Changes

  • #5054 6ab41f88343 Thanks @MahirMahdi! - Now useCustomMutation can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.

5.2.4

Patch Changes

  • #5054 6ab41f88343 Thanks @MahirMahdi! - Now useCustomMutation can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.

5.2.3

Patch Changes

  • #5054 6ab41f88343 Thanks @MahirMahdi! - Now useCustomMutation can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.

5.2.2

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.2.1

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.2.0

Minor Changes

  • #4652 96af6d25b7a Thanks @alicanerdurmaz! - feat: added error handling to support server-side validation errors.

    When the server returns default validation errors, update, create, updateMany, and createMany methods will throw an error with the validation errors. This allows the useForm update the error state with the validation errors.

5.1.0

Minor Changes

  • #4652 96af6d25b7a Thanks @alicanerdurmaz! - feat: added error handling to support server-side validation errors.

    When the server returns default validation errors, update, create, updateMany, and createMany methods will throw an error with the validation errors. This allows the useForm update the error state with the validation errors.

5.0.2

Patch Changes

5.0.1

Patch Changes

5.0.0

Major Changes

4.3.2

Patch Changes

  • #4196 05dd92662ce Thanks @salihozdemir! - fix: remove useStrapiUpload hook. It was outdated and not working properly.

    fix: update getValueProps logic to return the correct value.

4.3.1

Patch Changes

  • #4196 05dd92662ce Thanks @salihozdemir! - fix: remove useStrapiUpload hook. It was outdated and not working properly.

    fix: update getValueProps logic to return the correct value.

4.3.0

Minor Changes

  • #4182 a58e9a0f1b0 Thanks @alicanerdurmaz! - feat: added refine.config.js to support swizzling. Now with swizzle support, you can easily customize strapi-v4 data provider for your needs.

    feat: tests added for utility functions.

    chore: utility functions have been moved to their own files.

4.2.0

Minor Changes

  • #4182 a58e9a0f1b0 Thanks @alicanerdurmaz! - feat: added refine.config.js to support swizzling. Now with swizzle support, you can easily customize strapi-v4 data provider for your needs.

    feat: tests added for utility functions.

    chore: utility functions have been moved to their own files.

4.1.0

Minor Changes

  • Thanks @aliemir, @alicanerdurmaz, @batuhanW, @salihozdemir, @yildirayunlu, @recepkutuk!

    • metaData prop is now deprecated for all data provider methods. Use meta prop instead.

      For backward compatibility, we still support metaData prop with refine v4.

      create: async ({
      -    metaData
      +    meta
      }) => {
          ...
      },
      
    • sort, hasPagination, and metaData parameters of getList method are now deprecated. Use sorters, pagination, and meta parameters instead.

      For backward compatibility, we still support sort, hasPagination and metaData props with refine v4.

      getList: async ({
      -    sort
      +    sorters
      -    hasPagination
      +    pagination: { mode: "off" | "server | "client" }
      -    metaData
      +    meta
      }) => {
          ...
      },
      
  • 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

3.41.0

Minor Changes

3.40.0

Minor Changes

3.39.6

Patch Changes

3.39.5

Patch Changes

3.39.4

Patch Changes

3.39.3

Patch Changes

3.39.2

Patch Changes

3.39.1

Patch Changes

3.39.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,
            },
          ],
        },
      ],
    }
    

3.38.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,
            },
          ],
        },
      ],
    }
    

3.37.0

Minor Changes

  • Updated dataProvider types with Required utility to mark getMany, createMany, updateMany and deleteMany as implemented.

3.36.0

Minor Changes

  • #2688 508045ac30 Thanks @aliemir! - Updated dataProvider types with Required utility to mark getMany, createMany, updateMany and deleteMany as implemented.

3.35.0

Minor Changes

  • Added metaData support for the /me request

    const strapiAuthHelper = AuthHelper(API_URL + "/api");
    
    strapiAuthHelper.me("token", {
        metaData: {
            populate: ["role"],
        },
    });
    

3.34.0

Minor Changes

  • #2496 7e1538512e Thanks @albcunha! - Added metaData support for the /me request

    const strapiAuthHelper = AuthHelper(API_URL + "/api");
    
    strapiAuthHelper.me("token", {
        metaData: {
            populate: ["role"],
        },
    });
    

3.33.0

Minor Changes

  • Fixed payload data in delete on nestjsx data provider custom method.

3.32.0

Minor Changes

3.31.0

Minor Changes

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

3.30.0

Minor Changes

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

3.29.0

Minor Changes

  • Add React@18 support 🚀

3.28.0

Minor Changes

3.27.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.

3.26.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.

3.25.10

Patch Changes

  • Add pageSize support for getMany - #2077

  • Updated dependencies []:

    • @pankod/refine-core@3.42.0

3.25.9

Patch Changes

3.25.8

Patch Changes

  • Updated pagination parameters default values and added hasPagination property to getList method of the data providers.

    Implementation

    Updated the getList method accordingly to the changes in the useTable and useList of @pankod/refine-core. hasPagination is used to disable pagination (defaults to true)

    Use Cases

    For some resources, there might be no support for pagination or users might want to see all of the data without any pagination, prior to these changes this was not supported in refine data providers.

  • Fix pagination issue on users endpoint - #2028

  • Updated dependencies []:

    • @pankod/refine-core@3.36.0

3.25.7

Patch Changes

  • #2050 635cfe9fdb Thanks @ozkalai! - Updated pagination parameters default values and added hasPagination property to getList method of the data providers.

    Implementation

    Updated the getList method accordingly to the changes in the useTable and useList of @pankod/refine-core. hasPagination is used to disable pagination (defaults to true)

    Use Cases

    For some resources, there might be no support for pagination or users might want to see all of the data without any pagination, prior to these changes this was not supported in refine data providers.

3.25.6

Patch Changes

  • Added populate, fields, locale and publicationState support for @pankod/refine-strapi-v4 data provider's getMany function

3.25.5

Patch Changes

  • #1958 42100b631a Thanks @omeraplak! - Added populate, fields, locale and publicationState support for @pankod/refine-strapi-v4 data provider's getMany function

3.25.4

Patch Changes

  • Updated axios version (0.21.4 to 0.26.1). In this version, the way of sending headers has changed as follows.

    // old v0.21.4
    axiosInstance.defaults.headers = { Authorization: `Bearer ${data.jwt}` };
    
    // new v0.26.1
    axiosInstance.defaults.headers.common["Authorization"] = `Bearer ${data.jwt}`;
    
  • Updated dependencies []:

    • @pankod/refine-core@3.29.0

3.25.3

Patch Changes

  • Updated axios version (0.21.4 to 0.26.1). In this version, the way of sending headers has changed as follows.

    // old v0.21.4
    axiosInstance.defaults.headers = { Authorization: `Bearer ${data.jwt}` };
    
    // new v0.26.1
    axiosInstance.defaults.headers.common["Authorization"] = `Bearer ${data.jwt}`;
    
  • Updated dependencies []:

    • @pankod/refine-core@3.28.0

3.25.2

Patch Changes

  • Updated axios version (0.21.4 to 0.26.1). In this version, the way of sending headers has changed as follows.

    // old v0.21.4
    axiosInstance.defaults.headers = { Authorization: `Bearer ${data.jwt}` };
    
    // new v0.26.1
    axiosInstance.defaults.headers.common["Authorization"] = `Bearer ${data.jwt}`;
    
  • Updated dependencies []:

    • @pankod/refine-core@3.27.0

3.25.1

Patch Changes

  • #1899 fbfea418a0 Thanks @yildirayunlu! - Updated axios version (0.21.4 to 0.26.1). In this version, the way of sending headers has changed as follows.

    // old v0.21.4
    axiosInstance.defaults.headers = { Authorization: `Bearer ${data.jwt}` };
    
    // new v0.26.1
    axiosInstance.defaults.headers.common["Authorization"] = `Bearer ${data.jwt}`;
    
  • Updated dependencies [2ba2a96fd2]:

    • @pankod/refine-core@3.26.0

3.22.2

Patch Changes

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