Does Gatsby cache graphQL queries by Operation Name?

Question

I've read this question which is more general: What is the point of naming queries and mutations in GraphQL?. The top answer indicates that Operation Name is meaningless, but a particular implementation can give it meaning.

My team lead and I are working refactoring some data into new static queries which might be repeated many times across the app. We think that naming the queries will allow Gatsby to cache the results, which would be great. But I can't actually find anything saying that in the Gatsby docs and now neither of us know where that idea came from. All I have found is this rather unhelpful description. So, does giving these queries names actually help us here, or is it pointless?

LekoArts · Accepted Answer · 2022-12-01 08:07:33Z

0

The operation name is irrelevant as Gatsby generates its own unique name internally (you can add it so that it makes it into that generation). If you e.g. create a custom hook with a useStaticQuery and then use that throughout your app, it'll only use that (so it's "cached").

answered Dec 1, 2022 at 8:07

LekoArts

1,5691 gold badge9 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Does Gatsby cache graphQL queries by Operation Name?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related