fix: display reply indicators for received DM replies #64
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
Populates
replyMetadatawhen saving DM messages that containrepliesToMessageId, enabling the existing reply display UI to show "Replying to X".Problem
For Quorum DMs, the relay hub only sees encrypted blobs (E2E encryption via X3DH + Double Ratchet). Unlike Farcaster where the server returns
inReplyTowith full context, Quorum's API only returns the message ID reference inside encrypted content.The mobile app has full support for displaying reply indicators (
MessagesList.tsxchecksreplyToAuthor), butreplyMetadatawas never being populated for DMs.Solution
In
mmkvAdapter.saveMessage(), after loading existing messages, look up the parent message and populatereplyMetadata:Testing
Edge Cases
replyMetadatastays undefined (graceful degradation)replyMetadata→ not overwritten