DM shows raw public key instead of contact name #54
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_archipelagos#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Server-side DMs are created with
conversation.name = format!("DM with {}", participant_public_key). The messaging archipelago rendered that stored string literally in both the chat list and the chat detail header, so the UI showed raw keys like'DM with fulltest123key456'where the contact's friendly name was expected.Fix: add
participant_keys: Vec<String>toChatPreviewData; expose a pureresolve_chat_display_name(raw_name, is_group, participant_keys, own_user_key, contacts)helper in the service layer; load contacts unconditionally on archipelago mount; resolve the non-self participant's contact name at render time and in the chat detail fetch. Groups keep the stored name unchanged; unknown participants fall back to the raw name.zaelgohary referenced this issue2026-04-19 08:29:02 +00:00
bug: DM name shows 'DM with <public_key>' instead of the contact's nameto DM shows raw public key instead of contact namezaelgohary referenced this issue from lhumina_code/hero_os2026-04-19 09:26:23 +00:00
Fixed by #56.