Search by first characters in the name, not as general substring
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by locating the contact search entry point and reading how it currently matches names and other fields; the issue does not name files or tests. Check the behavior with the example names and a one-letter query, then confirm that first- or last-name prefixes appear without unrelated substring matches.
由索引模型根据 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
Imagine the following contact book (names only)
- James Adams
- Melissa Doe
- Valeria Moody
- Lenny Oldman
When you try searching, you'd expect that you'll get people whose first or last names start with the inputted prefix. For example, if you enter "m", you'd expect to have
- Melissa Doe
- Valeria Moody
in the search results.
But in reality, you'll have all four contacts displayed, because they all contain the letter "m".
I tried to switch somebody from Google Contacts to Fossify Contacts yesterday, but I had to revert the change when they couldn't search for their contacts by just entering one or two letters. And I was quite puzzled why the search works like this as well.
Why do you want this feature?
I think it's an expected behavior to filter contacts by first letters of either name field (or any other field). Nobody will search for "James" by typing "me" in the search field and it will be perceived just as a visual noise next to "Melissa", that the user was searching for.
Additional information
No response
- 主要语言
- Kotlin
- 星标
- 917
- 派生
- 73
- 平均合并
- 2 天 2 小时
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FossifyOrg/Contacts 的其他 Issue
-
feature request needs triage
难度 1/5 1 小时以内 新手友好度 72/100
FossifyOrg/Contacts#176 · 1 条评论 ·
维护者通常 1 天内回复
-
bug needs triage
难度 3/5 1-2 天 新手友好度 65/100
FossifyOrg/Contacts#630 ·
维护者通常 1 天内回复
-
bug needs triage
难度 3/5 1-2 天 新手友好度 64/100
FossifyOrg/Contacts#618 ·
维护者通常 1 天内回复
-
New field: IBAN未关闭feature request needs triage
难度 4/5 3-5 天 新手友好度 48/100
FossifyOrg/Contacts#613 ·
维护者通常 1 天内回复
-
bug needs triage
难度 4/5 3-5 天 新手友好度 52/100
FossifyOrg/Contacts#612 · 5 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
查看 FossifyOrg/Contacts 的全部 Issue
相似的 Issue
-
area:data-quality importer size:S
难度 2/5 1-3 小时 新手友好度 84/100
enorm-labs/event-junkie#3707 ·
维护者通常 1 天内回复
-
area/ui priority/p2 type/bug
难度 1/5 1 小时以内 新手友好度 94/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
commons-app/apps-android-commons#7072 ·
维护者通常 1 天内回复
-
bug ci good first issue help wanted severity: medium
难度 2/5 1-3 小时 新手友好度 65/100
dhananjay-nautiyal/music#17 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
T8RIN/ImageToolbox#3255 · 2 条评论 ·
维护者通常 1 天内回复