feat: integrate SIP calls with DM rooms#40752
Conversation
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
|
WalkthroughThis PR extends the media-calls contact system by adding user identity ( ChangesMedia Calls Contact Identity & UI
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Stopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a 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. Comment |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #40752 +/- ##
===========================================
- Coverage 69.76% 69.73% -0.03%
===========================================
Files 3327 3327
Lines 123134 123145 +11
Branches 21987 21923 -64
===========================================
- Hits 85904 85880 -24
- Misses 33869 33910 +41
+ Partials 3361 3355 -6
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
coderabbitai
Bot
added
the
type: feature
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (2)
packages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.ts (1)
28-34: ⚡ Quick winConsider adding comments to explain uid-based routing logic.
The routing logic at line 29 implements a non-obvious pattern: SIP contacts with
uidare routed to internal derivation (user-based) while SIP contacts withoutuidgo to external derivation (phone-number-based). This distinction is central to the DM-SIP integration feature but isn't documented in the code.📋 Suggested documentation
export const derivePeerInfoFromInstanceContact = (contact: CallContact) => { + // Route SIP contacts without uid to external (phone number-based) derivation. + // SIP contacts with uid represent user-backed contacts and use internal (user-based) derivation. if (contact.type === 'sip' && !contact.uid) { return deriveExternalPeerInfoFromInstanceContact(contact); }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.ts` around lines 28 - 34, Add a concise comment above derivePeerInfoFromInstanceContact explaining the uid-based routing: clarify that when contact.type === 'sip' and contact.uid is absent the function routes to deriveExternalPeerInfoFromInstanceContact (treat as external phone-number-based SIP peers), whereas SIP contacts with a uid and all non-SIP contacts are routed to deriveInternalPeerInfoFromInstanceContact (treat as internal/user-based routing); reference the CallContact shape and the uid field in the comment so future readers understand this DM-SIP integration distinction.apps/meteor/tests/e2e/voice-calls-ee.spec.ts (1)
61-67: 💤 Low valueConsider incorporating comment explanations into test.step descriptions.
The inline comments on lines 61 and 67 explain the navigation flow and rationale, which is valuable context. However, as per coding guidelines, TypeScript files should avoid inline comments. Consider moving this explanation into a more descriptive
test.step()description or splitting into separate steps for better clarity.For example:
await test.step('open voice call widget with user2', async () => { await user1.poHomeChannel.navbar.openChat('user2'); await expect(user1.poHomeChannel.composer.inputMessage).toBeVisible(); await user1.poHomeChannel.content.btnVoiceCall.click(); }); await test.step('navigate to home to establish call', async () => { await user1.poHomeChannel.navbar.btnHome.click(); await user1.poHomeChannel.waitForHome(); await user1.poHomeChannel.voiceCalls.initiateCall(); });This approach maintains consistency with the transfer test scenario (lines 118-125) which follows a similar pattern without inline comments.
As per coding guidelines, TypeScript files should avoid code comments in the implementation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/meteor/tests/e2e/voice-calls-ee.spec.ts` around lines 61 - 67, Convert the inline comments into explicit test.step blocks: wrap the sequence that opens the DM and clicks the voice call button (calls to user1.poHomeChannel.navbar.openChat, user1.poHomeChannel.composer.inputMessage, user1.poHomeChannel.content.btnVoiceCall) in a test.step with a descriptive title like "open voice call widget with user2", and wrap the navigation back to home (user1.poHomeChannel.navbar.btnHome) plus any follow-up actions (e.g., user1.poHomeChannel.waitForHome and user1.poHomeChannel.voiceCalls.initiateCall) in a second test.step titled like "navigate to home to establish call"; ensure each step replaces the comment and preserves existing awaits and expectations.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/meteor/client/views/room/body/MediaCallRoom.tsx`:
- Around line 11-23: The isSameList function currently misses a length check
causing subset arrays to be considered equal; update isSameList to first compare
list1.length and list2.length and return false if they differ, then keep a
single loop (e.g., iterate over list1 and ensure list2.includes(item)) or switch
to Set-based equality to avoid duplicate/ordering issues; reference the
isSameList function and remove the redundant second loop after adding the length
check.
In `@apps/meteor/tests/e2e/voice-calls-ee.spec.ts`:
- Line 122: After clicking user1.poHomeChannel.navbar.btnHome.click(), wait for
the home page to be visible before calling initiateCall to avoid races; add an
await on a home-page visibility assertion (e.g., await
user1.poHomeChannel.home.waitForDisplayed() or the appropriate page/component
selector on the PO) and only then call user1.clientA.initiateCall(), ensuring
the await is added so initiateCall runs after the home page is rendered.
- Line 65: After the click on user1.poHomeChannel.navbar.btnHome, add an
explicit await that waits for the home page UI to be visible before calling
initiateCall(); for example, await a stable home-root selector via
user1.page.waitForSelector(...) or call a PO helper like
user1.poHome.waitForVisible(), then proceed to initiateCall()—do not use
hardcoded timeouts.
In `@packages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.ts`:
- Around line 15-26: The thrown Error in
deriveInternalPeerInfoFromInstanceContact is misleading because the function
rejects only when contact.type !== 'user' AND no contact.uid; update the error
message to accurately reflect that (e.g., "Contact must be a user or have a
uid") so it describes the actual validation (check of contact.type and
contact.uid) before returning the derived object.
---
Nitpick comments:
In `@apps/meteor/tests/e2e/voice-calls-ee.spec.ts`:
- Around line 61-67: Convert the inline comments into explicit test.step blocks:
wrap the sequence that opens the DM and clicks the voice call button (calls to
user1.poHomeChannel.navbar.openChat, user1.poHomeChannel.composer.inputMessage,
user1.poHomeChannel.content.btnVoiceCall) in a test.step with a descriptive
title like "open voice call widget with user2", and wrap the navigation back to
home (user1.poHomeChannel.navbar.btnHome) plus any follow-up actions (e.g.,
user1.poHomeChannel.waitForHome and user1.poHomeChannel.voiceCalls.initiateCall)
in a second test.step titled like "navigate to home to establish call"; ensure
each step replaces the comment and preserves existing awaits and expectations.
In `@packages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.ts`:
- Around line 28-34: Add a concise comment above
derivePeerInfoFromInstanceContact explaining the uid-based routing: clarify that
when contact.type === 'sip' and contact.uid is absent the function routes to
deriveExternalPeerInfoFromInstanceContact (treat as external phone-number-based
SIP peers), whereas SIP contacts with a uid and all non-SIP contacts are routed
to deriveInternalPeerInfoFromInstanceContact (treat as internal/user-based
routing); reference the CallContact shape and the uid field in the comment so
future readers understand this DM-SIP integration distinction.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 722df00b-7928-47d7-a21d-e4f8c8fd38c8
📒 Files selected for processing (7)
apps/meteor/client/views/room/body/MediaCallRoom.tsxapps/meteor/tests/e2e/voice-calls-ee.spec.tsee/packages/media-calls/src/server/CastDirector.tspackages/core-typings/src/mediaCalls/IMediaCall.tspackages/media-signaling/src/definition/call/common.tspackages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.tspackages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsx
📜 Review details
⏰ 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). (2)
- GitHub Check: cubic · AI code reviewer
- GitHub Check: Hacktron Security Check
🧰 Additional context used
📓 Path-based instructions (4)
**/*.{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:
packages/media-signaling/src/definition/call/common.tspackages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsxee/packages/media-calls/src/server/CastDirector.tspackages/core-typings/src/mediaCalls/IMediaCall.tsapps/meteor/tests/e2e/voice-calls-ee.spec.tspackages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.tsapps/meteor/client/views/room/body/MediaCallRoom.tsx
**/*.spec.ts
📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)
**/*.spec.ts: Use descriptive test names that clearly communicate expected behavior in Playwright tests
Use.spec.tsextension for test files (e.g.,login.spec.ts)
Files:
apps/meteor/tests/e2e/voice-calls-ee.spec.ts
apps/meteor/tests/e2e/**/*.spec.ts
📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)
apps/meteor/tests/e2e/**/*.spec.ts: All test files must be created inapps/meteor/tests/e2e/directory
Avoid usingpage.locator()in Playwright tests - always prefer semantic locators such aspage.getByRole(),page.getByLabel(),page.getByText(), orpage.getByTitle()
Usetest.beforeAll()andtest.afterAll()for setup/teardown in Playwright tests
Usetest.step()for complex test scenarios to improve organization in Playwright tests
Group related tests in the same file
Utilize Playwright fixtures (test,page,expect) for consistency in test files
Prefer web-first assertions (toBeVisible,toHaveText, etc.) in Playwright tests
Useexpectmatchers for assertions (toEqual,toContain,toBeTruthy,toHaveLength, etc.) instead ofassertstatements in Playwright tests
Usepage.waitFor()with specific conditions instead of hardcoded timeouts in Playwright tests
Implement proper wait strategies for dynamic content in Playwright tests
Maintain test isolation between test cases in Playwright tests
Ensure clean state for each test execution in Playwright tests
Ensure tests run reliably in parallel without shared state conflicts
Files:
apps/meteor/tests/e2e/voice-calls-ee.spec.ts
apps/meteor/tests/e2e/**/*.{ts,spec.ts}
📄 CodeRabbit inference engine (.cursor/rules/playwright.mdc)
apps/meteor/tests/e2e/**/*.{ts,spec.ts}: Store commonly used locators in variables/constants for reuse
Follow Page Object Model pattern consistently in Playwright tests
Files:
apps/meteor/tests/e2e/voice-calls-ee.spec.ts
🧠 Learnings (9)
📚 Learning: 2026-02-26T19:25:44.063Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/providers/useMediaSession.ts:192-192
Timestamp: 2026-02-26T19:25:44.063Z
Learning: In the Rocket.Chat repository, do not reference Biome lint rules in code review feedback. Biome is not used even if biome.json exists; only reference Biome rules if there is explicit, project-wide usage documented. For TypeScript files, review lint implications without Biome guidance unless the project enables Biome rules.
Applied to files:
packages/media-signaling/src/definition/call/common.tsee/packages/media-calls/src/server/CastDirector.tspackages/core-typings/src/mediaCalls/IMediaCall.tsapps/meteor/tests/e2e/voice-calls-ee.spec.tspackages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.ts
📚 Learning: 2026-02-26T19:25:44.063Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/providers/useMediaSession.ts:192-192
Timestamp: 2026-02-26T19:25:44.063Z
Learning: In this repository (RocketChat/Rocket.Chat), Biome lint rules are not used even if a biome.json exists. When reviewing TypeScript files (e.g., packages/ui-voip/src/providers/useMediaSession.ts), ensure lint suggestions do not reference Biome-specific rules. Rely on general ESLint/TypeScript lint rules and project conventions instead.
Applied to files:
packages/media-signaling/src/definition/call/common.tsee/packages/media-calls/src/server/CastDirector.tspackages/core-typings/src/mediaCalls/IMediaCall.tsapps/meteor/tests/e2e/voice-calls-ee.spec.tspackages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.ts
📚 Learning: 2026-05-06T12:21:44.083Z
Learnt from: juliajforesti
Repo: RocketChat/Rocket.Chat PR: 40256
File: apps/meteor/client/components/CreateDiscussion/CreateDiscussion.tsx:121-149
Timestamp: 2026-05-06T12:21:44.083Z
Learning: Field wrappers in rocket.chat/fuselage-forms (Field, FieldLabel, FieldRow, FieldError, FieldHint) auto-create htmlFor/id associations, aria-describedby, and role="alert" for errors. Do not manually set htmlFor, id, aria-describedby, or role attributes when using these wrappers. This automatic wiring does not apply to plain rocket.chat/fuselage components, which require explicit ID wiring per the accessibility docs. In code reviews, prefer using fuselage-forms wrappers for form fields and verify there is no unnecessary manual ID/aria wiring in files that use these wrappers. If a component uses plain fuselage components, ensure proper id wiring as per docs.
Applied to files:
packages/media-signaling/src/definition/call/common.tspackages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsxee/packages/media-calls/src/server/CastDirector.tspackages/core-typings/src/mediaCalls/IMediaCall.tsapps/meteor/tests/e2e/voice-calls-ee.spec.tspackages/ui-voip/src/utils/derivePeerInfoFromInstanceContact.tsapps/meteor/client/views/room/body/MediaCallRoom.tsx
📚 Learning: 2026-02-26T19:22:29.385Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 38778
File: packages/ui-voip/src/views/CallHistoryContextualbar/CallHistoryActions.tsx:40-40
Timestamp: 2026-02-26T19:22:29.385Z
Learning: For TSX files in the UI VOIP package, ensure that when a media session state is 'unavailable', the voiceCall action is excluded from the actions object passed to CallHistoryActions so it does not render in the menu. This filtering should occur upstream (before getItems is called) to avoid tooltips or UI hints for unavailable actions. If there are multiple actions with availability states, implement a centralized helper to filter actions based on session state.
Applied to files:
packages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsx
📚 Learning: 2026-05-05T12:34:29.042Z
Learnt from: gabriellsh
Repo: RocketChat/Rocket.Chat PR: 40331
File: packages/ui-voip/src/views/MediaCallWidget/OngoingCallWithScreen.tsx:69-69
Timestamp: 2026-05-05T12:34:29.042Z
Learning: In Rocket.Chat’s `packages/ui-voip` UI (e.g., media/call widgets), voice/media calls are only supported in Direct Message (DM) rooms. Rocket.Chat models a DM as a “room” with exactly two participants, so handlers like `onClickDirectMessage` are the correct destination—even when the UI text/element says “Open in room” (e.g., on the shared screen card/`StreamCard`). During review, don’t flag a “DM vs room” mismatch for these cases; they intentionally map to the same destination.
Applied to files:
packages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsx
📚 Learning: 2026-03-27T14:52:56.865Z
Learnt from: dougfabris
Repo: RocketChat/Rocket.Chat PR: 39892
File: apps/meteor/client/views/room/contextualBar/Threads/Thread.tsx:150-155
Timestamp: 2026-03-27T14:52:56.865Z
Learning: In Rocket.Chat, there are two different `ModalBackdrop` components with different prop APIs. During review, confirm the import source: (1) `rocket.chat/fuselage` `ModalBackdrop` uses `ModalBackdropProps` based on `BoxProps` (so it supports `onClick` and other Box/DOM props) and does not have an `onDismiss` prop; (2) `rocket.chat/ui-client` `ModalBackdrop` uses a narrower props interface like `{ children?: ReactNode; onDismiss?: () => void }` and handles Escape keypress and outside mouse-up, and it does not forward arbitrary DOM props such as `onClick`. Flag mismatched props (e.g., `onDismiss` passed to the fuselage component or `onClick` passed to the ui-client component) and ensure the usage matches the correct component being imported.
Applied to files:
packages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsxapps/meteor/client/views/room/body/MediaCallRoom.tsx
📚 Learning: 2026-02-24T19:22:48.358Z
Learnt from: juliajforesti
Repo: RocketChat/Rocket.Chat PR: 38493
File: apps/meteor/tests/e2e/omnichannel/omnichannel-send-pdf-transcript.spec.ts:66-67
Timestamp: 2026-02-24T19:22:48.358Z
Learning: In Playwright end-to-end tests (e.g., under apps/meteor/tests/e2e/...), prefer locating elements by translated text (getByText) and ARIA roles (getByRole) over data-qa attributes. If translation values change, update the corresponding test locators accordingly. Never use data-qa locators. This guideline applies to all Playwright e2e test specs in the repository and helps keep tests robust to UI text changes and accessible semantics.
Applied to files:
apps/meteor/tests/e2e/voice-calls-ee.spec.ts
📚 Learning: 2026-02-24T19:39:42.247Z
Learnt from: juliajforesti
Repo: RocketChat/Rocket.Chat PR: 38493
File: apps/meteor/tests/e2e/page-objects/fragments/message.ts:7-7
Timestamp: 2026-02-24T19:39:42.247Z
Learning: In RocketChat e2e tests, avoid using data-qa attributes to locate elements. Prefer semantic locators such as getByRole, getByLabel, getByText, getByTitle and ARIA-based selectors. Apply this rule to all TypeScript files under apps/meteor/tests/e2e to improve test reliability, accessibility, and maintainability.
Applied to files:
apps/meteor/tests/e2e/voice-calls-ee.spec.ts
📚 Learning: 2026-03-06T18:10:15.268Z
Learnt from: tassoevan
Repo: RocketChat/Rocket.Chat PR: 39397
File: packages/gazzodown/src/code/CodeBlock.spec.tsx:47-68
Timestamp: 2026-03-06T18:10:15.268Z
Learning: In tests (especially those using testing-library/dom/jsdom) for Rocket.Chat components, the HTML <code> element has an implicit ARIA role of 'code'. Therefore, screen.getByRole('code') or screen.findByRole('code') will locate <code> elements even without a role attribute. Do not flag findByRole('code') as invalid in reviews; prefer using the implicit role instead of adding role="code" unless necessary for accessibility.
Applied to files:
apps/meteor/tests/e2e/voice-calls-ee.spec.ts
🔇 Additional comments (5)
packages/core-typings/src/mediaCalls/IMediaCall.ts (1)
23-23: LGTM!packages/media-signaling/src/definition/call/common.ts (1)
8-8: LGTM!ee/packages/media-calls/src/server/CastDirector.ts (1)
123-123: LGTM!apps/meteor/client/views/room/body/MediaCallRoom.tsx (1)
3-3: LGTM!Also applies to: 25-37, 46-49
packages/ui-voip/src/views/MediaCallRoomSection/MediaCallRoomSection.tsx (1)
20-20: LGTM!Also applies to: 82-89, 147-164
| await user1.poHomeChannel.navbar.openChat('user2'); | ||
| await expect(user1.poHomeChannel.composer.inputMessage).toBeVisible(); | ||
| await user1.poHomeChannel.content.btnVoiceCall.click(); | ||
| await user1.poHomeChannel.navbar.btnHome.click(); |
There was a problem hiding this comment.
Wait for home page to be visible after navigation.
After clicking btnHome, the test should wait for the home page to render before initiating the call. Without an explicit wait, initiateCall() on line 68 may execute before the home UI is ready, causing flaky test failures.
Based on learnings, prefer page.waitFor() with specific conditions instead of hardcoded timeouts in Playwright tests.
🔧 Proposed fix to add home page wait
await user1.poHomeChannel.content.btnVoiceCall.click();
await user1.poHomeChannel.navbar.btnHome.click();
+await user1.poHomeChannel.waitForHome();
// Initiate the call from the home screen so the DM doesn't affect how its rendered📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| await user1.poHomeChannel.navbar.btnHome.click(); | |
| await user1.poHomeChannel.navbar.btnHome.click(); | |
| await user1.poHomeChannel.waitForHome(); |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/meteor/tests/e2e/voice-calls-ee.spec.ts` at line 65, After the click on
user1.poHomeChannel.navbar.btnHome, add an explicit await that waits for the
home page UI to be visible before calling initiateCall(); for example, await a
stable home-root selector via user1.page.waitForSelector(...) or call a PO
helper like user1.poHome.waitForVisible(), then proceed to initiateCall()—do not
use hardcoded timeouts.
| await user1.poHomeChannel.navbar.openChat('user2'); | ||
| await expect(user1.poHomeChannel.composer.inputMessage).toBeVisible(); | ||
| await user1.poHomeChannel.content.btnVoiceCall.click(); | ||
| await user1.poHomeChannel.navbar.btnHome.click(); |
There was a problem hiding this comment.
Wait for home page to be visible after navigation.
Similar to line 65, after clicking btnHome, the test should wait for the home page to render before calling initiateCall() on line 123. This prevents potential race conditions and test flakiness.
🔧 Proposed fix to add home page wait
await user1.poHomeChannel.content.btnVoiceCall.click();
await user1.poHomeChannel.navbar.btnHome.click();
+await user1.poHomeChannel.waitForHome();
await user1.poHomeChannel.voiceCalls.initiateCall();🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/meteor/tests/e2e/voice-calls-ee.spec.ts` at line 122, After clicking
user1.poHomeChannel.navbar.btnHome.click(), wait for the home page to be visible
before calling initiateCall to avoid races; add an await on a home-page
visibility assertion (e.g., await user1.poHomeChannel.home.waitForDisplayed() or
the appropriate page/component selector on the PO) and only then call
user1.clientA.initiateCall(), ensuring the await is added so initiateCall runs
after the home page is rendered.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 7 files
Tip: cubic used a learning from your PR history. Let your coding agent read cubic learnings directly with the cubic MCP.
Re-trigger cubic
1 participant
Proposed changes (including videos or screenshots)
Issue(s)
DMV-32
Steps to test or reproduce
Further comments
Summary by CodeRabbit
Release Notes