[RFC] create a FAQ section

[morrys]

How the react-relay-offline version is managed

• Patch release ..1 : backward compatible & bug fixes
• Minor release *.1.0 : backward compatible or small breaking change & new small improvements
• Major release 1.0.0 : breaking change | new important improvements

I recommend using ~ and not ^ in the react-relay-offline version and follow this repository for any update

What are the main dependencies of react-relay-offline?

react-relay-offline uses these libraries to manage the offline:

• wora/cache-persist
  • manages the status and its persistence in the storage
• wora/netinfo
  • manages the network status detection
• wora/offline-first
  • manages all the offline workflow with queuing requests
• wora/relay-store
  • extension of the Store and Recordsource objects with the integration of wora/cache-persist + TTL
• wora/relay-offline
  • extension of the relay environment with the integration of the wora/offline-first library

I recommend following the repository wora for any details.

How should I manage the creation of a new node?

When a new node is created by mutation the id must be generated in the browser to use it in the optimistic response.
This ensures the consistency of the store.

offline needs optimistic updater?

the offline needs to have one of the following options:

• only optimisticResponse
• optimisticResponse + updater
• configs
• optimisticUpdate