You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Install @refinedev/hasura
Set up Hasura v3 with a blogs query and the blogsAggregate field.
Use the useList hook in your Refine app to query the blogs resource.
Run the app, and you should see the issue where the query fails or doesn't work as expected due to the mismatch in naming conventions (blogsAggregate vs blogs_aggregate).
Expected behavior
The useList hook should be able to properly query the blogs resource using the correct query structure.
The aggregation should be handled with the blogs_aggregate field as expected by the Refine.dev Hasura integration.
The query should successfully return the list of blogs with the correct count from the aggregation, without errors related to the field naming convention.
Actual Behavior:
The query fails or returns incorrect results because useList expects the blogs_aggregate field, but Hasura v3 uses blogsAggregate.
The mismatch in field names causes the query to not function as expected.
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: