@medipha/chat 1.0.14 → 1.0.16

package/README.md

@@ -1,103 +1,103 @@
-# @medipha/chat
-
-`@medipha/chat` is an embeddable React chat module for Medic-ERP. It uses the
-ERP application's React tree, BrowserRouter, authentication, and Ant Design 4
-installation; it does not use an iframe or create a router.
-
-## Install
-
-```bash
-pnpm add @medipha/chat
-```
-
-## Mount in Medic-ERP
-
-The ERP imports the Ant Design 4 stylesheet exactly once, at its application
-entry point. The chat library deliberately does not import it.
-
-```tsx
-import 'antd/dist/antd.css';
-import { ChatModule } from '@medipha/chat';
-import '@medipha/chat/styles.css';
-
-<Route
-  path="/chat-erp/*"
-  element={
-    <ChatModule
-      accessToken={accessToken}
-      apiUrl={CHAT_API_URL}
-      socketUrl={CHAT_SOCKET_URL}
-      onUnauthorized={handleUnauthorized}
-      onNavigateOutsideChat={handleNavigateOutsideChat}
-    />
-  }
-/>;
-```
-
-The ERP must own the surrounding `BrowserRouter`. `ChatModule` adds only
-relative routes: `/chat-erp` for the conversation list and
-`/chat-erp/:conversationId` for a room.
-
-## `ChatModuleProps`
-
-| Prop                    | Required | Meaning                                                   |
-| ----------------------- | -------- | --------------------------------------------------------- |
-| `accessToken`           | Yes      | Current ERP access token used by chat API/socket clients. |
-| `apiUrl`                | Yes      | Base URL for the Chat HTTP API.                           |
-| `socketUrl`             | Yes      | Socket server URL.                                        |
-| `onUnauthorized`        | No       | ERP callback for an unauthorized chat response.           |
-| `onNavigateOutsideChat` | No       | ERP callback for navigation that leaves chat.             |
-
-Pass a new `accessToken` prop whenever ERP refreshes its credential.
-`ChatModule` updates its internal runtime context from the new prop and never
-writes a token to `localStorage` or `sessionStorage`.
-
-## Nginx SPA fallback
-
-Configure the ERP server so deep links under `/chat-erp/*` return the ERP
-application entry file:
-
-```nginx
-location / {
-  try_files $uri $uri/ /index.html;
-}
-```
-
-## Development and validation
-
-Vite 8 requires Node.js `20.19+` or `22.12+`.
-
-```bash
-pnpm install
-pnpm dev
-```
-
-`pnpm dev` opens the root development playground. It loads `ChatModule`
-directly from `src`, so library code and CSS changes use Vite HMR without a
-library build after every edit. The playground's `BrowserRouter` is
-development-only; it is not part of the published package.
-
-To validate the publishable library:
-
-```bash
-pnpm typecheck
-pnpm build
-npm pack --dry-run
-```
-
-To verify the CRA host after building the library:
-
-```bash
-cd examples/erp-host
-pnpm install
-pnpm build
-```
-
-## Publish
-
-Publish `@medipha/chat-core` before `@medipha/chat`. GitLab CI uses a masked,
-protected `NPM_TOKEN` variable with npm publish permission and runs only for a
-version tag such as `v0.1.0`. Update versions using semantic versioning: patch
-for fixes, minor for backward-compatible features, and major for breaking API
-changes. Create and push the version tag through your normal release process
-after reviewing the working tree.
+# @medipha/chat
+
+`@medipha/chat` is an embeddable React chat module for Medic-ERP. It uses the
+ERP application's React tree, BrowserRouter, authentication, and Ant Design 4
+installation; it does not use an iframe or create a router.
+
+## Install
+
+```bash
+pnpm add @medipha/chat
+```
+
+## Mount in Medic-ERP
+
+The ERP imports the Ant Design 4 stylesheet exactly once, at its application
+entry point. The chat library deliberately does not import it.
+
+```tsx
+import 'antd/dist/antd.css';
+import { ChatModule } from '@medipha/chat';
+import '@medipha/chat/styles.css';
+
+<Route
+  path="/chat-erp/*"
+  element={
+    <ChatModule
+      accessToken={accessToken}
+      apiUrl={CHAT_API_URL}
+      socketUrl={CHAT_SOCKET_URL}
+      onUnauthorized={handleUnauthorized}
+      onNavigateOutsideChat={handleNavigateOutsideChat}
+    />
+  }
+/>;
+```
+
+The ERP must own the surrounding `BrowserRouter`. `ChatModule` adds only
+relative routes: `/chat-erp` for the conversation list and
+`/chat-erp/:conversationId` for a room.
+
+## `ChatModuleProps`
+
+| Prop                    | Required | Meaning                                                   |
+| ----------------------- | -------- | --------------------------------------------------------- |
+| `accessToken`           | Yes      | Current ERP access token used by chat API/socket clients. |
+| `apiUrl`                | Yes      | Base URL for the Chat HTTP API.                           |
+| `socketUrl`             | Yes      | Socket server URL.                                        |
+| `onUnauthorized`        | No       | ERP callback for an unauthorized chat response.           |
+| `onNavigateOutsideChat` | No       | ERP callback for navigation that leaves chat.             |
+
+Pass a new `accessToken` prop whenever ERP refreshes its credential.
+`ChatModule` updates its internal runtime context from the new prop and never
+writes a token to `localStorage` or `sessionStorage`.
+
+## Nginx SPA fallback
+
+Configure the ERP server so deep links under `/chat-erp/*` return the ERP
+application entry file:
+
+```nginx
+location / {
+  try_files $uri $uri/ /index.html;
+}
+```
+
+## Development and validation
+
+Vite 8 requires Node.js `20.19+` or `22.12+`.
+
+```bash
+pnpm install
+pnpm dev
+```
+
+`pnpm dev` opens the root development playground. It loads `ChatModule`
+directly from `src`, so library code and CSS changes use Vite HMR without a
+library build after every edit. The playground's `BrowserRouter` is
+development-only; it is not part of the published package.
+
+To validate the publishable library:
+
+```bash
+pnpm typecheck
+pnpm build
+npm pack --dry-run
+```
+
+To verify the CRA host after building the library:
+
+```bash
+cd examples/erp-host
+pnpm install
+pnpm build
+```
+
+## Publish
+
+Publish `@medipha/chat-core` before `@medipha/chat`. GitLab CI uses a masked,
+protected `NPM_TOKEN` variable with npm publish permission and runs only for a
+version tag such as `v0.1.0`. Update versions using semantic versioning: patch
+for fixes, minor for backward-compatible features, and major for breaking API
+changes. Create and push the version tag through your normal release process
+after reviewing the working tree.

package/dist/features/composer/attachment-file-helpers.d.ts

@@ -1,5 +1,5 @@
 import { PendingAttachment } from './pending-attachment';
-export declare const ACCEPT_ATTRIBUTE = ".jpg,.jpeg,.png,.webp,.pdf,.doc,.docx,.xls,.xlsx,.ppt,.pptx,.txt";
+export declare const ACCEPT_ATTRIBUTE = ".jpg,.jpeg,.png,.webp,.gif,.pdf,.doc,.docx,.xls,.xlsx,.ppt,.pptx,.txt,.csv,.zip,.rar,.mp4,.mp3";
 export declare const ACCEPTED_FILE_EXTENSIONS: Set<string>;
 export declare const getFileExtension: (file: File) => string;
 export declare const isImageFile: (file: File) => boolean;

package/dist/features/composer/conversation-composer.d.ts

@@ -12,9 +12,16 @@ interface ConversationComposerProps {
     onError?: (message: string) => void;
     onAttach?: () => void;
     onAttachImages?: () => void;
+    /** Stages pasted image file(s) exactly like the attach-image button/drop would. */
+    onPasteFiles?: (files: File[]) => void;
     onTypingStart?: () => void;
     onTypingStop?: () => void;
 }
+export interface ConversationComposerHandle {
+    /** Returns the caret to the editor — used after staging an attachment, where focus
+     *  otherwise stays on the attach button (or the file dialog that just closed). */
+    focus: () => void;
+}
 /** Rich-text composer that emits backend message content, with real @mentions. */
-export declare function ConversationComposer({ conversationName, members, canMentionAll, enableMentions, disabled, hasPendingAttachments, onSubmit, onError, onAttach, onAttachImages, onTypingStart, onTypingStop, }: ConversationComposerProps): import("react/jsx-runtime").JSX.Element;
+export declare const ConversationComposer: import('react').ForwardRefExoticComponent<ConversationComposerProps & import('react').RefAttributes<ConversationComposerHandle>>;
 export {};

package/dist/features/create-conversation/tabs/create-group-tab.d.ts

@@ -6,8 +6,9 @@ interface CreateGroupTabProps {
     isLoadingUsers: boolean;
     error: string;
     onSubmit: (title: string, memberIds: string[], isVerified: boolean) => void;
+    onInvalidTitle: () => void;
 }
 /** "Nhóm" tab — check off members, submit to create the group (title input lives in the
  *  parent panel, above the department/branch filters). */
-export declare function CreateGroupTab({ users, groupTitle, isCreating, isLoadingUsers, error, onSubmit, }: CreateGroupTabProps): import("react/jsx-runtime").JSX.Element;
+export declare function CreateGroupTab({ users, groupTitle, isCreating, isLoadingUsers, error, onSubmit, onInvalidTitle, }: CreateGroupTabProps): import("react/jsx-runtime").JSX.Element;
 export {};

package/dist/features/message-list/bubble/use-reaction-name-preview.d.ts

@@ -0,0 +1,21 @@
+/** How many reactor names the hover tooltip shows before collapsing the rest into
+ *  "và N người khác" — matches BADGE_ICON_LIMIT in message-reactions.tsx so the tooltip
+ *  reads as an expansion of the same overlapping icons the badge already shows. */
+export declare const REACTION_NAME_PREVIEW_LIMIT = 3;
+interface ReactionNamePreview {
+    names: string[];
+    totalCount: number;
+}
+/** Lazily loads just enough reactor names to fill the aggregate reaction badge's hover
+ *  tooltip. There can be hundreds of messages in a timeline, so this only fetches when a
+ *  given badge is actually hovered (call `load()` from the hover handler) — never eagerly
+ *  for messages nobody looks at — and caches the result per message so re-hovering the
+ *  same badge doesn't refetch. `requestRef` mirrors the stale-response guard already used
+ *  in use-reaction-modal.ts: if `load()` is called again for this message before the first
+ *  call resolves, the earlier response is ignored when it lands. */
+export declare function useReactionNamePreview(messageId: string | null): {
+    preview: ReactionNamePreview | null;
+    isLoading: boolean;
+    load: () => void;
+};
+export {};

package/dist/features/typing/typing-indicator.d.ts

@@ -0,0 +1,8 @@
+interface TypingIndicatorProps {
+    typingNames: string[];
+}
+/** Sits in normal flow between the timeline and the composer toolbar (Messenger/Zalo
+ *  style) instead of floating over the message list — the name(s) typing, plus a small
+ *  bubble of three bouncing dots standing in for "...". */
+export declare function TypingIndicator({ typingNames }: TypingIndicatorProps): import("react/jsx-runtime").JSX.Element | null;
+export {};