Implement retry for failed save operations
Now that we visualize connection errors on failed save operations (#242 (closed)), users may want some convenience features:
- an easy way to retry requests
- given that we usually dispatch individual
PATCH
requests per field containing only the change for that field, retrying multiple failed requests may get tiresome: should we pool failed requests and allow users to retry them all at once? - should we warn users if they leave a page that contains unsaved fields?
- if 3: should this apply to all changed but unsaved fields (all types of errors – including validation rules) or just fields that have not been saved because of connection errors.
We should explore which of these options we deem necessary with regard to time constraints and how often they are actually needed.