20 KiB
@refinedev/nestjsx-crud
5.0.1
Patch Changes
- #5425
190af9fce2
Thanks @aliemir! - Updated@refinedev/core
peer dependencies to latest (^4.46.1
)
5.0.0
Major Changes
- #5330
7c8827b43d
Thanks @BatuhanW! - feat: upgrade axios dependency to ^1.6.2
Patch Changes
-
#5300
1bc21de08b
Thanks @ksankeerth! - fix: missing files in package nestjsx-crudThere was an issue with nestjsx-crud package due to missing files(transformErrorMessages.ts and transformHttpError.ts)
4.5.5
Patch Changes
- #5054
6ab41f88343
Thanks @MahirMahdi! - NowuseCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.
4.5.4
Patch Changes
- #5054
6ab41f88343
Thanks @MahirMahdi! - NowuseCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.
4.5.3
Patch Changes
- #5054
6ab41f88343
Thanks @MahirMahdi! - NowuseCustomMutation
can modify headers for each individual call, without setting the default headers. Previously the default headers was included in all subsequent API calls.
4.5.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.
4.5.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.
4.5.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
, andcreateMany
methods will throw an error with the validation errors. This allows theuseForm
update the error state with the validation errors.
4.4.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
, andcreateMany
methods will throw an error with the validation errors. This allows theuseForm
update the error state with the validation errors.
4.3.4
Patch Changes
-
#4589
11241b16000
Thanks @yildirayunlu! - fix:getList
without pagination responseWithout the
limit
andoffset
parameters in thenestjsx/crud
library, the result is without paging. However, it was always expected to be paginated in the data provider. It now supports both situations.
4.3.3
Patch Changes
-
#4589
11241b16000
Thanks @yildirayunlu! - fix:getList
without pagination responseWithout the
limit
andoffset
parameters in thenestjsx/crud
library, the result is without paging. However, it was always expected to be paginated in the data provider. It now supports both situations.
4.3.2
Patch Changes
- #4285
b5cd3328504
Thanks @alicanerdurmaz! - fixed: A bug that prevented data providers from being swizzled.
4.3.1
Patch Changes
- #4285
b5cd3328504
Thanks @alicanerdurmaz! - fixed: A bug that prevented data providers from being swizzled.
4.3.0
Minor Changes
-
#4154
d6cb8f67d47
Thanks @alicanerdurmaz! - feat: added refine.config.js to support swizzling. Now with swizzle support, you can easily customize nextjs-crud data provider for your needs.feat: tests added for util functions.
chore: utility functions have been moved to their own files.
4.2.0
Minor Changes
-
#4154
d6cb8f67d47
Thanks @alicanerdurmaz! - feat: added refine.config.js to support swizzling. Now with swizzle support, you can easily customize nextjs-crud data provider for your needs.feat: tests added for util 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. Usemeta
prop instead.For backward compatibility, we still support
metaData
prop with refine v4.create: async ({ - metaData + meta }) => { ... },
-
sort
,hasPagination
, andmetaData
parameters ofgetList
method are now deprecated. Usesorters
,pagination
, andmeta
parameters instead.For backward compatibility, we still support
sort
,hasPagination
andmetaData
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.39.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
3.38.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
3.37.0
Minor Changes
-
#3429
92c3cac9a7f
Thanks @aliemir! - Added ability to passjoin
parameter throughmetaData
to queries.Example
useList({ metaData: { join: { select: ["id", "name"], field: "categories", }, }, }); useList({ metaData: { join: ["categories", ["id", "name"]], }, }); useList({ metaData: { join: [ ["categories", ["id", "name"]], { select: ["id", "label"], field: "tags", }, ], }, });
3.36.0
Minor Changes
-
#3429
92c3cac9a7f
Thanks @aliemir! - Added ability to passjoin
parameter throughmetaData
to queries.Example
useList({ metaData: { join: { select: ["id", "name"], field: "categories", }, }, }); useList({ metaData: { join: ["categories", ["id", "name"]], }, }); useList({ metaData: { join: [ ["categories", ["id", "name"]], { select: ["id", "label"], field: "tags", }, ], }, });
3.35.0
Minor Changes
-
Only
or
was supported as a conditional filter. Nowand
andor
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.34.0
Minor Changes
-
#2751
addff64c77
Thanks @yildirayunlu! - Onlyor
was supported as a conditional filter. Nowand
andor
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.33.0
Minor Changes
- Updated
dataProvider
types withRequired
utility to markgetMany
,createMany
,updateMany
anddeleteMany
as implemented.
3.32.0
Minor Changes
- #2688
508045ac30
Thanks @aliemir! - UpdateddataProvider
types withRequired
utility to markgetMany
,createMany
,updateMany
anddeleteMany
as implemented.
3.31.0
Minor Changes
- Fixed payload data in delete on nestjsx data provider custom method.
3.30.0
Minor Changes
- #2465
4d07f33993
Thanks @yildirayunlu! - Fixed payload data in delete on nestjsx data provider custom method.
3.29.0
Minor Changes
- Update type declaration generation with
tsc
instead oftsup
for better navigation throughout projects source code.
3.28.0
Minor Changes
- #2440
0150dcd070
Thanks @aliemir! - Update type declaration generation withtsc
instead oftsup
for better navigation throughout projects source code.
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 withpeerDependencies
+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 withpeerDependencies
+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.6
Patch Changes
-
Updated pagination parameters default values and added
hasPagination
property togetList
method of the data providers.Implementation
Updated the
getList
method accordingly to the changes in theuseTable
anduseList
of@pankod/refine-core
.hasPagination
is used to disable pagination (defaults totrue
)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.
-
Updated dependencies []:
- @pankod/refine-core@3.36.0
3.25.5
Patch Changes
-
#2050
635cfe9fdb
Thanks @ozkalai! - Updated pagination parameters default values and addedhasPagination
property togetList
method of the data providers.Implementation
Updated the
getList
method accordingly to the changes in theuseTable
anduseList
of@pankod/refine-core
.hasPagination
is used to disable pagination (defaults totrue
)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.
-
Updated dependencies [
ecde34a9b3
,635cfe9fdb
]:- @pankod/refine-core@3.35.0
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