Adding ability to fetch reactions from conversation messages

[kinga112]

I am new to this git library (not entirely new to XMTP), and also new to rust, but wanted to ask if there was the ability to fetch reactions easily.

seems like reactions are already fetched and used to form num_reactions inside the message struct
num_reactions: msg.reactions.len() as i32,

I may pull and try to test and send in a PR, but wanted to ask if it was as easy as it looks. I dont know the content of msg.reactions but I will try to mess around with this.

[gitctrlx]

Hey, good catch — you're on the right track.

Right now msg.reactions from the upstream DecodedMessage is available at the FFI layer, but we only pass through the count (msg.reactions.len() as i32 → num_reactions). The actual reaction data (emoji, sender, action, etc.) isn't exposed across the C FFI boundary yet.

To make this work, you'd need to:

1. Add a reactions list to FfiEnrichedMessage (or a separate accessor function)
2. Map each reaction's fields (reference, content, action, schema) through the FFI
3. Mirror that on the Rust wrapper side in Message

It's not hard conceptually — mostly plumbing work. Happy to review a PR if you want to take a stab at it.

[gitctrlx]

Actually, I should clarify my earlier reply — reactions are already fully accessible in the current API.

In XMTP, reactions are standalone messages with content type xmtp.org/reaction:2.0. So when you list messages from a conversation, reaction messages are already there. You just decode them:

let content = msg.decode()?;
if let Content::Reaction(r) = content {
    // r.reference  — message ID being reacted to
    // r.content    — the emoji (e.g. "👍")
    // r.action     — Added / Removed
    // r.schema     — Unicode / Shortcode / Custom
}

The num_reactions field on enriched messages is a pre-computed count for convenience — so you can show "3 reactions" in a message list without decoding every reaction message yourself.

If what you're after is getting the full list of reactions grouped with each parent message (instead of filtering them manually from the message stream), that would be a new convenience feature on top of what already exists. But the raw data is all there today.

[kinga112]

Thank you for your response! I did notice content_type including all message types. I was looking at the XMTP node sdk docs as a reference which includes a way to call reactions on each message. Yes, definitely just an enhancement, but I will send a PR when I have time to work on this improvement. I appreciate the time you took with your response and the steps needed to accomplish this task! Looking forward to continue using this package! Thanks for all the hard work!