There exists, in legend an Online Monitor component, that would hypothetically listen for changes in online activity, and if the internet drops out, or becomes too poor, offline requests and queue them for later.
I'm p-sure I had this working but maybe not. Either way, it needs to be implemented across web and native, even if it's just polling every few seconds, and update the state as well as some other variable to tell Apollo not to try the mutation.
Stages of this include:
~Add network listener to listen for changes, and toggle isOnline accordingly~
~Add some simple component to display to user that they're offline with hook into isOnline~
Tell Apollo not to run a mutation if offline (this may not be necessary, as apollo might just be able to detect if it can on it's own), and push the mutation onto a queue to try later.
When Online status returns, try purging the queue of offlined mutations
Add some common-sense checks in places to prevent mutations when user is clearly offline (offline state for buttons?)
There exists, in legend an Online Monitor component, that would hypothetically listen for changes in online activity, and if the internet drops out, or becomes too poor, offline requests and queue them for later.
I'm p-sure I had this working but maybe not. Either way, it needs to be implemented across web and native, even if it's just polling every few seconds, and update the state as well as some other variable to tell Apollo not to try the mutation.
Stages of this include:
isOnlineaccordingly~isOnline~