@helpway/react 0.15.2 → 0.16.0

package/dist/index.d.ts

@@ -111,6 +111,13 @@ interface IdentifyData {
     name?: string;
     image?: string;
     metadata?: Record<string, unknown>;
+    /**
+     * Move this browser's visitor to the contact above even if it already
+     * belongs to a different contact. Dangerous: it merges whatever history
+     * this browser has into that contact. Off by default; without it the
+     * server keeps the existing link and returns that contact (#193).
+     */
+    reassign?: boolean;
 }
 /** Use a slice of the widget store with auto re-render */
 declare function useWidgetStore<T>(selector: (state: WidgetStore) => T): T;
@@ -174,6 +181,13 @@ declare function useWidget(): {
         name?: string;
         image?: string;
         metadata?: Record<string, unknown>;
+        /**
+         * Move this browser's visitor to the contact above even if it already
+         * belongs to a different contact. Dangerous: it merges whatever history
+         * this browser has into that contact. Off by default; without it the
+         * server keeps the existing link and returns that contact (#193).
+         */
+        reassign?: boolean;
     }) => Promise<any>;
 };
 
@@ -261,6 +275,30 @@ declare function useUnread(): {
     totalUnread: number;
 };
 
+/**
+ * How many conversations are waiting on the visitor to reply.
+ *
+ * Exists because `useUnread()` answers a question consumers usually do not have.
+ * A thread we answered two minutes ago and a thread the visitor closed
+ * themselves look identical in the widget — same row, same weight, no marker —
+ * and that is the moment a support thread dies: we reply, the visitor never
+ * registers it, the conversation is abandoned with an unanswered message in it.
+ *
+ * Counts human replies, not AI ones. An auto-reply follows nearly every visitor
+ * message, so including them leaves the indicator permanently lit for anyone who
+ * has ever opened the widget, which teaches people to ignore it.
+ *
+ * Written by hand in a downstream dashboard before it existed here; a
+ * `hideLauncher` integration badging its own trigger should not have to
+ * reimplement the rule.
+ *
+ * ```tsx
+ * const awaiting = useAwaitingReply();
+ * // "3 awaiting reply" — label it, do not just show the number
+ * ```
+ */
+declare function useAwaitingReply(): number;
+
 /**
  * Subscribe to raw WebSocket events.
  * For advanced usage — most apps should use useTimeline/usePresence instead.
@@ -271,6 +309,13 @@ declare function useUnread(): {
  *   if (event.type === 'timelineItemCreated') { ... }
  * })
  * ```
+ *
+ * The subscription lives as long as the socket instance, not as long as the
+ * handler's identity (#146). Callers pass inline arrows, which are new on every
+ * render; with `handler` in the effect deps that meant `handlers.delete` and
+ * `handlers.add` on every render above the caller, and any event that arrived
+ * between the two was dropped. The latest handler is kept in a ref and one
+ * stable wrapper is subscribed per socket.
  */
 declare function useRealtime(handler: (event: RealtimeEvent) => void): void;
 
@@ -474,6 +519,19 @@ interface AnnouncementPreviewsProps {
      * so its visual stays byte-identical to the original.
      */
     footer?: ReactNode;
+    /**
+     * How many cards to render before collapsing the rest into a single
+     * "+N more updates" row.
+     *
+     * Unlimited by default, which is what every existing consumer already gets.
+     * The launcher passes a real number because the strip above it is shared with
+     * the incoming-reply card and the two together ran off the top of the screen:
+     * four cards need more than 600px of viewport, and the topmost ones were
+     * simply gone. Clipping is a priority statement, not a size fix — a reply is a
+     * conversation waiting on the visitor, an announcement is content that can
+     * wait, so the announcements are what gets collapsed.
+     */
+    maxVisible?: number;
 }
 /**
  * `<AnnouncementPreviews>` — proactive "new content" cards shown when
@@ -490,7 +548,7 @@ interface AnnouncementPreviewsProps {
  *
  * Must be rendered inside `<SupportProvider>`.
  */
-declare function AnnouncementPreviews({ onOpen, avatar, placement, footer, }: AnnouncementPreviewsProps): react_jsx_runtime.JSX.Element | null;
+declare function AnnouncementPreviews({ onOpen, avatar, placement, footer, maxVisible, }: AnnouncementPreviewsProps): react_jsx_runtime.JSX.Element | null;
 
 /**
  * Lightweight Markdown → HTML renderer.
@@ -520,4 +578,4 @@ declare function MarkdownContent({ bodyHtml, bodyMarkdown, className, }: {
     className?: string;
 }): react_jsx_runtime.JSX.Element | null;
 
-export { type AnnouncementPreviewEntry, AnnouncementPreviews, type AnnouncementPreviewsPlacement, type AnnouncementPreviewsProps, Composer, DefaultWidget, type HelpwayPublicAPI, HelpwayWidget, type HelpwayWidgetProps, type IdentifyData, MarkdownContent, MessageBubble, MessageList, MessagePreview, type MessagePreviewPlacement, type MessagePreviewProps, SupportProvider, WidgetLogo, linkifyText, renderMarkdown, useComposer, useConversations, useIdentify, usePresence, useRealtime, useTimeline, useUnread, useWidget, useWidgetStore };
+export { type AnnouncementPreviewEntry, AnnouncementPreviews, type AnnouncementPreviewsPlacement, type AnnouncementPreviewsProps, Composer, DefaultWidget, type HelpwayPublicAPI, HelpwayWidget, type HelpwayWidgetProps, type IdentifyData, MarkdownContent, MessageBubble, MessageList, MessagePreview, type MessagePreviewPlacement, type MessagePreviewProps, SupportProvider, WidgetLogo, linkifyText, renderMarkdown, useAwaitingReply, useComposer, useConversations, useIdentify, usePresence, useRealtime, useTimeline, useUnread, useWidget, useWidgetStore };