Option: Mark SMS as read after deleting the notification
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No files or tests are named in the issue. Start by locating the notification-dismissal flow and how the app marks an SMS as read; check whether swiping away a notification can trigger that action. Done means dismissing an SMS notification marks its message as read, while other notification behavior remains unchanged.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Automatically mark SMS message as read after swiping the notification
Why do you want this feature?
it's not a popular feature, but it's quite intuitive and eliminates the need to aim at the "Mark as read" button every time, making the interaction more convenient without creating a clutter of unread messages. These messages often appear after receiving short security codes or quick replies, which I prefer to swipe away (clear) from my smart band and not think about them further. I'm sure I'm not the only one who does this.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 1.6k
- Forks
- 187
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 FossifyOrg/Messages
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
FossifyOrg/Messages#919 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Messages#897 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Messages#761 ·
Maintainers usually reply within 1 day
-
[Export] mms "No entries for export have been found"May be free again A pull request for this issue was closed without being merged. Openbug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
FossifyOrg/Messages#493 · 24 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
FossifyOrg/Messages#918 · 1 comment ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Messages
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rustyrazorblade/easy-db-lab#1017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-brownfield#492 · 1 comment ·
Maintainers usually reply within 4 days
-
fix: retain the best partial noise-correction solutionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
world-federation-of-advertisers/cross-media-measurement#4653 ·
Maintainers usually reply within 1 day