feat(call): use correct thread components

[whutchinson98]

macro-cz9CYNqjvBDaWKRFBuEBw-use-correct-railchat-for-transcript

[macro-application]

use correct railchat for transcript

[github-actions]

Preview: https://hutch-fix-call-use-correct-thr-3z6gnx.preview.macro.com/app (678a793)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 25dcbae6-1fda-488e-ab6d-662432511b27

📥 Commits

Reviewing files that changed from the base of the PR and between 555c827 and 5e3834a.

📒 Files selected for processing (2)

• js/app/packages/block-call/component/CallBlockAdapter.tsx
• js/app/packages/block-call/component/CallTranscript.tsx

---

📝 Walkthrough

Summary by CodeRabbit

• Refactor
  • Call transcript display has been refactored to use channel messaging components for improved visual consistency and better integration with the messaging system. Transcript segments now feature enhanced channel context information, refined icon display handling for grouped segments, and improved alignment with standard channel message presentation formats.

Walkthrough

Call transcript rendering was refactored to integrate with channel messaging primitives. CallBlockAdapter now passes a channelId prop to CallTranscript, which was updated to accept this prop and render transcript segments using channel-message components instead of user-display rendering, utilizing a segmentToApiChannelMessage() mapping function.

Changes

Cohort / File(s)

Summary

Call Transcript Channel Integration js/app/packages/block-call/component/CallBlockAdapter.tsx, js/app/packages/block-call/component/CallTranscript.tsx

Updated call transcript rendering to use channel-message primitives instead of user-display rendering. CallBlockAdapter passes channelId from data to CallTranscript; CallTranscript now requires channelId in props and uses segmentToApiChannelMessage(segment, channelId) to map transcript segments to ApiChannelMessage objects for display through Thread.Row, Message.Root, and Message.Layout components. TranscriptSegmentRow and GroupedTranscriptSegmentRow updated to accept and use channelId prop, with grouped rows hiding the sender icon.

Possibly related PRs

• Hutch/feat call block #2554: Directly related—both PRs modify CallBlockAdapter and CallTranscript components, with this PR adding the channelId prop integration to components previously introduced.
• feat(call): use channel style rails for call transcript #2576: Modifies same transcript row components; this PR builds on that refactor by adding channelId prop support and ApiChannelMessage mapping for channel-style row rendering.

🚥 Pre-merge checks | ✅ 1 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description appears to be a branch name or ticket identifier rather than a meaningful description of the changes, making it too vague to convey what the PR actually accomplishes.	Provide a clear description explaining why the thread components are being changed and what the expected impact is on the call transcript rendering.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows conventional commits format (feat:) and is well under 72 characters (41 chars). It clearly describes the main change: using correct thread components for call transcripts.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}