Feature request: Caching

[good-idea]

Is implementing a cache within the scope of this project?

[f]

Query caching or object caching?

…

________________________________ From: Joseph Thomas <notifications@github.com> Sent: Wednesday, October 24, 2018 9:06:28 AM To: f/graphql.js Cc: Subscribed Subject: [f/graphql.js] Feature request: Caching (#32) Is implementing a cache within the scope of this project? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#32>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAL_fT5mtFSIpTCvoW5gHAQhVNdWvySwks5uoANkgaJpZM4X3ML5>.

[good-idea]

Object caching would be ideal, but either would be nice. I suppose caching the query (if you mean caching the results of a particular query) could be as simple as generating a hash from the query string to use as a key. I don't know much about GraphQL response metadata though, so I don't know if this would mess up any timestamps.

Just wondering if you had any plans!

[revskill10]

Without caching, i can't use this library.

[frederikhors]

It would be amazing to have something like Apollo caching mechanism.

[suryacaprice]

@f I need caching too . Is there any updates coming for this?

[f]

What kind of caching do you people need? Can you specify the need?

[dougogodinho]

What kind of caching do you people need? Can you specify the need?

data cache... to avoid round trips