Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add an option for one-time timers

未关闭
#262 1 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
android, kotlin
领域
mobile

调研方向

The payload names no files, so start from the Timer tab's create-timer flow and wherever saved timers are stored and listed. Read the linked issue #75 for prior context first. Done means the create flow offers a one-time option, that timer runs once and is removed from the saved list afterwards, and the existing saved-timer behaviour is unchanged.

由索引模型根据 Issue 内容生成。

描述

feature request needs triage
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

When creating a new timer in the "Timer"-tab I wish, that I had the additional option to create a one-time timer. "One-time" means, that this timer is only used one single time and then disappears automatically. It does NOT stay in the list of saved timers in the "Timer"-tab.

Why do you want this feature?
  • I want this feature, because sometimes I only need/want a timer once. Deleting such a timer costs time.
  • I personally find one-time timers more intuitive/natural to use than a list of saved timers.
  • In my opinion a one-time timer matches the general simplicity of all Fossify apps better than a list of saved timers.
Additional information

Relevant: https://github.com/FossifyOrg/Clock/issues/75

主要语言
Kotlin
星标
706
派生
73
平均合并
2 天 18 小时
30 天内合并 PR
10

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

FossifyOrg/Clock 的其他 Issue

查看 FossifyOrg/Clock 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。