Graphql caching mechanism preventing double fetching?

[axhamre]

Is there any caching mechanism in Gatsby that prevents the same object queried in different parts of the application to be fetched multiple times? Something similar to how apollo-client works.

If so, what's the prerequisites for this to work? E.g. always include ID etc.

[gatsbot[bot]]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

[gatsbot[bot]]

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!

[KyleAMathews]

Hey, sorry we missed your question.

To answer it, there isn't right now but it's something we'd like to add. React Static does something along these lines where it identifies common data between queries and moves those into "shared" data chunks and only loads those once. We should be able to do something like this fairly cheaply with GraphQL. /cc @freiksenet @stefanprobst

[freiksenet]

Fetching node in Gatsby is already made through a cache, there isn't really a need to do additional cache on top of that on GraphQL level. Do you have any use case where this is important @axhamre?

[freiksenet]

Ah right, this is about using common chunks on client side. Disregard my comment above.