Errors on Offline app #973
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is my proposal to #279. Any thoughts/suggestions to improve or make it different are welcome.
Thanks.
Description
When calling
_makeRequest
(or custom transport) set the onError function to store the event if we have the feature enabled.This means the feature can also be used on the custom transport if we use the passed
onError
.The queue is processed once we initialise it or on the
online
event or a custom one set withonlineEventName
.Processing the queue means call again
_sendProcessedPayload
with the stored error data.New options
allowOfflineStorage
- Booleanfalse
by default.onlineEventName
- Event name if you want to specify some other than theonline
(default) to trigger the process queue while still on the app. Eg: You don't use some other event on your app to say you have connection.TODO
If this works for you I'm missing documentation and tests.