@opencxh/ui-kit 3.177.0 → 3.179.0

package/dist/src/index.d.ts

@@ -72,4 +72,4 @@ export { type CatTone, catTone } from './utils/catTone';
 export { cn, createSizes, createVariants } from './utils/cn';
 export { IDENTITY_TONE_COUNT, type IdentityTone, identityDotClass, identityPlateClass, identityTone, } from './utils/identity';
 export { normalizeText, text } from './utils/text';
-export { type AnchoredPositionOptions, useAnchoredPosition, } from './utils/useAnchoredPosition';
+export { type AnchoredPositionOptions, type AnchorRect, useAnchoredPosition, } from './utils/useAnchoredPosition';

package/dist/src/input/MentionComposer.d.ts

@@ -10,8 +10,14 @@ export interface MentionPerson {
 export interface MentionComposerProps {
     /** Seed HTML, sanitised before it lands. Mention chips survive if they carry `data-mention-id`. */
     initialContent?: string;
-    /** Plain text plus the ids of the chips still standing in it. */
-    onChange: (plainText: string, mentionIds: string[]) => void;
+    /**
+     * Plain text, the ids of the chips still standing in it, and the sanitised HTML.
+     *
+     * Persist the HTML next to the text, never instead of it: everything that reads a comment
+     * without rendering it — an AI prompt, a search index, a notification, the native app —
+     * wants the plain text, and only the surface that draws chips wants the markup.
+     */
+    onChange: (plainText: string, mentionIds: string[], html: string) => void;
     people: MentionPerson[];
     placeholder?: string;
     /** Cmd/Ctrl+Enter. Omitted means the shortcut does nothing. */

package/dist/src/utils/mentionChip.d.ts

@@ -0,0 +1,20 @@
+/**
+ * How a mention chip looks, as descendant utilities.
+ *
+ * **The chip element itself carries no `class`** — only `data-mention-id`. Comment HTML is
+ * persisted, and class names baked into stored markup would freeze today's design tokens in
+ * the database: a token rename would leave every old comment styled by a class that no longer
+ * exists. The attribute is the contract, the styling is applied by whoever renders it.
+ *
+ * Used by both ends: the composer (so a chip looks the same while you type) and `RichText`
+ * (so it still looks the same once posted).
+ */
+/**
+ * `info-soft`, not the `beta-container` the chip used to carry: that one is a hand-written
+ * rule in `global.css`, not an `@theme` token, so Tailwind can generate `.bg-beta-container`
+ * but not the `[&_…]:bg-beta-container` **variant** this needs. Verified against a compile:
+ * both tokens here resolve, and the chip would otherwise have been silently unstyled.
+ */
+export declare const MENTION_CHIP_CLASSES: string;
+/** DOMPurify must keep the marker attribute, or a sanitised chip is just text. */
+export declare const MENTION_SANITIZE_ATTR = "data-mention-id";

package/dist/src/utils/useAnchoredPosition.d.ts

@@ -1,4 +1,11 @@
 import { CSSProperties, RefObject } from 'react';
+/**
+ * Anything that can report where it is. An element is the usual anchor, but a DOM `Range`
+ * qualifies too — which is how a panel anchors to the caret instead of to its whole field.
+ */
+export interface AnchorRect {
+    getBoundingClientRect(): DOMRect;
+}
 export interface AnchoredPositionOptions {
     /** Gap between the anchor and the panel, in px. */
     gap?: number;
@@ -19,4 +26,4 @@ export interface AnchoredPositionOptions {
  * Recomputes on scroll and resize while open, so the panel tracks its trigger
  * instead of detaching when the page moves under it.
  */
-export declare function useAnchoredPosition(open: boolean, anchorRef: RefObject<HTMLElement | null>, { gap, matchWidth, placement }?: AnchoredPositionOptions): CSSProperties;
+export declare function useAnchoredPosition(open: boolean, anchorRef: RefObject<AnchorRect | null>, { gap, matchWidth, placement }?: AnchoredPositionOptions): CSSProperties;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opencxh/ui-kit",
-  "version": "3.177.0",
+  "version": "3.179.0",
   "description": "Theme-aware UI component library for OpenCXH platform",
   "type": "module",
   "exports": {