Skip to content

Conversation

@olegbespalov
Copy link
Contributor

@olegbespalov olegbespalov commented Sep 15, 2025

⚠️ BREAKING CHANGE

Previously this method returned only reaction details, but with this change it started to also return the item itself (e.g. message, file, file_comment). This makes this closer to the actual response of the Slack API.

To migrate an existing code, you can just use resp.Reactions to access the slice of []ItemReaction.

API changes

GetReactions returns ReactedItem instead of the []ItemReaction. To migrate your existing logic, you can switch to using resp.Reactions

Closes #1479

@nlopes nlopes force-pushed the feat/reactions-get-full branch from d27ef61 to 8870d8e Compare January 24, 2026 22:42
!BREAKING CHANGE

Previously this method returned only reaction details, but with this change it started to also return the item itself (e.g. message, file, file_comment). This makes this closer to the actual response of Slack API.

To migrate an existing code, you can just use resp.Reactions to access
the slice of []ItemReaction.
@nlopes nlopes force-pushed the feat/reactions-get-full branch from 8870d8e to b4fa961 Compare January 24, 2026 23:42
I think the Slack API returns the channel field at the root level of the reactions.get
response for message types, not inside the message object.
@nlopes nlopes force-pushed the feat/reactions-get-full branch from 1fde67c to 5a50289 Compare January 25, 2026 14:58
@nlopes nlopes merged commit 14acba2 into slack-go:master Jan 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adjust GetReactions to return also an item to align with Slack API

2 participants