You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I chose to use apollo-client for my Nodejs build scripts, basically retrieving the latest release from a Github repository and pushing new releases.
I like the architecture of the module where different concerns are separated and pluggable (network protocol, caching implementation, etc.), but I find it strange that caching is mandatory, while at the same time the policy option for no-cache is available. What about treating undefined apollo-clientcache option as if no-cache policy is on ?
import { ApolloClient } from 'apollo-client'
import { HttpLink } from 'apollo-link-http'
const client = new ApolloClient({
link: new HttpLink(),
cache: null // 👌will result in `no-cache` default options for both `query` and `watchQuery`.
})
The text was updated successfully, but these errors were encountered:
Hi, I chose to use
apollo-client
for my Nodejs build scripts, basically retrieving the latest release from a Github repository and pushing new releases.I like the architecture of the module where different concerns are separated and pluggable (network protocol, caching implementation, etc.), but I find it strange that caching is mandatory, while at the same time the policy option for
no-cache
is available. What about treating undefinedapollo-client
cache
option as ifno-cache
policy is on ?Current implementation:
Suggested implementation:
The text was updated successfully, but these errors were encountered: