You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 24, 2021. It is now read-only.
To support offline mutations even when the app is closed, the mutation requests have to be persisted in a database. Refer to #159 for detailed information.
You need to design a roadmap (flowchart/structure) for the same describing how you are planning to do that, what will be the structure of your database (SQLite/room or any other), how you are going to serialize the mutation requests, any extra files you would be making to implement this feature and so on. You can make it using draw.io or any other similar tool.
Feature Request
To support offline mutations even when the app is closed, the mutation requests have to be persisted in a database. Refer to #159 for detailed information.
You need to design a roadmap (flowchart/structure) for the same describing how you are planning to do that, what will be the structure of your database (SQLite/room or any other), how you are going to serialize the mutation requests, any extra files you would be making to implement this feature and so on. You can make it using draw.io or any other similar tool.