@antzsoft/chat-core 1.2.7 → 1.2.9

package/README.md

@@ -2518,6 +2518,12 @@ interface Message {
   replyTo?: MessageReplyReference;
   reactions: MessageReaction[];
   status: 'sent' | 'delivered' | 'read' | 'failed' | 'deleted';
+  /**
+   * Tick status for the current user's perspective.
+   * On full message objects: computed from readBy / deliveredTo at fetch time.
+   * On Conversation.lastMessage (v1.2.8+): stored on the conversation and kept
+   * up-to-date by the server on every read/delivery event. Defaults to 'sent'.
+   */
   deliveryStatus?: 'sending' | 'sent' | 'delivered' | 'read' | 'failed';
   isEdited: boolean;
   editedAt?: string;
@@ -2668,7 +2674,7 @@ interface Conversation {
   participants: Participant[];
   participantCount?: number;
   settings?: ConversationSettings;
-  lastMessage?: Message;
+  lastMessage?: Message;  // deliveryStatus populated as of v1.2.8 — tick state of the last message
   createdBy?: string;
   isActive: boolean;
   createdAt: string;
@@ -2950,6 +2956,40 @@ document.querySelectorAll('[data-conv-id]').forEach((el) => {
 
 ## Changelog
 
+### v1.2.8
+
+- **New: `deliveryStatus` on `Conversation.lastMessage`** — The conversation list API (`GET /conversations`) and the `conversation_updated` socket event now include `deliveryStatus` on the `lastMessage` object. This is the tick state (`'sent'` | `'delivered'` | `'read'`) of the last message as seen by the sender. It is computed and stored directly on the conversation document — no extra queries at list time.
+
+  | Value | Meaning |
+  |---|---|
+  | `'sent'` | Message written to the server — not yet delivered to all recipients |
+  | `'delivered'` | All active recipients have received the message on at least one device |
+  | `'read'` | All active recipients have opened and read the message |
+
+  **Usage — conversation list tick marks (custom UI):**
+
+  ```typescript
+  const { data: conversations } = await conversationsApi.list();
+
+  for (const conv of conversations) {
+    const lm = conv.lastMessage;
+    if (!lm) continue;
+
+    // Only show ticks on messages sent by the current user
+    const isMyMessage = lm.senderId === currentUserId;
+    if (!isMyMessage) continue;
+
+    // lm.deliveryStatus: 'sent' | 'delivered' | 'read'
+    renderTick(conv.id, lm.deliveryStatus ?? 'sent');
+  }
+  ```
+
+  **Live updates** — the `read_receipt` socket event continues to carry real-time tick updates while a conversation room is open. `deliveryStatus` on `lastMessage` is the cold-start / list-load source of truth; the socket events keep it live after that.
+
+  **Backward compatibility** — `deliveryStatus` defaults to `'sent'` when absent (`lm.deliveryStatus ?? 'sent'`). Existing conversations are backfilled automatically by migration `005_backfill_last_message_delivery_status` which runs on first deploy. No integration changes required.
+
+  **`Message` type** — `deliveryStatus` was already defined as an optional field on the `Message` interface. It is now also populated on the `lastMessage` snapshot returned by the conversation list.
+
 ### v1.2.7
 - **New: `syncApi` — offline delta sync for mobile** — Two new REST endpoints let the mobile app pull all changes since a given timestamp without a full refetch. Call `syncApi.pull(since)` on every socket reconnect to get cross-conversation deltas; call `syncApi.pullConversation(convId, since?)` when opening a stale conversation (or on fresh install with no `since`). When the gap exceeds the stale threshold (default 30 days, env: `CHAT_SYNC_STALE_DAYS`) the server sets `stale: true` and returns no data — the app lazy-syncs each conversation as the user opens it. See [`syncApi`](#sync-api-syncapi) for full reference.
 - **New: `message_star_updated` socket event — real-time star sync across devices** — When the current user stars or unstars a message, the server now emits `message_star_updated` to their personal socket room. All other connected devices of the same user receive the event and update their local message cache automatically — no refetch needed. Payload: `{ messageId: string; conversationId: string; isStarred: boolean }`. New exported type: `MessageStarUpdatedEvent`. Web and RN `SocketProvider` handle this event internally.

package/dist/index.cjs

@@ -152,7 +152,13 @@ module.exports = __toCommonJS(src_exports);
 
 // src/config/types.ts
 function resolveConfig(config) {
-  const socketUrl = config.socketUrl ?? config.apiUrl.replace(/\/api\/v\d+\/?$/, "").replace(/\/$/, "");
+  const socketUrl = config.socketUrl ?? (() => {
+    try {
+      return new URL(config.apiUrl).origin;
+    } catch {
+      return config.apiUrl;
+    }
+  })();
   let socketOrigin = socketUrl;
   let socketPath = "/socket.io";
   try {
@@ -854,14 +860,22 @@ var syncApi = {
   },
   /**
    * Per-conversation delta sync — call when a conversation has `needs_refresh = true`
-   * or on fresh install (omit `since` to receive the full message history).
+   * or on fresh install (omit both since and afterSeq to receive full history).
    * Covers messages, deletedForMe, full reaction state, stars, participant changes,
    * and read receipts — everything needed to make local SQLite authoritative.
+   *
+   * Prefer `afterSeq` when available (new server) — paginated, collision-safe.
+   * Fall back to `since` timestamp for old servers or first sync on a new install.
+   * When `hasMore` is true in the response, call again with the returned `nextSeq`.
    */
-  pullConversation(conversationId, since) {
-    return getApiClient().get(`/conversations/${conversationId}/sync`, {
-      params: since ? { since } : {}
-    }).then((r) => r.data);
+  pullConversation(conversationId, opts) {
+    const params = {};
+    if (opts?.afterSeq !== void 0) {
+      params.afterSeq = opts.afterSeq;
+    } else if (opts?.since) {
+      params.since = opts.since;
+    }
+    return getApiClient().get(`/conversations/${conversationId}/sync`, { params }).then((r) => r.data);
   }
 };
 
@@ -1118,7 +1132,8 @@ function normalizeLastMessage(lastMsg) {
     },
     reactions: [],
     lastReaction: lastMsg.lastReaction ?? null,
-    status: lastMsg.status ?? "sent",
+    status: lastMsg.status ?? "active",
+    deliveryStatus: lastMsg.deliveryStatus ?? "sent",
     isEdited: false,
     sentAt: lastMsg.sentAt ?? "",
     createdAt: lastMsg.sentAt ?? "",