Failed move action should be sync afterwards #150
Description
When a move action sync fails (no network for instance), it might be tedious to apply it afterwards.
Calling a simple update from local data model won't work. It needs to be applied using the TaskApi.move endpoint.
The would mean to store failed move actions with proper parameters (source list, target list, parent task, position etc.)
This is true for move to top, move to list (new or not), indent, unindent (shouldn't be needed for subtask creation).
This should be stored in Database to allow syncing after app restart.
How to model "failed sync action" that are different in terms of parameters?
- As many tables as needed?
- As many columns as needed?
- A generic table with custom Json stored?
Anyway, it should contain the type of action that failed and the data to re-apply it.
(For non move action, storing action and local id might be enough?)