nextcloud / nextcloud/mail

Store envelope actions in a debounced queue

Open
#10,725 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement performance 🚀 skill:backend skill:frontend
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Is your feature request related to a problem? Please describe.

Let's say I delete multiple envelopes in rapid succession one-by-one. This would cause many small requests to be sent to the backend which cause a lot of unnecessary connection to the IMAP server. Operations should be bundled in larger chunks.

Requires https://github.com/nextcloud/mail/pull/10280

Describe the solution you'd like

Implement an envelope action queue in the frontend. Have a debounced flush timer that sends all similar actions in one big chunk to the backend, e.g. wait for a second without interaction and send all deletes at once.

Describe alternatives you've considered

No response

Additional context

This require extensive refactoring of our frontend. An action queue probably means to have a good abstraction over all possible envelope actions that have to be stored centrally. We would also need to think about handling errors (rollbacks?).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing required pull request #10280, then trace the frontend paths that send envelope actions. The issue names no files or tests, so map where these actions are coordinated before designing the queue. Done means similar rapid actions are bundled after the debounce period and the error or rollback behavior is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.