We could handle offline actions directly in the repository, to remove as much logic from the activities.
We could run it every time network connectivity has been regained.
With this I mean every time the connection is regained the repository would autonomously connect to the server and sync all changes that have been done offline.
We could handle offline actions directly in the repository, to remove as much logic from the activities.
We could run it every time network connectivity has been regained.
With this I mean every time the connection is regained the repository would autonomously connect to the server and sync all changes that have been done offline.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We could handle offline actions directly in the repository, to remove as much logic from the activities.
We could run it every time network connectivity has been regained.
With this I mean every time the connection is regained the repository would autonomously connect to the server and sync all changes that have been done offline.
Done and done !