The use case of graphQL caches is to cases where the data consistency is not that important (social media, etc.). But that is not the case for blockchains.
Proposal
The following is done:
The async_graph::prefix is removed in 3 instances.
To, the #[Object] entries, a cache_control(no_cache) is added.
It has not been added to the examples which may be needed.
Test Plan
This may remove some errors occurring in the CI, though at the present time we cannot point out CI failures to GraphQL errors.
Motivation
The use case of graphQL caches is to cases where the data consistency is not that important (social media, etc.). But that is not the case for blockchains.
Proposal
The following is done:
async_graph::prefix is removed in 3 instances.#[Object]entries, acache_control(no_cache)is added.exampleswhich may be needed.Test Plan
This may remove some errors occurring in the CI, though at the present time we cannot point out CI failures to GraphQL errors.
Release Plan
Not relevant.
Links