Modify 'Day and alarm time' sorting option
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 22/100
調査の方向性
The payload names no files, so start by searching the Kotlin sources for the 'Day and alarm time' sort option and the code that orders alarms. Read the discussion in #155 first, since the maintainer proposed removing this option and the thread has no decision. Done would mean the option stays and alarms that occur today are placed by their weekday within the list. Expect the work to need a maintainer's direction before coding.
索引モデルが issue の本文から書いたものです。
説明
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
As I have argued in #155, it seems to me that the current behaviour of the 'Day and alarm time' sorting option is not intuitive, as alarms that happen 'Today' are always shown before other items.
In that discussion @naveensingh suggested to remove that option, but in my opinion it would be nice to keep it. For instance, it would be useful if one has several recurring events during a week and wants to see them ordered by day (first).
So, I suggest to keep that sorting option but also to modify the ordering that one gets with it by putting the events that occur 'Today' in the right place of the list, depending on which day of the week 'Today' is.
Why do you want this feature?
Have a more consistent ordering with that option
Additional information
No response
- 主要言語
- Kotlin
- スター
- 706
- フォーク
- 73
- 平均マージ
- 2日 18時間
- マージ済み PR（30日）
- 10
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
FossifyOrg/Clock のほかの issue
-
feature request needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
FossifyOrg/Clock#504 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
feature request needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
FossifyOrg/Clock#492 ·
メンテナーはふだん 1 日以内に返信
-
feature request needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
FossifyOrg/Clock#491 ·
メンテナーはふだん 1 日以内に返信
-
bug needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
FossifyOrg/Clock#448 · コメント 2 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
feature request needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
FossifyOrg/Clock#446 ·
メンテナーはふだん 1 日以内に返信
FossifyOrg/Clock の issue をすべて見る
似ている issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
SLNE-Development/surf-chat#134 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100