Enh: store message arrival time for use in sorting
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start by reviewing the issue's proposal for storing message arrival timestamps and import status, then trace how messages are added, archived, imported, and sorted by Date. Done would mean an agreed design and implementation that records arrival time for all relevant messages and supports arrival-order display, including imports.
Written by the indexing model from the issue text.
Description
Messages can be delayed in transit for various reasons; in particular messages that are moderated may incur a delay of several days.
It might be useful to show when a message actually arrived.
It would also be useful to be able to display messages in arrival order: at present they are displayed in order by Date, which means that it is quite difficult to see which messages have arrived since one last looked at a list.
For messages that were archived, the timestamp on the From_ line could potentially be used.
However that would not work for imports.
It might be useful to add a new field to the database with a timestamp showing when it was added.
Also whether it was imported or not.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/ponymail
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Similar issues
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kestra-io/kestra#20702 · 1 comment ·
Maintainers usually reply within 1 day
-
Form-data fields are not parsed when importing a cURL requestPossibly taken @aayushbaluni claimed this today. Openbug status-new
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug MVP
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
saayam-for-all/webapp#1911 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vshulcz/deja-vu#4937 · 2 comments ·
Maintainers usually reply within 1 day
-
[Focus] Accessibility (a11y) [Package] Grid [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day