cleanup an rename compatibility mode

This commit is contained in:
Timo K
2026-01-07 16:08:20 +01:00
parent d814f60f23
commit 75fca3108a
6 changed files with 13 additions and 7 deletions

View File

@@ -235,7 +235,7 @@ const mockLegacyRingEvent = {} as { event_id: string } & ICallNotifyContent;
describe.each([
[MatrixRTCMode.Legacy],
[MatrixRTCMode.Compatibil],
[MatrixRTCMode.Compatibility],
[MatrixRTCMode.Matrix_2_0],
])("CallViewModel (%s mode)", (mode) => {
const withCallViewModel = withCallViewModelInMode(mode);

View File

@@ -429,7 +429,11 @@ export function createCallViewModel$(
};
const useOldJwtEndpoint$ = scope.behavior(
matrixRTCMode$.pipe(map((v) => v !== MatrixRTCMode.Matrix_2_0)),
matrixRTCMode$.pipe(
map(
(v) => v === MatrixRTCMode.Legacy || v === MatrixRTCMode.Compatibility,
),
),
);
const localTransport$ = createLocalTransport$({

View File

@@ -711,7 +711,9 @@ export function enterRTCSession(
const useDeviceSessionMemberEvents =
features?.feature_use_device_session_member_events;
const { sendNotificationType: notificationType, callIntent } = getUrlParams();
const multiSFU = matrixRTCMode !== MatrixRTCMode.Legacy;
const multiSFU =
matrixRTCMode === MatrixRTCMode.Compatibility ||
matrixRTCMode === MatrixRTCMode.Matrix_2_0;
// Multi-sfu does not need a preferred foci list. just the focus that is actually used.
// TODO where/how do we track errors originating from the ongoing rtcSession?
rtcSession.joinRTCSession(