Repository navigation
Use a query cache on the source block component #54
Description
Activity
As mentioned by Adam, it might be better to implement caching into the graphgist API:
For graph gists where the queries don't change then I think we could auto generate the results because the queries won't change. We could run the queries at build time and mock the results. I think that caching should be implemented into the graphgist API
Putting this issue on hold until we agree on a caching strategy.
The goal is to reduce the number of queries sent to Neo4j sandbox, aura and the GraphGists portal.
It should be possible to populate the cache from a query result generated at build time.
For instance, the GraphGists build could generate static files in the attachments directory that contain query results.
The source block component will then check if a file exists for a given couple page-query.
The source block component will use the cache when available. If not, it will switch to interactive mode and query the backend.
We could use a md5sum of the query as a unique key.
We can use https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage to save data.