Repository navigation
fix: bring back reaction apis to channel - #1906
Merged
Merged
Conversation
isekovanic
requested review from
MartinCupela,
oliverlaz and
szuperaz
as code owners
October 9, 2026 14:09
MartinCupela
approved these changes
Oct 9, 2026
|
🎉 This PR is included in version 10.0.0-rc.21 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
3 participants
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.
CLA
Description of the changes, What, Why and How?
#1897 removed
channel.sendReaction/channel.deleteReaction. This brings them back as thin pass-throughs toclient.sendReaction/client.deleteReaction. They take the same arguments,(pathParams, request, requestOptions), and return the same response.They send the HTTP request only: no local state and no offline queueing, the same as the client methods. The full operation (optimistic state, offline queue, rollback) is still
messageOperations.addReaction/deleteReaction.Unlike the versions removed in #1897, these don't queue for offline replay and don't require the channel to have an id, since a reaction is addressed by message id.
The migration guide no longer lists them as removed.
Changelog
channel.sendReactionandchannel.deleteReactionare back, as pass-throughs toclient.sendReaction/client.deleteReaction