When updating notification table with AJAX only use latest data #16445

Merged
lunny merged 2 commits from notification-sequence into main 2021-07-17 16:18:11 +00:00
Contributor

When marking a lot of notifications individually as read on the /notifications page, the results may be returned out of order or delayed because of the use of AJAX. This PR sends a sequence number to gitea so that the browser can ensure that only the results of the latest notification change are shown.

Improves #10961

Signed-off-by: Andrew Thornton art27@cantab.net

When marking a lot of notifications individually as `read` on the `/notifications` page, the results may be returned out of order or delayed because of the use of AJAX. This PR sends a sequence number to gitea so that the browser can ensure that only the results of the latest notification change are shown. Improves #10961 Signed-off-by: Andrew Thornton <art27@cantab.net>
lafriks (Migrated from github.com) approved these changes 2021-07-16 12:44:35 +00:00
6543 (Migrated from github.com) approved these changes 2021-07-17 15:53:52 +00:00
This repo is archived. You cannot comment on pull requests.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lunny/gitea#16445
No description provided.