Skip to content

Conversation

@gabriellsh
Copy link
Member

@gabriellsh gabriellsh commented Dec 10, 2025

Proposed changes (including videos or screenshots)

Issue(s)

VGA-75

Steps to test or reproduce

Further comments

Summary by CodeRabbit

  • New Features

    • View media call history with separate rendering for internal and external records.
    • Contextual bar UI showing call details and actions (voice call, direct message, jump-to-message, user info).
    • Call history tab integrated into room toolbox and core room routes for easy access.
    • New actions provider to surface call-related actions from history items.
  • Localization

    • Added messages for call info load failures and retry prompts.

✏️ Tip: You can customize this high-level summary in your review settings.

@dionisio-bot
Copy link
Contributor

dionisio-bot bot commented Dec 10, 2025

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

@changeset-bot
Copy link

changeset-bot bot commented Dec 10, 2025

⚠️ No Changeset found

Latest commit: 601bfb0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 10, 2025

Walkthrough

Adds a media call history contextual bar feature: new contextual-bar component with API fetch and error handling, internal and external renderers, internal actions hook, room-toolbox core route/provider integration, message-block action to open the history tab, query keys, and i18n keys.

Changes

Cohort / File(s) Summary
Contextual Bar
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx
New component that fetches call-history.info, shows loading/error states, and dispatches to internal or external renderers based on response. Exports named and default.
Internal History UI & Actions
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx, apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts
New internal renderer with type guard and contact normalization; new hook useMediaCallInternalHistoryActions exposing voiceCall, directMessage, jumpToMessage, and userInfo actions.
External History UI
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx
New external renderer with type guard, contact derivation, history data mapping, and a voice-call action.
Room Toolbox: core routes & provider
apps/meteor/client/views/room/providers/hooks/useCoreRoomRoutes.ts, apps/meteor/client/views/room/providers/RoomToolboxProvider.tsx
Added useCoreRoomRoutes() returning core route config (including media-call-history) and updated RoomToolboxProvider to resolve core routes by id before action-based lookup.
Message Block Integration
apps/meteor/client/uikit/hooks/useMessageBlockContextValue.ts
Integrated useRoomToolbox and handled appId: 'media-call-core' + actionId: 'open-history' to call openTab('media-call-history', blockId).
Query Keys
apps/meteor/client/lib/queryKeys.ts
Added callHistoryQueryKeys (all and info(callId?)) for client query-keying of call history endpoints.
i18n
packages/i18n/src/locales/en.i18n.json
Added keys: Call_info_could_not_be_loaded ("Call info could not be loaded") and Please_try_again ("Please try again.").

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MessageBlock as Message Block Hook
    participant Toolbox as Room Toolbox
    participant CoreRoutes as Core Room Routes
    participant Contextualbar as MediaCallHistoryContextualbar
    participant API as Server API
    participant Internal as MediaCallHistoryInternal
    participant External as MediaCallHistoryExternal

    User->>MessageBlock: trigger 'open-history' (blockId)
    MessageBlock->>Toolbox: openTab('media-call-history', blockId)
    Toolbox->>CoreRoutes: resolve tab by id
    CoreRoutes-->>Toolbox: return media-call-history route
    Toolbox->>Contextualbar: render contextual bar (route context)
    Contextualbar->>API: fetch call-history.info (async)
    API-->>Contextualbar: return call data
    alt internal call
        Contextualbar->>Internal: render internal component
        Internal->>Internal: compute contact & actions via hook
    else external call
        Contextualbar->>External: render external component
        External->>External: compute contact & actions
    end
    Internal-->>User: show actions (voice, DM, jump, user info)
    External-->>User: show actions (voice)
Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

  • Areas to focus:
    • useMediaCallInternalHistoryActions.ts (multiple contexts, router/navigation, useEffectEvent)
    • RoomToolboxProvider.tsx (route resolution priority, memo deps)
    • MediaCallHistoryContextualbar.tsx (API fetching, error handling, type guards)

Possibly related PRs

Suggested labels

stat: ready to merge, stat: QA assured

Suggested reviewers

  • KevLehman
  • tassoevan

Poem

🐰 I hopped to the toolbox and opened the door,
Found echoes of calls and the stories they bore.
Internal, external — each history in view,
Buttons to ring, message, or jump straight to you.
A little rabbit cheers — history looks new! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Linked Issues check ❓ Inconclusive The linked issue VGA-75 provides no specific coding requirements, making full compliance assessment inconclusive. Review the linked issue VGA-75 to verify all coding requirements are met and documented.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Out of Scope Changes check ✅ Passed All changes directly relate to implementing the call history contextual bar feature with no unrelated modifications detected.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title 'feat: Implement Call History contextual bar inside rooms' directly and clearly describes the main change: adding a call history contextual bar UI component to rooms.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/callHistoryCore

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

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

@gabriellsh gabriellsh added this to the 7.14.0 milestone Dec 10, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 10, 2025

📦 Docker Image Size Report

📈 Changes

Service Current Baseline Change Percent
sum of all images 1.2GiB 1.2GiB +12MiB
rocketchat 358MiB 347MiB +12MiB
omnichannel-transcript-service 132MiB 132MiB -479B
queue-worker-service 132MiB 132MiB +279B
ddp-streamer-service 126MiB 126MiB -1.1KiB
account-service 113MiB 113MiB +523B
authorization-service 111MiB 111MiB +363B
stream-hub-service 110MiB 110MiB +79B
presence-service 110MiB 110MiB -563B

📊 Historical Trend

---
config:
  theme: "dark"
  xyChart:
    width: 900
    height: 400
---
xychart
  title "Image Size Evolution by Service (Last 30 Days + This PR)"
  x-axis ["11/15 22:28", "11/16 01:28", "11/17 23:50", "11/18 22:53", "11/19 23:02", "11/21 16:49", "11/24 17:34", "11/27 22:32", "11/28 19:05", "12/01 23:01", "12/02 21:57", "12/03 21:00", "12/04 18:17", "12/05 21:56", "12/08 20:15", "12/09 22:17", "12/10 23:26", "12/11 21:56", "12/12 22:45", "12/13 01:34", "12/15 22:31", "12/16 22:18", "12/17 21:04", "12/18 20:41", "12/18 20:46 (PR)"]
  y-axis "Size (GB)" 0 --> 0.5
  line "account-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
  line "authorization-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
  line "ddp-streamer-service" [0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12]
  line "omnichannel-transcript-service" [0.14, 0.14, 0.14, 0.14, 0.14, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13]
  line "presence-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
  line "queue-worker-service" [0.14, 0.14, 0.14, 0.14, 0.14, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13]
  line "rocketchat" [0.36, 0.36, 0.35, 0.35, 0.35, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.35]
  line "stream-hub-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
Loading

Statistics (last 24 days):

  • 📊 Average: 1.5GiB
  • ⬇️ Minimum: 1.2GiB
  • ⬆️ Maximum: 1.6GiB
  • 🎯 Current PR: 1.2GiB
ℹ️ About this report

This report compares Docker image sizes from this build against the develop baseline.

  • Tag: pr-37773
  • Baseline: develop
  • Timestamp: 2025-12-18 20:46:34 UTC
  • Historical data points: 24

Updated: Thu, 18 Dec 2025 20:46:35 GMT

@codecov
Copy link

codecov bot commented Dec 10, 2025

Codecov Report

❌ Patch coverage is 19.27711% with 67 lines in your changes missing coverage. Please review.
✅ Project coverage is 67.78%. Comparing base (5106fcd) to head (601bfb0).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #37773      +/-   ##
===========================================
+ Coverage    67.72%   67.78%   +0.05%     
===========================================
  Files         3464     3469       +5     
  Lines       113728   113811      +83     
  Branches     20908    20926      +18     
===========================================
+ Hits         77024    77143     +119     
+ Misses       34527    34483      -44     
- Partials      2177     2185       +8     
Flag Coverage Δ
e2e 57.10% <19.27%> (-0.07%) ⬇️
e2e-api 44.99% <ø> (+1.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gabriellsh gabriellsh force-pushed the feat/callHistoryCore branch 4 times, most recently from baa16bd to 3479327 Compare December 17, 2025 20:36
@gabriellsh gabriellsh marked this pull request as ready for review December 18, 2025 15:06
@gabriellsh gabriellsh requested a review from a team as a code owner December 18, 2025 15:06
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (8)
apps/meteor/client/uikit/hooks/useMessageBlockContextValue.ts (1)

58-62: Consider adding event.preventDefault() for consistency.

The videoconf-core block above (line 47) calls event.preventDefault() to prevent default browser behavior. For consistency and to avoid unintended side effects (such as form submission or link navigation), consider adding the same for the media-call-core block.

🔎 Apply this diff to add event.preventDefault():
 if (appId === 'media-call-core') {
+	event.preventDefault();
 	if (actionId === 'open-history') {
 		return openTab('media-call-history', blockId);
 	}
 }
packages/i18n/src/locales/en.i18n.json (1)

4170-4177: Optional: confirm reuse and punctuation for generic Please_try_again

The generic Please_try_again key is fine, but two small things you might want to double‑check:

  • Whether you really want a new generic key vs. reusing an existing “try again”/error string to reduce duplication.
  • Whether this should end with a period or match nearby short prompts (many omit trailing punctuation) for consistency.

If usage looks good in the UI, you can leave as is.

apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx (3)

24-33: Consider using enabled option instead of throwing inside queryFn.

Currently, the query throws an error when context is undefined, which triggers the error state. Using the enabled option is more idiomatic for react-query and prevents unnecessary query attempts.

🔎 Suggested improvement:
 const { data, isError, isPending } = useQuery({
   queryKey: ['call-history', context],
   queryFn: async () => {
-    if (!context) {
-      throw new Error('Call ID is required');
-    }
     return getCallHistory({ callId: context } as any); // TODO fix this type
   },
   staleTime: Infinity, // Call history should never change...
+  enabled: !!context,
 });

56-60: Consider graceful error handling instead of throwing.

If data doesn't match internal or external call history types, the component throws an error that could crash the application. Consider falling back to the error UI instead.

🔎 Suggested improvement:
 if (isExternalCallHistoryItem(data)) {
   return <MediaCallHistoryExternal onClose={closeTab} data={data} />;
 }

-throw new Error('Invalid call history item');
+// Fallback to error state for unknown data types
+return (
+  <ContextualbarDialog onClose={closeTab}>
+    <ContextualbarHeader>
+      <ContextualbarIcon name='info-circled' />
+      <ContextualbarTitle>{t('Call_info')}</ContextualbarTitle>
+      <ContextualbarClose onClick={closeTab} />
+    </ContextualbarHeader>
+    <ContextualbarEmptyContent icon='warning' title={t('Call_info_could_not_be_loaded')} subtitle={t('Please_try_again')} />
+  </ContextualbarDialog>
+);

30-30: Replace as any with proper discriminated union type for endpoint parameters.

The /v1/call-history.info endpoint accepts a discriminated union: { historyId: string; callId: never } | { callId: string; historyId: never }. Since context is guaranteed to be a string at this point (line 27-29 guard), replace the cast with as { callId: string } to maintain type safety:

return getCallHistory({ callId: context } as { callId: string });

Alternatively, allow TypeScript to infer the type if the useEndpoint generic typing properly resolves the discriminated union through the Endpoints interface.

apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts (1)

1-1: Remove commented-out code.

Commented-out type definition should be removed per coding guidelines.

-// type HistoryActions = 'voiceCall' | 'videoCall' | 'jumpToMessage' | 'directMessage' | 'userInfo';
-
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx (1)

36-46: Consider more granular memoization dependencies.

Using [data] as dependency means any change to the data object triggers recalculation. Consider using specific fields if the data object reference changes frequently but the relevant fields remain the same.

🔎 Suggested improvement:
-const contact = useMemo(() => getContact(data.item, data.call), [data]);
+const contact = useMemo(() => getContact(data.item, data.call), [data.item, data.call]);
 const historyData = useMemo(() => {
   return {
     callId: data.call._id,
     direction: data.item.direction,
     duration: data.item.duration,
     startedAt: new Date(data.item.ts),
     state: data.item.state,
   };
-}, [data]);
+}, [data.call._id, data.item.direction, data.item.duration, data.item.ts, data.item.state]);
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx (1)

29-29: Consider optimizing the contact dependency array.

The contact memo depends on [data] but only accesses data.item. Using [data.item] would prevent unnecessary re-computation when other parts of data change.

🔎 View suggested change:
-	const contact = useMemo(() => getContact(data.item), [data]);
+	const contact = useMemo(() => getContact(data.item), [data.item]);
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 73d9eb2 and b2c3873.

📒 Files selected for processing (8)
  • apps/meteor/client/uikit/hooks/useMessageBlockContextValue.ts (3 hunks)
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx (1 hunks)
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx (1 hunks)
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx (1 hunks)
  • apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts (1 hunks)
  • apps/meteor/client/views/room/providers/RoomToolboxProvider.tsx (3 hunks)
  • apps/meteor/client/views/room/providers/hooks/useCoreRoomRoutes.ts (1 hunks)
  • packages/i18n/src/locales/en.i18n.json (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{ts,tsx,js}

📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)

**/*.{ts,tsx,js}: Write concise, technical TypeScript/JavaScript with accurate typing in Playwright tests
Avoid code comments in the implementation

Files:

  • apps/meteor/client/uikit/hooks/useMessageBlockContextValue.ts
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx
  • apps/meteor/client/views/room/providers/RoomToolboxProvider.tsx
  • apps/meteor/client/views/room/providers/hooks/useCoreRoomRoutes.ts
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx
  • apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx
🧠 Learnings (4)
📓 Common learnings
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 37419
File: apps/meteor/server/services/media-call/service.ts:141-141
Timestamp: 2025-11-19T18:20:37.116Z
Learning: In apps/meteor/server/services/media-call/service.ts, the sendHistoryMessage method should use call.caller.id or call.createdBy?.id as the message author, not call.transferredBy?.id. Even for transferred calls, the message should appear in the DM between the two users who are calling each other, not sent by the person who transferred the call.
📚 Learning: 2025-10-28T16:53:42.761Z
Learnt from: ricardogarim
Repo: RocketChat/Rocket.Chat PR: 37205
File: ee/packages/federation-matrix/src/FederationMatrix.ts:296-301
Timestamp: 2025-10-28T16:53:42.761Z
Learning: In the Rocket.Chat federation-matrix integration (ee/packages/federation-matrix/), the createRoom method from rocket.chat/federation-sdk will support a 4-argument signature (userId, roomName, visibility, displayName) in newer versions. Code using this 4-argument call is forward-compatible with planned library updates and should not be flagged as an error.

Applied to files:

  • apps/meteor/client/uikit/hooks/useMessageBlockContextValue.ts
📚 Learning: 2025-11-19T18:20:37.116Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 37419
File: apps/meteor/server/services/media-call/service.ts:141-141
Timestamp: 2025-11-19T18:20:37.116Z
Learning: In apps/meteor/server/services/media-call/service.ts, the sendHistoryMessage method should use call.caller.id or call.createdBy?.id as the message author, not call.transferredBy?.id. Even for transferred calls, the message should appear in the DM between the two users who are calling each other, not sent by the person who transferred the call.

Applied to files:

  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx
  • apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts
  • apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx
📚 Learning: 2025-11-19T18:20:07.720Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 37419
File: packages/i18n/src/locales/en.i18n.json:918-921
Timestamp: 2025-11-19T18:20:07.720Z
Learning: Repo: RocketChat/Rocket.Chat — i18n/formatting
Learning: This repository uses a custom message formatting parser in UI blocks/messages; do not assume standard Markdown rules. For keys like Call_ended_bold, Call_not_answered_bold, Call_failed_bold, and Call_transferred_bold in packages/i18n/src/locales/en.i18n.json, retain the existing single-asterisk emphasis unless maintainers request otherwise.

Applied to files:

  • packages/i18n/src/locales/en.i18n.json
🧬 Code graph analysis (6)
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx (2)
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx (1)
  • isInternalCallHistoryItem (17-22)
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx (1)
  • isExternalCallHistoryItem (21-26)
apps/meteor/client/views/room/providers/RoomToolboxProvider.tsx (1)
apps/meteor/client/views/room/providers/hooks/useCoreRoomRoutes.ts (1)
  • useCoreRoomRoutes (17-19)
apps/meteor/client/views/room/providers/hooks/useCoreRoomRoutes.ts (1)
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryContextualbar.tsx (1)
  • MediaCallHistoryContextualbar (17-61)
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx (4)
packages/core-typings/src/ICallHistoryItem.ts (2)
  • IInternalMediaCallHistoryItem (37-43)
  • CallHistoryItem (51-51)
packages/core-typings/src/mediaCalls/IMediaCall.ts (1)
  • IMediaCall (35-68)
apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts (1)
  • useMediaCallInternalHistoryActions (21-75)
packages/ui-voip/src/index.ts (1)
  • CallHistoryContextualBar (7-7)
apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts (2)
packages/ui-contexts/src/index.ts (3)
  • useRouter (63-63)
  • useCurrentRoutePath (32-32)
  • useUserAvatarPath (84-84)
packages/ui-contexts/src/RouterContext.ts (1)
  • LocationPathname (16-16)
apps/meteor/client/views/mediaCallHistory/MediaCallHistoryExternal.tsx (2)
packages/core-typings/src/ICallHistoryItem.ts (2)
  • IExternalMediaCallHistoryItem (45-49)
  • CallHistoryItem (51-51)
packages/core-typings/src/mediaCalls/IMediaCall.ts (1)
  • IMediaCall (35-68)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: 🚢 Build Docker (arm64, account-service, presence-service, stream-hub-service, omnichannel-tran...
  • GitHub Check: 🚢 Build Docker (amd64, account-service, presence-service, stream-hub-service, omnichannel-tran...
  • GitHub Check: 🚢 Build Docker (amd64, authorization-service, queue-worker-service, ddp-streamer-service, cove...
  • GitHub Check: 🚢 Build Docker (amd64, rocketchat, coverage)
  • GitHub Check: 🚢 Build Docker (arm64, authorization-service, queue-worker-service, ddp-streamer-service, cove...
  • GitHub Check: 🚢 Build Docker (arm64, rocketchat, coverage)
🔇 Additional comments (7)
apps/meteor/client/uikit/hooks/useMessageBlockContextValue.ts (1)

4-4: LGTM: Clean integration with room toolbox.

The import and hook usage are correctly implemented to enable opening the media call history tab.

Also applies to: 42-42

packages/i18n/src/locales/en.i18n.json (1)

984-1000: Call info error string is well‑named and placed

Call_info_could_not_be_loaded fits the existing naming pattern in the Call_* block, the wording is clear, and the change does not touch the special Call_*_bold formatting keys mentioned in prior i18n guidance. No changes needed here.

apps/meteor/client/views/room/providers/hooks/useCoreRoomRoutes.ts (1)

5-11: LGTM!

The route configuration is well-structured with appropriate id, title, component reference, icon, and group restrictions.

apps/meteor/client/views/room/providers/RoomToolboxProvider.tsx (2)

74-75: LGTM!

Good clarifying comment explaining the distinction between core routes (no header button) and core actions.


91-102: LGTM!

The tab resolution logic correctly prioritizes core routes before falling back to actions, and the memoization dependencies are properly updated.

apps/meteor/client/views/mediaCallHistory/useMediaCallInternalHistoryActions.ts (1)

21-74: LGTM!

The hook is well-structured with proper use of useEffectEvent for stable callbacks, appropriate guards for optional values, and correct memoization of the returned actions object.

apps/meteor/client/views/mediaCallHistory/MediaCallHistoryInternal.tsx (1)

17-22: LGTM!

The type guard correctly narrows the data type by checking for the external property and its boolean value.

gabriellsh and others added 2 commits December 18, 2025 15:02
…HistoryActions.ts

Co-authored-by: Douglas Fabris <devfabris@gmail.com>
@gabriellsh gabriellsh added the stat: QA assured Means it has been tested and approved by a company insider label Dec 18, 2025
@dionisio-bot dionisio-bot bot added the stat: ready to merge PR tested and approved waiting for merge label Dec 18, 2025
@gabriellsh gabriellsh changed the title feat: Implement Call History contextual bar inside rooms feat: Implement Call history contextual bar inside rooms Dec 18, 2025
@gabriellsh gabriellsh changed the title feat: Implement Call history contextual bar inside rooms feat: Implement Call History contextual bar inside rooms Dec 18, 2025
@ggazzo ggazzo merged commit a909ab6 into develop Dec 18, 2025
90 of 92 checks passed
@ggazzo ggazzo deleted the feat/callHistoryCore branch December 18, 2025 22:19
gaolin1 pushed a commit to gaolin1/medsense.webchat that referenced this pull request Jan 6, 2026
@dougfabris dougfabris modified the milestones: 7.14.0, 8.0.0 Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants