@medipha/chat 1.0.18 → 1.0.20

package/dist/shared/components/user-profile-modal.d.ts

@@ -4,10 +4,14 @@ interface UserProfileModalProps {
     onClose: () => void;
     /** Opens (or reuses) a direct conversation with this user. */
     onStartChat?: (userId: string) => void;
+    /** Badges the avatar with the owner key — set when this dialog was opened from a group
+     *  whose owner this user is. It's a per-conversation role, not a property of the account,
+     *  so it can only come from the caller that knows which group we came from. */
+    isGroupOwner?: boolean;
 }
 /** Zalo-style "Thông tin tài khoản" dialog, opened from a user avatar click: avatar on
  *  top, then contact details (họ tên, ngày sinh, email, số điện thoại) and a second
  *  group with the directory info (chi nhánh, phòng ban, chức vụ). Portals to body with
  *  the layered mask so it stacks above the member-list modal it may be opened from. */
-export declare function UserProfileModal({ userId, fallbackName, onClose, onStartChat }: UserProfileModalProps): import('react').ReactPortal;
+export declare function UserProfileModal({ userId, fallbackName, onClose, onStartChat, isGroupOwner, }: UserProfileModalProps): import('react').ReactPortal;
 export {};

package/dist/store/draftStore.d.ts

@@ -2,28 +2,14 @@ import { JSONContent } from '@tiptap/core';
 type DraftMap = Record<string, JSONContent>;
 interface DraftState {
     draftByConversation: DraftMap;
-    /** Stores (or, with `null`, discards) the unsent composer content for one conversation. */
     setDraft: (conversationId: string, doc: JSONContent | null) => void;
 }
-/** Flattens a draft doc to the one-line plain text the sidebar row previews. Mention nodes
- *  carry their display name in attrs rather than as a text child, so they need their own
- *  branch or an "@ai đó" draft would preview as an empty string. */
+/** Flattens a draft doc to the one-line plain text the sidebar row previews. */
 export declare function getDraftText(doc: JSONContent | undefined): string;
-/** Writes the pending draft snapshot out immediately — call before the tab goes away, or
- *  before handing the store over to a different account. */
+/** Writes the pending snapshot out now, skipping the debounce. */
 export declare function flushDrafts(): void;
-/**
- * Points the store at one account's drafts: flushes whatever the previous account still had
- * pending, then loads that user's own set. Called once the session's user id is known (see
- * ChatBootstrap) — signing in as someone else on the same browser therefore swaps the whole
- * map rather than leaking the first account's unsent text into the second's sidebar.
- */
+/** Swaps the loaded draft set to another account, flushing the previous one first. */
 export declare function setDraftUser(userId: string | null): void;
-/**
- * Unsent composer content, kept per conversation so switching threads (or reloading) and
- * coming back restores what was being typed — Zalo/Messenger behaviour. Scoped to the
- * signed-in user and mirrored to localStorage; a draft is dropped the moment its message is
- * actually sent.
- */
+/** Unsent composer content per conversation, scoped to the signed-in user. */
 export declare const useDraftStore: import('zustand').UseBoundStore<import('zustand').StoreApi<DraftState>>;
 export {};

package/dist/store/messageRemovalStore.d.ts

@@ -0,0 +1,21 @@
+interface Removal {
+    conversationId: string;
+    messageId: string;
+    /** Monotonic, so re-notifying the same message id still registers as a new event. */
+    token: number;
+}
+interface MessageRemovalState {
+    lastRemoval: Removal | null;
+    noteRemoval: (conversationId: string, messageId: string) => void;
+}
+/**
+ * Broadcasts "a message was just removed" to views outside the timeline (the archive, the
+ * settings media/file preview) so they can refetch.
+ *
+ * They can't rely on the `message:removed` socket event alone: a recall is issued over REST
+ * and applied locally from that response, so the person doing the recall may never see the
+ * broadcast. This store is written from the one place that handles both paths
+ * (applyRemovedMessage in conversation-detail).
+ */
+export declare const useMessageRemovalStore: import('zustand').UseBoundStore<import('zustand').StoreApi<MessageRemovalState>>;
+export {};

package/dist/store/typingStore.d.ts

@@ -1,13 +1,10 @@
 interface TypingState {
     /** conversationId -> display names currently typing there, most recent first. */
     namesByConversation: Record<string, string[]>;
-    /** Replaces the typer list for one conversation; an empty list drops the key entirely. */
     setTypingNames: (conversationId: string, names: string[]) => void;
     clearConversation: (conversationId: string) => void;
 }
-/** Mirrors the open conversation's typing state so the sidebar row can show "Đang nhập..."
- *  the same way Zalo/Messenger do. It is fed by useTypingIndicator (the single owner of the
- *  typing timers) rather than by its own socket subscription — which also means it only
- *  ever covers the conversation currently open, since the socket joins that room alone. */
+/** Typing state of the open conversation, mirrored here so its sidebar row can show it.
+ *  Fed by useTypingIndicator (which owns the typing timers), not its own subscription. */
 export declare const useTypingStore: import('zustand').UseBoundStore<import('zustand').StoreApi<TypingState>>;
 export {};