Skip to content

[BUG] Hasura data provider not using meta.gqlVariables #6775

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

Open
thanaParis opened this issue May 7, 2025 · 0 comments · May be fixed by #6780, #6781 or #6782
Open

[BUG] Hasura data provider not using meta.gqlVariables #6775

thanaParis opened this issue May 7, 2025 · 0 comments · May be fixed by #6780, #6781 or #6782
Labels
bug Something isn't working

Comments

@thanaParis
Copy link

Describe the bug

When using the Hasura data provider, meta.gqlVariables is used for getOne, getMany, and getList, but not for any other queries. This prevents, for example, useForm's mutationMeta.gqlVariables from applying.

Steps To Reproduce

  1. Add gqlVariables object with variables defined inside to the meta field of any hook which uses create, update, or delete, alongside a gql operation (meta.gqlQuery or meta.gqlMutation)
  2. Expectation: gqlVariables are passed to the gql operation, reality: they usually are not

Expected behavior

when using a meta gql operation such as gqlQuery or gqlMutation, meta.gqlVariables should always be passed to the operation.

Packages

  • @refinedev/hasura

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment