@wora/apollo-offline
v2.5.1
Published
@wora Apollo Offline Capabilities
Downloads
797
Maintainers
Readme
@wora/apollo-offline
Installation
Install @wora/apollo-offline using yarn or npm:
yarn add apollo-client @wora/apollo-offline
Installation React Web
Install @wora/apollo-offline using yarn or npm:
yarn add apollo-client @wora/apollo-offline
Installation React Native
Install react-relay and react-relay-offline using yarn or npm:
yarn add @react-native-community/netinfo @wora/apollo-offline
You then need to link the native parts of the library for the platforms you are using. The easiest way to link the library is using the CLI tool by running this command from the root of your project:
react-native link @react-native-community/netinfo
Main Additional Features
automatic persistence and rehydration of the store (AsyncStorage, localStorage, IndexedDB) with @wora/apollo-cache
configuration of persistence
custom storage
different key prefix (multi user)
serialization: JSON or none
management and utilities for network detection with @wora/netinfo
automatic use of the polity cache_first when the application is offline
offline mutation management
update and publication of the mutation changes in the store
persistence of mutation information performed
automatic execution of mutations persisted when the application returns online
configurability of the offline mutation execution link
onComplete callback of the mutation performed successfully
onDiscard callback of the failed mutation
React Web Example
The offline-examples repository contains an integration of @wora/apollo-offline. To try it out
Apollo Client
import { ApolloClient } from "@wora/apollo-offline";
import { HttpLink } from "apollo-link-http";
import ApolloCache from '@wora/apollo-cache';
const httpLink = new HttpLink({
uri: "http://localhost:4000/graphql"
});
const client = new ApolloClient({
link: httpLink,
cache: new ApolloCache({
dataIdFromObject: o => o.id
})
});
// await before instantiating Query, else queries might run before the cache is persisted
// or use apollo-offline useQuery
await client.hydrate(): Promise<boolean>
Apollo Client new functions
public hydrate(): Promise<boolean>
public setOfflineOptions(offlineOptions: OfflineOptions<Payload> = {}): void;
public getStoreOffline(): OfflineFirst<Payload>
public isRehydrated(): boolean
public isOnline(): boolean
public mutateOffline<T>(mutationOptions: MutationOptions): Promise<FetchResult<T>>
Apollo Client with Offline Options
import { ApolloClient } from "@wora/apollo-offline";
import { HttpLink } from "apollo-link-http";
import ApolloCache from '@wora/apollo-cache';
const httpLink = new HttpLink({
uri: "http://localhost:4000/graphql"
});
const httpLinkOffline = new HttpLink({
uri: "http://localhost:4000/graphql"
});
const client = new ApolloClient({
link: httpLink,
cache: new ApolloCache({
dataIdFromObject: o => o.id
})
});
client.setOfflineOptions({
manualExecution: false, //optional
link: httpLinkOffline, //optional
start: async (mutations) => { //optional
console.log("start offline", mutations)
return mutations;
},
finish: async (mutations, error) => { //optional
console.log("finish offline", error, mutations)
},
onExecute: async (mutation) => { //optional
console.log("onExecute offline", mutation)
return mutation;
},
onComplete: async (options ) => { //optional
console.log("onComplete offline", options)
return true;
},
onDiscard: async ( options ) => { //optional
console.log("onDiscard offline", options)
return true;
},
onPublish: async (offlinePayload) => { //optional
console.log("offlinePayload", offlinePayload)
return offlinePayload
}
};)
// await before instantiating Query, else queries might run before the cache is persisted, TODO ApolloProviderOffline
await client.hydrate(): Promise<boolean>
manualExecution: if set to true, mutations in the queue are no longer performed automatically as soon as you go back online. invoke manually:
client.getStoreOffline().process();
link: it is possible to configure a different link for the execution of mutations in the queue
start: function that is called once the request queue has been started.
finish: function that is called once the request queue has been processed.
onExecute: function that is called before the request is sent to the network.
onPublish: function that is called before saving the mutation in the store
onComplete: function that is called once the request has been successfully completed. Only if the function returns the value true, the request is deleted from the queue.
onDiscard: function that is called when the request returns an error. Only if the function returns the value true, the mutation is deleted from the queue
IndexedDB
localStorage is used as the default react web persistence, while AsyncStorage is used for react-native.
To use persistence via IndexedDB:
import { HttpLink } from "apollo-link-http";
import ApolloClientIDB from '@wora/apollo-offline/lib/ApolloClientIDB';
import { HttpLink } from "apollo-link-http";
const httpLink = new HttpLink({
uri: "http://localhost:4000/graphql"
});
const cacheOptions = {
dataIdFromObject: o => o.id
}
const client = ApolloClientIDB.create({ link: httpLink }, {
cacheOptions
});
ApolloClientIDB.create function
public static create(
config: ApolloClientIDBOptions,
options: {
cacheOptions?: InMemoryCacheConfig;
persistOptions?: CacheOptions;
offlineStoreOptions?: CacheOptions;
idbOptions?: {
name?: string;
onUpgrade?: IOnUpgrade;
version?: number;
};
},
): ApolloClientOffline
ApolloClient with PersistOfflineOptions
import { ApolloClient } from "@wora/apollo-offline";
import { HttpLink } from "apollo-link-http";
import ApolloCache from '@wora/apollo-cache';
const httpLink = new HttpLink({
uri: "http://localhost:4000/graphql"
});
const httpLinkOffline = new HttpLink({
uri: "http://localhost:4000/graphql"
});
const persistOfflineOptions: CacheOptions = {
prefix: "app-user1"
};
const client = new ApolloClient({
link: httpLink,
cache: new ApolloCache({
dataIdFromObject: o => o.id
})
}, persistOfflineOptions);
useQuery
the useQuery provides native management of client hydration.
If the client is not hydrated, the hydration request is made and the application will have the same behavior as when it is offline and will be rendered with only the information present in the store if present.
When the hydration promise is resolved, the useQuery is re-rendered.
import useQuery from '@wora/apollo-offline/lib/react/useQuery';