Persisted Query Hashed don't match with Fragments #3648
Unanswered
alexnsorensen
asked this question in
Q&A
Replies: 1 comment 3 replies
-
|
I would say that the issue is the difference in how your PO aggregator shifts the order of the query π
I haven't really seen that before, the GraphQL Code Generator client-preset attaches a |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all
I have a weird issue happening, when using URQL and persisted queries with fragments, and I want to make sure I'm using it correctly.
If I follow the instructions here:
https://commerce.nearform.com/open-source/urql/docs/basics/core/#graphql-tags
Then I have my code like this (using the demo):
import { gql } from '@urql/core';
When I run my codegen to generate hashes, I might get this
c727a2c5(using a fake hash for demonstration), then when urql runs, it would send this hash701e6878, and what's caused this seems to be one (or more) of these:so Codgen is producing:
and urql is sending this (once it sends the incorrect hash it sends the full query):
But if I do this:
Then the hashes are correct and match, and the persisted query is used.
Am I not using this correctly?
Beta Was this translation helpful? Give feedback.
All reactions