@ethora/chat-component 26.6.1 → 26.6.2

package/dist/main.js

@@ -1,4 +1,4 @@
-import { m as e, R as o, C as t, M as p, n as r, X as u, o as n, p as d, q as h, t as i, v as y, w as I, x as T, y as g, z as l, D as C, E as c, F as m } from "./main-L70Zd5ai.js";
+import { m as e, R as o, C as t, M as p, n as r, X as u, o as n, p as d, q as h, t as i, v as y, w as I, x as T, y as g, z as l, D as C, E as c, F as m } from "./main-BHPCoRk-.js";
 export {
   e as AuthTestIds,
   o as Chat,

package/dist/roomStore/chatSettingsSlice.d.ts

@@ -8,12 +8,36 @@ interface ChatState {
     selectedUser?: IUser;
     activeFile?: ModalFile;
     langSource?: Iso639_1Codes;
+    /**
+     * Whether THIS reader's own outgoing messages get tagged with
+     * `<translate source="xx"/>` (see sendTextMessageWithTranslateTag) so
+     * translations can be generated for them. Defaults to true so existing
+     * hosts that already set `config.translates.enabled` see no change
+     * until a reader explicitly opts out via the language-selector toggle.
+     *
+     * Turning this off does NOT untag anything already sent - a message
+     * ships with whatever tag was active at send time, permanently. Turning
+     * it back on only affects messages sent from that point forward. Same
+     * asymmetry the other direction: turning it on doesn't retroactively
+     * tag old messages either - see the disclaimer surfaced next to the
+     * toggle in LanguageSelectorModal.
+     */
+    translateSendEnabled?: boolean;
+    /**
+     * Reader's own auto/manual pick from the language-selector modal's
+     * switcher. Undefined means "never touched it" - falls back to
+     * `config.translates.mode` (see resolveTranslateMode). Ignored entirely
+     * when the host sets `config.translates.forceType: true`, which is also
+     * why the switcher itself doesn't render in that case - nothing should
+     * ever write here that a host has pinned.
+     */
+    translateMode?: 'auto' | 'manual';
 }
 export declare const setUser: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<User, "chatSettingStore/setUser">, setConfig: import('@reduxjs/toolkit').ActionCreatorWithNonInferrablePayload<"chatSettingStore/setConfig">, refreshTokens: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     token: string;
     refreshToken: string;
 }, "chatSettingStore/refreshTokens">, logout: import('@reduxjs/toolkit').ActionCreatorWithoutPayload<"chatSettingStore/logout">, setActiveModal: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<string, "chatSettingStore/setActiveModal">, setDeleteModal: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<DeleteModal, "chatSettingStore/setDeleteModal">, setSelectedUser: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<IUser, "chatSettingStore/setSelectedUser">, updateUser: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     updates: Partial<User>;
-}, "chatSettingStore/updateUser">, setActiveFile: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<ModalFile, "chatSettingStore/setActiveFile">, setLangSource: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<Iso639_1Codes, "chatSettingStore/setLangSource">;
+}, "chatSettingStore/updateUser">, setActiveFile: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<ModalFile, "chatSettingStore/setActiveFile">, setLangSource: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<Iso639_1Codes, "chatSettingStore/setLangSource">, setTranslateSendEnabled: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<boolean, "chatSettingStore/setTranslateSendEnabled">, setTranslateMode: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<"auto" | "manual", "chatSettingStore/setTranslateMode">;
 declare const _default: import('redux').Reducer<ChatState>;
 export default _default;

package/dist/roomStore/index.d.ts

@@ -9,6 +9,9 @@ export declare const ENCRYPTION_INFLATION_FACTOR = 1.4;
 export declare const getRoomActivityTimestamp: (room: IRoom) => number;
 export declare const compactMessageForPersist: (message: IMessage) => IMessage;
 export declare const optimizePersistedRooms: (rooms: Record<string, IRoom>, charBudget?: number) => Record<string, IRoom>;
+export declare const compactUsersSetForPersist: (usersSet: Record<string, any>) => Record<string, any>;
+/** Puts back what compactUsersSetForPersist folded into the key. */
+export declare const restoreUsersSetForRehydrate: (usersSet: Record<string, any>) => Record<string, any>;
 export declare const limitMessagesTransform: import('redux-persist').Transform<any, any, Record<string, any>, Record<string, any>>;
 export declare const scrubSensitiveChatStateTransform: import('redux-persist').Transform<any, any, Record<string, any>, Record<string, any>>;
 export declare const sanitizeRoomsStateTransform: import('redux-persist').Transform<any, any, Record<string, any>, Record<string, any>>;

package/dist/types/models/config.model.d.ts

@@ -223,43 +223,63 @@ export interface IConfig {
         enabled: boolean;
         translations?: Iso639_1Codes;
         /**
-         * 'auto' shows the translation inline automatically (legacy behaviour).
-         * 'on-demand' shows a "Translate" link the reader clicks (LinkedIn-style),
-         * then renders the result inline with a "Show original" toggle. Default 'auto'.
-         */
-        mode?: 'auto' | 'on-demand';
-        /**
-         * Locales a message is pre-translated into BEFORE it is sent (e.g.
-         * ["en-CA", "fr-CA", "es-US"]). The sender calls the translation service
-         * (see `endpoint`) and embeds the result in the stanza as
-         * `<translations value='...'/>`, so every recipient receives the message
-         * already translated and renders it with the existing parser - no
-         * ejabberd module needed.
+         * 'auto' shows the translation inline automatically. 'manual' shows a
+         * "Translate" link the reader clicks (LinkedIn-style), then renders the
+         * result inline with a "Show original" toggle. Default 'auto'.
          *
-         * Keep this to the locales actually present in the room: every extra target
-         * is one more translation shipped per message. Leave empty to disable
-         * pre-translation (the on-demand `onTranslate` path still works).
+         * Neither mode calls any translation service - both only ever display
+         * `message.translations`, whatever arrived attached to the stanza (see
+         * `readerLocale` below for how a message gets translated in the first
+         * place). This is purely a display choice: show it immediately, or let
+         * the reader ask for it.
          */
-        targets?: string[];
+        mode?: 'auto' | 'manual';
         /**
-         * Translation service URL for pre-translation (GET ?source=&text=,
-         * responding `{translates:[{translatedText, language, languageName}]}`).
-         * Defaults to Ethora's hosted service; point it at your own deployment
-         * for self-hosted setups.
+         * Pins `mode` as fixed host policy. When true, the language-selector
+         * modal's auto/manual switcher does not render at all, and the reader
+         * has no way to override `mode` - it's always whatever the host set.
+         * Defaults to false: the reader can flip between auto and manual
+         * themselves via the switcher, which then wins over `mode` (the host's
+         * declared default, used until the reader touches it).
          */
-        endpoint?: string;
+        forceType?: boolean;
         /**
          * Reader's full locale (BCP-47, e.g. "fr-CA"). Falls back to
          * `config.i18n.locale`. The region is passed through to `onTranslate` so
          * the service can distinguish fr-CA vs fr-FR; the Translate button
          * visibility comparison ignores the region (en-US vs en-CA => no button).
+         *
+         * This is also how a host drives the reader's language from OUTSIDE the
+         * chat component: set it (e.g. from your own app's language switcher)
+         * and pass the updated config down as a normal prop. Whenever it
+         * changes, the component syncs it into the same internal state the
+         * in-chat language picker writes to - so it drives both what a reader
+         * sees translated INTO and the source language declared on their own
+         * outgoing messages. Leave unset to let the reader manage it themselves
+         * via the picker (see `showLanguageSelector`).
          */
         readerLocale?: string;
         /**
-         * Host-provided translation function. When set, the Translate action calls
-         * this - wire it to your own endpoint (or Google / OpenAI). When omitted,
-         * the component falls back to server-provided translations parsed onto the
-         * message (`message.translations`).
+         * Shows/hides the globe-icon language picker in the chat header.
+         * Defaults to true whenever `enabled` is true. Set to false when the
+         * host manages the reader's language itself (via `readerLocale`) and
+         * an in-chat picker would just be a second, redundant control.
+         */
+        showLanguageSelector?: boolean;
+        /**
+         * Shows/hides the list of selectable languages INSIDE the picker
+         * (English/Español/...). Defaults to true. Set to false to keep only
+         * the enable/disable-translates toggle - for hosts that drive the
+         * reader's language externally via `readerLocale` and don't want a
+         * second, redundant language list, but still want the reader to control
+         * whether their own outgoing messages get tagged for translation.
+         */
+        showLanguageList?: boolean;
+        /**
+         * Host-provided translation function. When set, the manual Translate
+         * action calls this - wire it to your own service - instead of reading
+         * `message.translations`. Optional; omit to use only what already
+         * arrived over XMPP.
          */
         onTranslate?: (text: string, ctx: {
             sourceLocale?: string;

package/dist/types/models/message.model.d.ts

@@ -22,6 +22,7 @@ export interface IMessage {
     activeMessage?: boolean;
     isReply?: boolean | string;
     isDeleted?: boolean;
+    isEdited?: boolean;
     mainMessage?: string;
     reply?: IReply[];
     reaction?: Record<string, ReactionMessage>;

package/dist/utils/translateModePolicy.d.ts

@@ -0,0 +1,19 @@
+import { IConfig } from '../types/types';
+export type TranslateMode = 'auto' | 'manual';
+/**
+ * Whether the reader is allowed to pick auto vs manual themselves via the
+ * language-selector modal's switcher. `forceType: true` means the host has
+ * pinned `translates.mode` as policy - the switcher must not even render,
+ * let alone let a reader flip it.
+ */
+export declare const canReaderChooseTranslateMode: (translates?: IConfig["translates"]) => boolean;
+/**
+ * The mode actually in effect for this reader right now.
+ *
+ * `forceType` wins unconditionally - even a leftover `readerMode` from
+ * before the host turned forcing on must not leak through. Otherwise the
+ * reader's own pick (if they've touched the switcher) wins over the host's
+ * declared default, and the host's `mode` (defaulting to 'auto') is the
+ * fallback for a reader who never has.
+ */
+export declare const resolveTranslateMode: (translates?: IConfig["translates"], readerMode?: TranslateMode) => TranslateMode;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ethora/chat-component",
-  "version": "26.6.1",
+  "version": "26.6.2",
   "type": "module",
   "main": "dist/main.js",
   "types": "dist/main.d.ts",

package/public/firebase-messaging-sw.js

@@ -384,9 +384,10 @@ async function handlePush(raw = {}, source = 'push') {
   });
 
   const visible = isVisibleClients(windowClients);
+  const hasAnyClient = windowClients.length > 0;
 
   if (DEBUG) log('clients:', dumpClients(windowClients));
-  log('visibleClientExists:', visible);
+  log('visibleClientExists:', visible, 'anyClientExists:', hasAnyClient);
 
   await broadcastDebugMessage({
     source,
@@ -445,9 +446,20 @@ async function handlePush(raw = {}, source = 'push') {
     },
   };
 
-  if (!visible) {
+  // Calls: a client that's merely backgrounded (open, just not the
+  // visible/focused tab) is NOT the "nobody will hear this ring" case -
+  // VideoCallOverlay already rings its own OS notification for exactly
+  // that state (see its comment: this SW push is meant to be the
+  // fully-offline fallback). `visible` collapses "backgrounded but open"
+  // and "fully closed" into the same false, which duplicated that
+  // client-side ring every time the tab was merely hidden. Suppress on
+  // ANY open client for calls; regular messages keep the visible-only
+  // check they already had.
+  const suppress = isCall ? hasAnyClient : visible;
+
+  if (!suppress) {
     log('SHOW NOTIFICATION', {
-      reason: 'NO_VISIBLE_CLIENT',
+      reason: isCall ? 'NO_CLIENT_AT_ALL' : 'NO_VISIBLE_CLIENT',
       tag: options.tag,
       isCall,
     });
@@ -456,7 +468,7 @@ async function handlePush(raw = {}, source = 'push') {
   }
 
   log('SKIP NOTIFICATION', {
-    reason: 'VISIBLE_CLIENT',
+    reason: isCall ? 'CLIENT_OPEN_WILL_RING_ITSELF' : 'VISIBLE_CLIENT',
   });
 }