-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with useList integration with Hasura v3 #6627
Comments
Hey @socheatleang, sorry for the issue. You can pass provider options to change the naming convention. import dataProvider from "@refinedev/hasura";
const client = /*...*/
const hasuraDataProvider = dataProvider(client, { namingConvention: "graphql-default" });
return (
<Refine
dataProvider={hasuraDataProvider}
>
/*...*/
</Refine>
); By default it's |
Thanks to help me on this. @aliemir It's pretty work fine. But it seems like not 100% work. Now i am having this.
Do you have any input about this? |
Hey @socheatleang could you provide more details? It looks like data provider can't find |
When will you update the naming convention to Hasura v3? as described above? Stuck here for now |
Describe the bug
Hello Refine.dev Team,
I am experiencing an issue where the useList hook does not work properly with Hasura v3. Specifically, the query structure provided by Hasura v3 differs from the expected structure for the Refine.dev Hasura integration.
Just question, would the hasura sdk from refinedev has up to date with the Hasura V3 yet?
Steps To Reproduce
Expected behavior
Actual Behavior:
Packages
Additional Context
Expected Query for @refinedev/hasura:
Hasura V3 Query:
The text was updated successfully, but these errors were encountered: