graphql.js Feature request: Caching

Is implementing a cache within the scope of this project?

Oct 24 '18 06:10 good-idea

Query caching or object caching?

From: Joseph Thomas [email protected] 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 GitHubhttps://github.com/f/graphql.js/issues/32, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAL_fT5mtFSIpTCvoW5gHAQhVNdWvySwks5uoANkgaJpZM4X3ML5.

Oct 24 '18 06:10 f

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!

Oct 24 '18 06:10 good-idea

Without caching, i can't use this library.