[feature request] Be able to undo the alarm clock that was just deleted
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- mobile-dev
Research direction
First, locate the alarm deletion logic in the Kotlin codebase, likely in the module handling alarm list operations. Add a temporary undo prompt (such as a Snackbar) when an alarm is deleted, retain the deleted alarm's data for a short window, and restore it if the user selects undo. Test the flow by deleting an alarm and verifying the undo option functions correctly.
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
[feature request] Be able to undo the alarm clock that was just deleted
Why do you want this feature?
sometime delete alarm by mistake
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 706
- Forks
- 73
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 8
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/Clock
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Clock#504 · 1 comment ·
Maintainers usually reply within 7 days
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FossifyOrg/Clock#492 ·
Maintainers usually reply within 7 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Clock#448 · 2 comments · 1 reaction ·
Maintainers usually reply within 7 days
-
feature request needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Clock#446 ·
Maintainers usually reply within 7 days
-
bug needs triage
Difficulty 2/5 Under an hour Newbie friendliness 74/100
FossifyOrg/Clock#439 ·
Maintainers usually reply within 7 days
All issues in FossifyOrg/Clock
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Kotlin/kotlin-lsp#288 ·
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
enorm-labs/event-junkie#3166 ·
Maintainers usually reply within 1 day
-
bugbane/qf good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
osservatorionessuno/bugbane#173 ·
Maintainers usually reply within 1 day
-
Android: build fails with Android Gradle Plugin 9 (kotlinOptions, lintOptions, proguard-android.txt)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
capacitor-community/stripe#544 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100