feat(CLNP-2026): support reactions for super group channel

[bang9]

External Contributions

This project is not yet set up to accept pull requests from external contributors.

If you have a pull request that you believe should be accepted, please contact
the Developer Relations team [email protected] with details
and we'll evaluate if we can setup a CLA to allow for the contribution.

For Internal Contributors

CLNP-2026

Description Of Changes

Add a brief description of the changes that you have involved in this PR

Types Of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply_

• Bugfix
• New feature
• Documentation (correction or otherwise)
• Cosmetics (whitespace, appearance (ex) Prettier)
• Build configuration
• Improvement (refactor code)
• Test

---

• spec: https://sendbird.atlassian.net/wiki/spaces/UK/pages/2265614898/Reactions+for+Super+Group+Channel

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes are missing coverage. Please review.

Project coverage is 13.00%. Comparing base (48aa109) to head (8ab0720).

Files	Patch %	Lines
...native/src/components/ChannelMessageList/index.tsx	0.00%	3 Missing ⚠️
...c/components/GroupChannelMessageRenderer/index.tsx	0.00%	2 Missing ⚠️
...es/uikit-react-native/src/contexts/ReactionCtx.tsx	0.00%	1 Missing ⚠️
packages/uikit-utils/src/sendbird/message.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #159      +/-   ##
==========================================
- Coverage   13.01%   13.00%   -0.01%     
==========================================
  Files         334      334              
  Lines        7430     7434       +4     
  Branches     2050     2052       +2     
==========================================
  Hits          967      967              
- Misses       6392     6396       +4     
  Partials       71       71              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[HoonBaek]

How about changing the param reactionEnabled to config for the shouldRenderReaction?

// Usage
const configs = sbOptions.uikitWithAppInfo.groupChannel.channel;
shouldRenderReaction(channel, configs)

// Function
export function shouldRenderReaction(channel: SendbirdBaseChannel, configs: CustomDefinedConfigType) {
  if (channel.isOpenChannel()) {
    return false;
  }

  if (channel.isGroupChannel()) {
    if (channel.isBroadcast) return false;
    if (channel.isEphemeral) return false;
    if (channel.isChatNotification) return false;
  }

  return channel.isSuper ? configs.enableReactionsSupergroup : configs.enableReactions;
}

[bang9]

How about changing the param reactionEnabled to config for the shouldRenderReaction?

// Usage
const configs = sbOptions.uikitWithAppInfo.groupChannel.channel;
shouldRenderReaction(channel, configs)

// Function
export function shouldRenderReaction(channel: SendbirdBaseChannel, configs: CustomDefinedConfigType) {
  if (channel.isOpenChannel()) {
    return false;
  }

  if (channel.isGroupChannel()) {
    if (channel.isBroadcast) return false;
    if (channel.isEphemeral) return false;
    if (channel.isChatNotification) return false;
  }

  return channel.isSuper ? configs.enableReactionsSupergroup : configs.enableReactions;
}

In such cases, it's preferable to receive a single value determined externally rather than adding logic internally to handle multiple values.

For example, if we need to determine the enabled status of a reaction and it requires adding a flag at the module level rather than in the config, then we should add a new parameter.

This is similar to why we can pass anything to the children when rendering components. (we should not write code that brings outside events inside the house to resolve them.)