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
The success or failure state of exports and imports should be derived by listening to notifications (if the app is enabled) instead of the status endpoint so that the modal and notifications on the frontend do not present discrepancies or desync due to different polling intervals
The status endpoint would only be queried to check if the export/import was queued successfully and if the job has started
Final success/failure state of the job would be derived by listening to notifications through the event-bus to
a) ensure a single source of truth is used for both the modal and notifications
b) provide actual success/failure state rather than just if the job has finished executing as the user_export_jobs and user_import_jobs tables do not contain this information
There is currently no event for when a new notification came in, but I guess we can add this on top of nextcloud/notifications#728 so once the event-bus is in
The success or failure state of exports and imports should be derived by listening to notifications (if the app is enabled) instead of the status endpoint so that the modal and notifications on the frontend do not present discrepancies or desync due to different polling intervals
a) ensure a single source of truth is used for both the modal and notifications
b) provide actual success/failure state rather than just if the job has finished executing as the
user_export_jobs
anduser_import_jobs
tables do not contain this informationRequires
The text was updated successfully, but these errors were encountered: