@opencxh/ui-kit 3.137.12 → 3.137.13

package/dist/src/index.d.ts

@@ -2,6 +2,7 @@ export { cn, createSizes, createVariants } from './utils/cn';
 export { useAnchoredPosition, type AnchoredPositionOptions } from './utils/useAnchoredPosition';
 export { IDENTITY_TONE_COUNT, identityDotClass, identityPlateClass, identityTone, type IdentityTone } from './utils/identity';
 export { catTone, type CatTone } from './utils/catTone';
+export { normalizeText, text } from './utils/text';
 export { MeetingGrid, type MeetingGridProps } from './meeting/MeetingGrid';
 export { ParticipantTile, type ParticipantTileProps } from './meeting/ParticipantTile';
 export { VideoSurface, type VideoSurfaceProps } from './meeting/VideoSurface';

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

@@ -0,0 +1,20 @@
+/**
+ * Coerce an unknown value to text.
+ *
+ * Every input component in this kit declares its `value` as `string`, and every
+ * one of them is fed straight out of form data, which is `any`. A field whose
+ * entity type is numeric therefore arrives as a number — `eylo-voip`'s time
+ * rules do exactly that (`interval?: number`, `days?: number[]`) — and the two
+ * failure modes are both silent from the type system's side:
+ *
+ * - a hard `TypeError: (…).trim is not a function` the moment anything calls a
+ *   string method on it;
+ * - a comparison that simply never matches, because `1 === "1"` is false, so a
+ *   stored option renders as unselected with no error at all.
+ *
+ * `null` and `undefined` become `""` so callers can treat "absent" and "empty"
+ * alike, which is what a text input does anyway.
+ */
+export declare const text: (value: unknown) => string;
+/** {@link text} folded to a comparable key: trimmed and lower-cased. */
+export declare const normalizeText: (value: unknown) => string;

package/package.json

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