30 KiB
@refinedev/hasura
6.4.12
Patch Changes
- #5425
190af9fce2
Thanks @aliemir! - Updated@refinedev/core
peer dependencies to latest (^4.46.1
)
6.4.11
Patch Changes
- #5330
7c8827b43d
Thanks @BatuhanW! - chore: upgrade nock library version to ^13.4.0
6.4.10
Patch Changes
-
#5040
ca57048580a
Thanks @IkumaTadokoro! - fix: issue with #4972When using the Hasura provider with the 'graphql-default' naming convention, snake-case graphql operators (e.g. _is_null) were not converted to the correct case, causing query errors. This problem is now fixed. Now the snake_case operator is converted according to the given naming convention (e.g. hasura-default: _is_null, graphql-default: _isNull).
6.4.9
Patch Changes
-
#5040
ca57048580a
Thanks @IkumaTadokoro! - fix: issue with #4972When using the Hasura provider with the 'graphql-default' naming convention, snake-case graphql operators (e.g. _is_null) were not converted to the correct case, causing query errors. This problem is now fixed. Now the snake_case operator is converted according to the given naming convention (e.g. hasura-default: _is_null, graphql-default: _isNull).
6.4.8
Patch Changes
-
#5022
80513a4e42f
Thanks @BatuhanW! - chore: update README.md- fix grammar errors.
- make all README.md files consistent.
- add code example code snippets.
6.4.7
Patch Changes
-
#5022
80513a4e42f
Thanks @BatuhanW! - chore: update README.md- fix grammar errors.
- make all README.md files consistent.
- add code example code snippets.
6.4.6
Patch Changes
- #4951
04837c62077
Thanks @aliemir! - - Update build configuration foresbuild
to use the shared plugins.- Fix the lodash replacement plugin to skip redundant files.
6.4.5
Patch Changes
- #4951
04837c62077
Thanks @aliemir! - - Update build configuration foresbuild
to use the shared plugins.- Fix the lodash replacement plugin to skip redundant files.
6.4.4
Patch Changes
-
#4584
6305f41d2a6
Thanks @IkumaTadokoro! - fix: issue with #4574We had a problem when using Hasura Provider with grapqhql-convention where it causes could not retrieve some response issue to happen, now it's fixed.
6.4.3
Patch Changes
-
#4584
6305f41d2a6
Thanks @IkumaTadokoro! - fix: issue with #4574We had a problem when using Hasura Provider with grapqhql-convention where it causes could not retrieve some response issue to happen, now it's fixed.
6.4.2
Patch Changes
- #4285
b5cd3328504
Thanks @alicanerdurmaz! - fixed: A bug that prevented data providers from being swizzled.
6.4.1
Patch Changes
- #4285
b5cd3328504
Thanks @alicanerdurmaz! - fixed: A bug that prevented data providers from being swizzled.
6.4.0
Minor Changes
-
#4174
d040da9a428
Thanks @alicanerdurmaz! - feat: added refine.config.js to support swizzling. Now with swizzle support, you can easily customize hasura data provider for your needs.feat: tests added for utility functions.
chore: utility functions have been moved to their own files.
chore:
genereteUseListSubscription
is deprecated and has been renamed togenerateListSubscriptionHook
. chore:genereteUseManySubscription
is deprecated and has been renamed togenerateUseManySubscription
. chore:genereteUseOneSubscription
is deprecated and has been renamed togenerateUseOneSubscription
.
Patch Changes
-
#4179
fd808368a36
Thanks @austin047! - fix: change enum from lowercase to UPPERCASE in api request for hasura camelCase naming conventionFrom the hasura documentation here, for the graphql-default naming convention, the naming convention for enums is upper-cased. Currently the request are being made with the lowercase enum and not uppercase.
The change mainly affects
sort
, desc gets changed to DESC and asc gets changed to ASC. the request from the refine client interface maintains the underscore and convertion to uppercase is only done at the API request layer.
6.3.0
Minor Changes
-
#4174
d040da9a428
Thanks @alicanerdurmaz! - feat: added refine.config.js to support swizzling. Now with swizzle support, you can easily customize hasura data provider for your needs.feat: tests added for utility functions.
chore: utility functions have been moved to their own files.
chore:
genereteUseListSubscription
is deprecated and has been renamed togenerateListSubscriptionHook
. chore:genereteUseManySubscription
is deprecated and has been renamed togenerateUseManySubscription
. chore:genereteUseOneSubscription
is deprecated and has been renamed togenerateUseOneSubscription
.
Patch Changes
-
#4179
fd808368a36
Thanks @austin047! - fix: change enum from lowercase to UPPERCASE in api request for hasura camelCase naming conventionFrom the hasura documentation here, for the graphql-default naming convention, the naming convention for enums is upper-cased. Currently the request are being made with the lowercase enum and not uppercase.
The change mainly affects
sort
, desc gets changed to DESC and asc gets changed to ASC. the request from the refine client interface maintains the underscore and convertion to uppercase is only done at the API request layer.
6.2.0
Minor Changes
-
#4144
06bdf9e4837
Thanks @mattbho! - feat: support camelCase graphql naming convention for HasuraPreviously, our Hasura data provider only supported snake-case naming conventions for operations and type names.
Hasura recently released a setting allowing for camelCase support.
The following changes do the Hasura data provider now support the new setting.
All methods for the Hasura Data provider now support the camelCase
graphql-default
naming convention.The data provider now accepts a
namingConvention
field in the options payload.Ex:
const gqlDataProvider = dataProvider(client, {namingConvention: "graphql-default"});
If the
graphql-default
naming convention is provided, all field names and variables will be camel cased. Type names will be PascalCased.
6.1.0
Minor Changes
-
#4144
06bdf9e4837
Thanks @mattbho! - feat: support camelCase graphql naming convention for HasuraPreviously, our Hasura data provider only supported snake-case naming conventions for operations and type names.
Hasura recently released a setting allowing for camelCase support.
The following changes do the Hasura data provider now support the new setting.
All methods for the Hasura Data provider now support the camelCase
graphql-default
naming convention.The data provider now accepts a
namingConvention
field in the options payload.Ex:
const gqlDataProvider = dataProvider(client, {namingConvention: "graphql-default"});
If the
graphql-default
naming convention is provided, all field names and variables will be camel cased. Type names will be PascalCased.
6.0.1
Patch Changes
- #4030
1b019280252
Thanks @yildirayunlu! - Upgradedgraphql-request
dependency4.x
to5.x
.
6.0.0
Major Changes
- #4030
1b019280252
Thanks @yildirayunlu! - Upgradedgraphql-request
dependency4.x
to5.x
.
5.1.2
Patch Changes
- #4001
e9807e60510
Thanks @BatuhanW! - fix: add missing possible id types to hasura data provider
5.1.1
Patch Changes
- #4001
e9807e60510
Thanks @BatuhanW! - fix: add missing possible id types to hasura data provider
5.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
4.21.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.20.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.19.0
Minor Changes
- #3752
426386ca250
Thanks @zulianrizki! - Allow custom ID types withidType
property when initializing the data provider instance.idType
can either beInt
,uuid
or a function returning the type by resource name.
4.18.0
Minor Changes
- #3752
426386ca250
Thanks @zulianrizki! - Allow custom ID types withidType
property when initializing the data provider instance.idType
can either beInt
,uuid
or a function returning the type by resource name.
4.17.3
Patch Changes
- #3275
aaa499548cd
Thanks @aliemir! -contains
,ncontains
,containss
andncontainss
filters were passing the value without wrapping it to%
characters. This caused the filters to not work as expected. Added a case to the filter value handler to wrap the value with%
characters. (Resolves #3245)
4.17.2
Patch Changes
- #3275
aaa499548cd
Thanks @aliemir! -contains
,ncontains
,containss
andncontainss
filters were passing the value without wrapping it to%
characters. This caused the filters to not work as expected. Added a case to the filter value handler to wrap the value with%
characters. (Resolves #3245)
4.17.1
Patch Changes
- #3275
aaa499548cd
Thanks @aliemir! -contains
,ncontains
,containss
andncontainss
filters were passing the value without wrapping it to%
characters. This caused the filters to not work as expected. Added a case to the filter value handler to wrap the value with%
characters. (Resolves #3245)
4.17.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, }, ], }, ], }
4.16.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, }, ], }, ], }
4.15.2
Patch Changes
- Added nested property filter support for
or
filters.
4.15.1
Patch Changes
- #2743
8aecb59d7b
Thanks @aliemir! - Added nested property filter support foror
filters.
4.15.0
Minor Changes
- Added missing implementations for
nnull
,startswith
,startswiths
,nstartswith
,nstartswiths
,endswith
,endswiths
,nendswith
andnendswiths
filters by_similar
,_nsimilar
,_regex
and_iregex
filters from Hasura.
4.14.0
Minor Changes
- #2728
585ba350f8
Thanks @aliemir! - Added missing implementations fornnull
,startswith
,startswiths
,nstartswith
,nstartswiths
,endswith
,endswiths
,nendswith
andnendswiths
filters by_similar
,_nsimilar
,_regex
and_iregex
filters from Hasura.
4.13.0
Minor Changes
- Updated
dataProvider
types withRequired
utility to markgetMany
,createMany
,updateMany
anddeleteMany
as implemented.
4.12.0
Minor Changes
- #2688
508045ac30
Thanks @aliemir! - UpdateddataProvider
types withRequired
utility to markgetMany
,createMany
,updateMany
anddeleteMany
as implemented.
4.11.2
Patch Changes
- Added nested sorting feature 💥
- Added new CRUD Filter Operators with undefined
4.11.1
Patch Changes
- #2427
b21908e872
Thanks @geoffatsource! - Added nested sorting feature 💥
- #2456
f20a0ed621
Thanks @workatease! - Added new CRUD Filter Operators with undefined
4.11.0
Minor Changes
- Update type declaration generation with
tsc
instead oftsup
for better navigation throughout projects source code.
4.10.0
Minor Changes
- #2440
0150dcd070
Thanks @aliemir! - Update type declaration generation withtsc
instead oftsup
for better navigation throughout projects source code.
4.9.4
Patch Changes
-
lodash
moved to "dependencies" for CommonJS builds
4.9.3
Patch Changes
-
lodash
moved to "dependencies" for CommonJS builds
4.9.2
Patch Changes
-
lodash
moved to "dependencies" for CommonJS builds
4.9.1
Patch Changes
- #2366
de87f13dad
Thanks @omeraplak! - -lodash
moved to "dependencies" for CommonJS builds
4.9.0
Minor Changes
-
Add nested filter support to
Hasura
data provider.Example usage:
filters: [ { field: "category.id", operator: "eq", value: "8332c138-3231-406d-9655-1328ded9d5f2", }, ],
4.8.0
Minor Changes
-
#2347
628324d950
Thanks @ozkalai! - Add nested filter support toHasura
data provider.Example usage:
filters: [ { field: "category.id", operator: "eq", value: "8332c138-3231-406d-9655-1328ded9d5f2", }, ],
4.7.0
Minor Changes
- Add React@18 support 🚀
4.6.0
Minor Changes
- #1718
b38620d842
Thanks @omeraplak! - Add React@18 support 🚀
4.5.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.
4.4.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.
4.3.2
Patch Changes
- Add support for multiple operators on the same field - #2154
4.3.1
Patch Changes
- #2157
6f5ec7c32f
Thanks @smparekh! - Add support for multiple operators on the same field - #2154
4.3.0
Minor Changes
-
@pankod/refine-core
- Added extra params to
useSubscription
anduseResourceSubscription
useOne
,useMany
anduseList
passed extra params to own subscription hook.
@pankod/refine-hasura
- Added
liveProvider
.
To see an example of how to use it, check out
here
.@pankod/refine-nhost
- Added
liveProvider
.
To see an example of how to use it, check out
here
.@pankod/refine-graphql
- Added
liveProvider
.
- Added extra params to
Patch Changes
- Updated dependencies []:
- @pankod/refine-core@3.42.0
4.2.0
Minor Changes
-
#2120
2aa7aace52
Thanks @salihozdemir! - ###@pankod/refine-core
- Added extra params to
useSubscription
anduseResourceSubscription
useOne
,useMany
anduseList
passed extra params to own subscription hook.
@pankod/refine-hasura
- Added
liveProvider
.
To see an example of how to use it, check out
here
.@pankod/refine-nhost
- Added
liveProvider
.
To see an example of how to use it, check out
here
.@pankod/refine-graphql
- Added
liveProvider
.
- Added extra params to
Patch Changes
- Updated dependencies [
2aa7aace52
]:- @pankod/refine-core@3.41.0
4.1.0
Minor Changes
-
Upgraded
grapql-request
version in graphql data provider packages.Now the
graphql-request
andqql-query-builder
packages are exported in these packages.- import dataProvider from "@pankod/refine-strapi-graphql"; - import { GraphQLClient } from "graphql-request"; - import * as qqlQueryBuilder from "gql-query-builder"; + import dataProvider, { GraphQLClient, qqlQueryBuilder } from "@pankod/refine-strapi-graphql";
Patch Changes
- Updated dependencies []:
- @pankod/refine-core@3.38.2
4.0.0
Major Changes
-
#2113
c2fb7ac0e9
Thanks @omeraplak! - Upgradedgrapql-request
version in graphql data provider packages.Now the
graphql-request
andqql-query-builder
packages are exported in these packages.- import dataProvider from "@pankod/refine-strapi-graphql"; - import { GraphQLClient } from "graphql-request"; - import * as qqlQueryBuilder from "gql-query-builder"; + import dataProvider, { GraphQLClient, qqlQueryBuilder } from "@pankod/refine-strapi-graphql";
Patch Changes
- Updated dependencies [
ee8e8bbd6c
]:- @pankod/refine-core@3.38.1
3.25.4
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.3
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.2
Patch Changes
- Added
graphql-request
dependency to peerDependencies
3.25.1
Patch Changes
- #1930
04572f5085
Thanks @omeraplak! - Addedgraphql-request
dependency to peerDependencies
3.22.2
Patch Changes
- Updated dependencies [
2deb19babf
]:- @pankod/refine-core@3.23.2