@ttt-productions/chat-core 0.5.8 → 0.6.0

package/dist/mentions/types.d.ts

@@ -3,16 +3,16 @@
  *
  * chat-core owns the mention infrastructure (parsing, autocomplete UI, keyboard
  * behavior, composer insertion, message text rendering) but knows nothing about
- * what a "user" or "project" is. The consumer parameterizes `TKind` to its own
+ * what a "user" or "entity" is. The consumer parameterizes `TKind` to its own
  * union and supplies one `MentionProvider` per kind.
  *
- * Wire format — mentions are encoded inline in the message's `text` field as
+ * Wire format — mentions are encoded inline in the message's `text` field as
  * `@[kind:id|displayText]` tokens. The renderer parses them out at display
  * time. No schema change to ChatMessage.
  */
 import type { ReactNode } from 'react';
 /**
- * Resolved mention — the value that ends up in the wire token after the user
+ * Resolved mention — the value that ends up in the wire token after the user
  * selects an autocomplete result.
  *
  * `kind` is the discriminator supplied by the consumer (e.g. `'member'`, `'tag'`); `id` is the
@@ -38,17 +38,17 @@ export type ParsedSegment<TKind extends string = string> = {
 /**
  * Provider supplying autocomplete results for one mention kind.
  *
- * - `kind` — the discriminator. Must match `MentionRef.kind` for results
+ * - `kind` — the discriminator. Must match `MentionRef.kind` for results
  *   returned by `search`.
- * - `label` — human-readable label for the section / tab.
- * - `search` — async query. Receives the current query string (after the
+ * - `label` — human-readable label for the section / tab.
+ * - `search` — async query. Receives the current query string (after the
  *   trigger character), the consumer-supplied `context`, and an optional
  *   `signal` for cancellation. Returns up to whatever limit the provider
  *   chooses; chat-core renders all returned results.
- * - `renderResult` — optional custom row UI. When omitted, the autocomplete
+ * - `renderResult` — optional custom row UI. When omitted, the autocomplete
  *   renders the `displayText` plain.
  *
- * `TContext` is consumer-owned — pass anything you need inside `search`
+ * `TContext` is consumer-owned — pass anything you need inside `search`
  * (Firestore db, current user id, surface-specific filters). chat-core never
  * inspects it.
  */
@@ -67,7 +67,7 @@ export type MentionProvider<TKind extends string = string, TContext = unknown> =
  * recent picks when the user opens the dropdown without typing a query
  * (or after typing fewer than the configured minimum characters).
  *
- * `getRecent` MAY be async — the autocomplete renders a spinner while it
+ * `getRecent` MAY be async — the autocomplete renders a spinner while it
  * resolves. `recordUse` is fired after a successful selection so consumers
  * can persist usage.
  */
@@ -80,8 +80,8 @@ export type RecentMentionsAdapter<TKind extends string = string> = {
  * text buffer. Tracked in component state so positionally-collocated mentions
  * with the same display string disambiguate on send.
  *
- * - `start` / `end` — character offsets into the current textarea value.
- * - `ref` — the resolved MentionRef.
+ * - `start` / `end` — character offsets into the current textarea value.
+ * - `ref` — the resolved MentionRef.
  */
 export type MentionAnchor<TKind extends string = string> = {
     start: number;

package/dist/mentions/types.js

@@ -3,10 +3,10 @@
  *
  * chat-core owns the mention infrastructure (parsing, autocomplete UI, keyboard
  * behavior, composer insertion, message text rendering) but knows nothing about
- * what a "user" or "project" is. The consumer parameterizes `TKind` to its own
+ * what a "user" or "entity" is. The consumer parameterizes `TKind` to its own
  * union and supplies one `MentionProvider` per kind.
  *
- * Wire format — mentions are encoded inline in the message's `text` field as
+ * Wire format — mentions are encoded inline in the message's `text` field as
  * `@[kind:id|displayText]` tokens. The renderer parses them out at display
  * time. No schema change to ChatMessage.
  */

package/dist/types.d.ts

@@ -28,13 +28,13 @@ export type ChatMessageV1 = {
  * Access mode controls how chat-core decides whether the current user
  * can read/write a thread.
  *
- * - "firestore-rules" — chat-core trusts Firestore rules. canAccessThread
+ * - "firestore-rules" — chat-core trusts Firestore rules. canAccessThread
  *   returns true for any signed-in user; if rules deny, onSnapshot will
  *   surface permission-denied. Use this when access depends on data the
- *   client doesn't reliably know up-front (project membership, invite
+ *   client doesn't reliably know up-front (entity membership, invite
  *   participation, etc.).
  *
- * - "explicit-allowlist" — chat-core enforces access client-side via
+ * - "explicit-allowlist" — chat-core enforces access client-side via
  *   threadAllowedUserIds. The list is required in this mode. Use this
  *   when the consumer already knows the participants (admin/support
  *   threads).
@@ -77,7 +77,7 @@ export type ChatCoreConfig = {
  *
  * `buildUploadPath` and `buildUploadMetadata` receive the userId and
  * attachmentId so consumers can interpolate them per their own conventions.
- * chat-core does not interpret `originId` — it forwards it via callbacks
+ * chat-core does not interpret `originId` — it forwards it via callbacks
  * and uses it for adapter identity only.
  */
 export type ChatUploadAdapter = {
@@ -112,7 +112,7 @@ export type ChatAttachmentConfig = {
  * doc with the caption text + reply pointer. The processor will create the
  * message doc itself after media moderation succeeds.
  *
- * No message doc is created at this point — Composer should render an
+ * No message doc is created at this point — Composer should render an
  * optimistic local "uploading" state until the listener delivers the real
  * message after processing completes.
  */
@@ -134,7 +134,7 @@ export type SendAttachmentFn = (input: SendAttachmentInput) => Promise<void>;
  * mention tokens out of `text`.
  *
  * Generic over `TKind` and `TContext` is intentionally NOT exposed here at
- * the type level — `ChatCoreConfig` would have to become generic too, which
+ * the type level — `ChatCoreConfig` would have to become generic too, which
  * cascades. Instead this type accepts permissive `string`-keyed providers;
  * consumers binding stricter kind unions narrow at the call site via their
  * provider definitions.
@@ -171,14 +171,14 @@ export type MessageRendererRegistry = Record<string, MessageRenderer>;
 export declare const GROUP_GAP_SEC = 120;
 /**
  * Resolves a senderId to a display name synchronously from app-side cache.
- * Returns null if the sender is unknown or the cache hasn't loaded yet —
+ * Returns null if the sender is unknown or the cache hasn't loaded yet —
  * chat-core will render a stable fallback ("User") in that case.
  */
 export type ChatNameResolver = (senderId: string) => string | null;
 /**
  * Optional pre-warm callback. chat-core calls this with the deduped list of
  * senderIds visible in the current message page so the consuming app can
- * batch-fetch names into its cache. Implementations should be idempotent —
+ * batch-fetch names into its cache. Implementations should be idempotent —
  * the same id list will be passed across re-renders.
  */
 export type ChatPrewarmSenders = (senderIds: string[]) => void;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ttt-productions/chat-core",
-  "version": "0.5.8",
+  "version": "0.6.0",
   "description": "Shared Firestore chat core (realtime newest window + infinite older pagination) for TTT Productions apps",
   "repository": {
     "type": "git",