feat: reaction events in watch + react command #31
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
This PR addresses issues #24 and #26 by adding:
--reactionsflag forwatchcommand (Feature request: Include reactions/tapbacks in message output #26)is_reaction,reaction_type,reaction_emoji,is_reaction_add,reacted_to_guidimsg reactcommand (Feature request: Send tapback reactions #24)Usage
Watch with reactions
# Stream messages AND reaction events imsg watch --chat-id 1 --reactions --jsonOutput includes reaction events with metadata:
{ "id": 12345, "chat_id": 1, "is_reaction": true, "reaction_type": "like", "reaction_emoji": "👍", "is_reaction_add": true, "reacted_to_guid": "ABC123-DEF456" }Send reactions
Limitations
The
reactcommand:Testing
Built and tested locally on macOS 15. All existing tests pass.
Closes #24
Closes #26