OptionalassumeThe cache that Apollo Client should use to store query results locally. The recommended cache is InMemoryCache, which is provided by the @apollo/client package.
For more information, see Configuring the cache.
OptionalclientOptionaldataDetermines if data masking is enabled for the client.
OptionaldefaultOptionaldefaultProvide this object to set application-wide default values for options you can provide to the watchQuery, query, and mutate functions. See below for an example object.
See this example object.
OptionaldevtoolsConfiguration used by the Apollo Client Devtools extension for this client.
OptionaldocumentOptionalenhancedOptional ExperimentalexperimentsAllows passing in "experiments", experimental features that might one day become part of Apollo Client's core functionality. Keep in mind that these features might change the core of Apollo Client. Do not pass in experiments that are not provided by Apollo.
OptionalincrementalDetermines the strategy used to parse incremental chunks from @defer
queries.
An ApolloLink instance to serve as Apollo Client's network layer. For more information, see Advanced HTTP networking.
OptionallocalOptionalqueryIf false, Apollo Client sends every created query to the server, even if a completely identical query (identical in terms of query string, variable values, and operationName) is already in flight.
OptionalssrThe time interval (in milliseconds) before Apollo Client force-fetches queries after a server-side render.
OptionalssrWhen using Apollo Client for server-side rendering, set this to true so that the getDataFromTree function can work effectively.
If
true, Apollo Client will assume results read from the cache are never mutated by application code, which enables substantial performance optimizations.