Fix announced LXMF peer names on iOS - #137
Merged
Merged
Conversation
Contributor
Greptile SummaryThe PR now atomically replaces generated peer-name placeholders with announced LXMF display names while preserving custom names, and refreshes the visible conversation list after the committed metadata change.
Confidence Score: 5/5The PR appears safe to merge. The previously reported stale-list issue is resolved by posting a metadata-change notification after the conditional database update completes and reloading the active ChatsViewModel from the committed store; no blocking failure remains. Important Files Changed
Sequence DiagramsequenceDiagram
participant Peer as LXMF Peer
participant Services as AppServices
participant Repo as MessageRepository
participant DB as GRDB
participant VM as ChatsViewModel
Peer->>Services: Announce with display name
Services->>Repo: applyAnnouncedDisplayName(hash, name)
Repo->>DB: Conditional UPDATE
DB-->>Repo: One row updated
Repo-->>VM: conversationMetadataChangedNotification
VM->>Repo: loadConversations()
Repo-->>VM: Conversation with announced name
Reviews (2): Last reviewed commit: "test: isolate announced name refresh sig..." | Re-trigger Greptile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Peer <hash>conversation placeholders when an LXMF announce supplies the peer's display nameVerification
Risk and rollback
The update is limited to conversation rows whose display name is null, empty, or exactly the generated hash placeholder. Reverting this PR restores the previous behavior.