Display Names Under Group Messages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
Research direction
Start by locating the group-chat message rendering entry point and reading how sender information is currently available to the UI. The screenshots show the intended outcome: sender names should appear under messages in group chats; check the existing conversation layout and tests, if present, to understand what behavior needs coverage.
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
Display names under messages in group chats
Why do you want this feature?
I would like to immediately know who sent which messages in group chats. Every other text app displays sender names under group texts. Currently, it is not immediately obvious to me who sent a message when I read my messages in group chats. This is frustrating.
Additional information
This is e/os messages, which displays sender names under group texts
Fossify Messages does not display sender names. Group texts are confusing:
- 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 62/100
damontecres/Wholphin#2069 ·
Maintainers usually reply within 1 day
-
Android (vision-camera-location): HybridLocationManager never quits its HandlerThread on disposeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
margelo/react-native-vision-camera#4217 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
saisaharsh3/Leftovers#13 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
navikt/esyfo-narmesteleder#700 ·
Maintainers usually reply within 1 day
-
[DEV] Update ktlintOpenbackend maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
digitalfabrik/entitlementcard#3183 ·
Maintainers usually reply within 7 days