feat(react-native-uikit-docs): Pin & Save, Pin Conversation and Thread Subscription

[suraj-chauhan-cometchat]

Brings the React Native UI Kit docs to parity with the Android and React kits for the four features shipped in @cometchat/chat-uikit-react-native@5.5.0.

Before this, React Native had the two panel component pages (pinned-messages, saved-messages) but no core-features entries, no guides, and no mention of the thread-subscription bell anywhere.

Core features

ui-kit/react-native/core-features.mdx gains three sections, placed in the same order Android uses:

Mentions → Pin & Save Messages → Pin Conversations → Rich Text Formatting
Threaded Conversations → Thread Subscription → Group Chat

Thread Subscription sits directly after Threaded Conversations, as requested.

New guides

File	Modelled on
guide-pin-and-save-messages.mdx	ui-kit/react/guide-pin-and-save-messages.mdx
guide-thread-subscription.mdx	ui-kit/android/guide-thread-subscription.mdx

Both are added to docs.json in Android's relative order: threaded-messages → thread-subscription → pin-and-save.

Thread header component

threaded-messages-header.mdx gains a Thread Subscription section, mirroring the React thread-header page.

Two deliberate divergences from the reference platforms

These are real platform differences, documented rather than copied:

1. The bell is on CometChatMessageHeader, not CometChatThreadHeader.
React puts its toggle on the thread header. The landed React Native design places it in the thread screen's top bar, driven by parentMessage + threadSubscriptionVisibility. CometChatThreadHeader's TrailingView is the escape hatch for a custom control there and explicitly does not host the bell. The section says so, so nobody goes looking for a prop that isn't there.

2. Thread Subscription is ON by default on React Native, and has no dashboard flag — so it is documented as opt-out via ThreadSubscriptionConfig.setEnabled(false). Android documents the same feature as opt-in because its default differs. The React Native text matches what v5.5.0 actually ships and the published release notes.

Pin is documented as available to every member, with the server enforcing permission — matching React. The React Native role gate was removed in ENG-38197, so canPin() now only asserts that somebody is logged in.

Verification

• 0 dangling navigation refs across the whole docs.json — build is safe
• 100 internal links across the changed files, all resolve
• docs.json diff is 3 insertions / 1 deletion — no reformat churn
• Every prop, method and default documented here was read from the shipped 5.5.0 source, not from the design doc

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
cometchat	🟢 Ready	View Preview	Sep 11, 2026, 11:42 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[raj-dubey1]

Review — React Native Pin & Save, Pin Conversation, Thread Subscription

Verdict: request changes (one code fix + a few small ones). The structure is safe to merge and nearly every claim matches the shipped kit. I checked the pages against the @cometchat/chat-uikit-react-native@5.5.0 source from npm. One code sample in the new guide is wrong, though, and it contradicts the component page in this same PR.

Must fix

1. The Saved Messages guide code reads fields that don't exist on source. ui-kit/react-native/guide-pin-and-save-messages.mdx:153-160 does:

onItemPress={(message, source) => {
  navigation.navigate("Messages", { user: source?.user, group: source?.group, ... });
}}

In 5.5.0, SavedMessageSource is { receiverType, receiverId, label, name, avatar? }, with no user or group (src/shared/utils/SavedMessagesHelper.ts:16-27). So this fails TypeScript, and at runtime it opens "Messages" with user and group both undefined. saved-messages.mdx:113-114 in this PR already does it correctly with source?.receiverType / source?.receiverId. Mirror that here, for example by resolving the User/Group from receiverId and receiverType before navigating.

Should fix

2. The threads guide wires a prop the RN message list doesn't have. guide-threaded-messages.mdx:129, 165, 362 use onThreadRepliesClick, but the RN prop is onThreadRepliesPress (CometChatMessageList.tsx:346). So the guide's navigation to the thread screen never fires. This predates the PR, but the new Thread Subscription section on the same page depends on reaching that screen.

3. "Jump to this message" is never wired. Both screens in the guide pass messageId back to "Messages" (:94-100, :153-160), with the comment "Jump the main message list to this message". The Complete Example (:200-234) never uses it. Either show goToMessageId={route.params?.messageId} on CometChatMessageList (documented at message-list.mdx#gotomessageid), or drop the jump claim.

Nits

4. The thread option's label doesn't match the kit.

• message-list.mdx:443 and :1177, which this PR edits, call it "Follow / Unfollow thread".
• The message-header.mdx:511 example logs "Following this thread".
• The kit's strings are "Subscribe to thread" and "Unsubscribe from thread" (translation.json:231-232), which core-features.mdx and the guide already use.

5. The pinned-messages button needs both props. message-header.mdx:441 says to set showPinnedMessagesButton to render the button. The kit renders it only when onPinnedMessagesPress is also set (CometChatMessageHeader.tsx:343), so say "set both".

6. The PR description is out of date. It lists a new guide-thread-subscription.mdx (folded into guide-threaded-messages.mdx in 4376a5a) and an opt-out via ThreadSubscriptionConfig.setEnabled(false) (references removed in bf75dc1). It also says docs.json changed by 3 insertions and 1 deletion, but it's +2/−1 including an indentation-only change on "index". Worth updating so reviewers don't look for things that aren't there. Optionally, ThreadSubscriptionConfig (still exported, default on) could get one line as the app-wide off switch.

Checked and fine

• Build and URLs: 0 unresolved navigation refs; the new guide is in navigation. No files removed or renamed, so no redirects are needed. 0 broken internal links across 62 scanned pages.
• Images: images/pin.png and images/save.png exist and are referenced with descriptive alt text.
• Checked against the 5.5.0 source:
  • The kit resolves the Pin, Save and Pin Conversation flags itself at login and on every reconnect (PinSaveFeatureGates.ts:78-80, CometChatUIKit.ts:185,210), so "no app code to write" is correct, including for restored sessions.
  • canPin() only checks for a logged-in user, so "every member, server enforces" is correct.
  • The limit toasts use the server's limit.
  • Header props and defaults: showPinnedMessagesButton is false, threadSubscriptionVisibility is true, and onThreadSubscriptionChange exists.
  • Thread subscription is on by default.
  • CometChatThreadHeader has TrailingView.
  • CometChatMessageList has parentMessage (with parentMessageId deprecated).
  • The CometChatPinnedMessages default page size is 30.
  • The automatic-subscription rules match the kit's thread helper.
  • Every other identifier in backticks across the 9 changed pages exists in 5.5.0.

🤖 Generated with Claude Code

[suraj-chauhan-cometchat]

Thanks — all three Must fix / Should fix items are addressed in 775cdc97. Each was verified against the 5.5.0 source before changing anything; you were right on all three.

1. (must) source?.user / source?.group — confirmed SavedMessageSource is { receiverType, receiverId, label, name, avatar? } (SavedMessagesHelper.ts:16-27). The guide now resolves the User/Group from receiverId + receiverType before navigating, so the Messages screen signature is unchanged, and the prose lists the real fields with a link to the component reference.

2. (should) onThreadRepliesClick — confirmed the prop is onThreadRepliesPress (CometChatMessageList.tsx:346). Renamed in all 3 places plus the handler name. Agreed this predates the PR, but it mattered here because the new Thread Subscription section depends on reaching that screen.

3. (should) unwired jump — confirmed goToMessageId?: string exists (CometChatMessageList.tsx:587) and drives getMessagesAroundId. Wired it in the Complete Example rather than dropping the claim, so the messageId both screens pass is now actually consumed.

Nits 4–6 are knowingly still open: the thread label drift, message-header.mdx saying to set only showPinnedMessagesButton, and the stale PR description.

Not merging yet — a follow-up pass on the newly restructured pinned-messages.mdx / saved-messages.mdx turned up two further must-fixes of our own (ItemView on CometChatPinnedMessages replaces only the bubble, not the row; and one snippet that fails typecheck). Those are being fixed next.

🤖 Generated with Claude Code