@danxbot/ui 8.0.0 → 9.0.0

package/dist/types/lib/values/absent.d.ts

@@ -0,0 +1,7 @@
+/** The shared "no value" reading for a blank field — a date, a number, a
+ *  phone number, a currency amount: nothing recorded. Shared by every
+ *  formatter that reads absence this way, so the glyph itself never drifts
+ *  between them (DX-3254). `formatBoolean` does NOT use this — see its own
+ *  module doc for why a tri-state boolean reads absence as "Unknown"
+ *  instead. */
+export declare const ABSENT = "\u2014";

package/dist/types/lib/values/currency.d.ts

@@ -3,7 +3,7 @@
  *
  * `NaN` / `Infinity` are not real amounts either and render as the em dash —
  * grouped with absence rather than with a malformed string, because unlike
- * `formatDate`/`formatPhone`'s malformed-input case, there is no ORIGINAL
+ * `formatDate`'s malformed-input case, there is no ORIGINAL
  * user-facing string to show back: the caller already has a `number`, and a
  * non-finite one is a computation defect upstream, not a typo to surface.
  */

package/dist/types/lib/values/index.d.ts

@@ -1,8 +1,5 @@
 export { formatDate, parseDate } from "./date";
 export { formatDateTime, parseDateTime, type FormatDateTimeOptions, type ParseDateTimeOptions } from "./datetime";
 export { formatCurrency, parseCurrency } from "./currency";
-export { formatPhone, parsePhone, digitsOfPhoneInProgress, formatPhonePartial } from "./phone";
 export { formatNumber, parseNumber, type FormatNumberOptions } from "./number";
 export { formatBoolean, parseBoolean, type FormatBooleanOptions } from "./boolean";
-export { isValidEmail } from "./email";
-export { isValidUrl } from "./url";

package/dist/types/pure.d.ts

@@ -39,5 +39,5 @@
  * about this is a migration and no existing import has to change.
  */
 export { formatBytes, formatTokens, formatCompactNumber } from "./lib/format";
-export { formatDate, parseDate, formatDateTime, parseDateTime, type FormatDateTimeOptions, type ParseDateTimeOptions, formatCurrency, parseCurrency, formatPhone, parsePhone, digitsOfPhoneInProgress, formatPhonePartial, formatNumber, parseNumber, type FormatNumberOptions, formatBoolean, parseBoolean, type FormatBooleanOptions, isValidEmail, isValidUrl, } from "./lib/values";
+export { formatDate, parseDate, formatDateTime, parseDateTime, type FormatDateTimeOptions, type ParseDateTimeOptions, formatCurrency, parseCurrency, formatNumber, parseNumber, type FormatNumberOptions, formatBoolean, parseBoolean, type FormatBooleanOptions, } from "./lib/values";
 export { confidenceLevel, CONFIDENCE_LEVEL_LABELS, type ConfidenceLevel } from "./lib/confidence";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danxbot/ui",
-  "version": "8.0.0",
+  "version": "9.0.0",
   "type": "module",
   "description": "Danxbot — a domain-agnostic React design system with motion as a first-class primitive.",
   "license": "MIT",

package/dist/types/components/InfiniteScroller.d.ts

@@ -1,34 +0,0 @@
-import { type CSSProperties, type Key, type ReactNode, type Ref, type RefObject } from "react";
-export interface InfiniteScrollerHandle {
-    /** Mount everything up to `index` (if not already mounted), then scroll that item into view. */
-    reveal: (index: number, options?: ScrollIntoViewOptions) => void;
-}
-export interface InfiniteScrollerProps<T> {
-    /** Every item. Only a window of them is mounted. */
-    items: readonly T[];
-    renderItem: (item: T, index: number) => ReactNode;
-    /** A stable React key per item. */
-    getKey: (item: T, index: number) => Key;
-    /** How many items are mounted at first. Default 20. */
-    initialCount?: number;
-    /** How many more mount each time the end comes into range. Default `initialCount`. */
-    batchSize?: number;
-    /** Lay items out as a CSS grid with this many equal columns. Omit for a plain vertical list. */
-    columns?: number;
-    /** How far outside the scroll viewport the end may be before more mount. Default "200px". */
-    rootMargin?: string;
-    /**
-     * The scrolling element to observe against. Default: the nearest ancestor whose `overflow-y`
-     * scrolls, else the viewport.
-     */
-    root?: RefObject<Element | null>;
-    /** Changing this puts the window back to `initialCount` (a genuinely different list). */
-    resetKey?: unknown;
-    /** Classes for the list/grid element — gaps, padding. */
-    className?: string;
-    style?: CSSProperties;
-    ref?: Ref<InfiniteScrollerHandle>;
-    /** Accessible name for the list, when it needs one. */
-    "aria-label"?: string;
-}
-export declare function InfiniteScroller<T>({ items, renderItem, getKey, initialCount, batchSize, columns, rootMargin, root, resetKey, className, style, ref, "aria-label": ariaLabel, }: InfiniteScrollerProps<T>): import("react").JSX.Element;

package/dist/types/components/PhoneField.d.ts

@@ -1,17 +0,0 @@
-export interface PhoneFieldProps {
-    /** The stored ten-digit form, or null for none. */
-    value: string | null;
-    /** Reports the new ten-digit value, or null when the person cleared it. Only on commit. */
-    onValueChange: (value: string | null) => void;
-    /** Told while the box has focus — i.e. while the person's own in-progress digits are on screen. */
-    onEditingChange?: (editing: boolean) => void;
-    /** The accessible name — required, same reasoning as `DateField`'s. */
-    "aria-label": string;
-    /** @default "(555) 123-4567" */
-    placeholder?: string;
-    disabled?: boolean;
-    /** The sentence shown for a committed value that is not ten digits. */
-    invalidMessage?: string;
-    className?: string;
-}
-export declare function PhoneField({ value, onValueChange, onEditingChange, "aria-label": ariaLabel, placeholder, disabled, invalidMessage, className, }: PhoneFieldProps): import("react").JSX.Element;

package/dist/types/components/calendar/index.d.ts

@@ -1,9 +0,0 @@
-export { CalendarMonth, type CalendarMonthProps } from "./CalendarMonth";
-export { CalendarTimeGrid, type CalendarTimeGridProps } from "./CalendarTimeGrid";
-export { useNow, type UseNowOptions } from "./use-now";
-export { EventActions, type EventActionsProps } from "./EventActions";
-export { useCalendarDrag, type CalendarDragOptions, type CalendarDragState, } from "./use-calendar-drag";
-export { useEventKeyboard, type EventKeyboardOptions, type EventKeyboardState, } from "./use-event-keyboard";
-export { EVENT_PALETTE, DEFAULT_PALETTE_KEY, isPaletteKey, paletteFor } from "./palette";
-export { cellLabel, dayNumber, eventLabel, formatDateRange, longDate, monthTitle, timeOfDay, weekdayName, zoneLabel, } from "./format";
-export { initialFocusDay, isInMonth, nextDayForKey, useGridNavigation, type GridNavigation, type GridNavigationOptions, } from "./use-grid-navigation";

package/dist/types/lib/values/email.d.ts

@@ -1,12 +0,0 @@
-/**
- * Whether `value` reads as a plausible email address. An empty (or
- * whitespace-only) value is treated as VALID — clearing the field is not a
- * typo, and a required-field rule belongs to the caller, not this check.
- *
- * SG-909 review fix: the previous regex (`/^[^\s@]+@[^\s@]+\.[^\s@]+$/`)
- * matched the domain half non-specifically, so `"a@b..com"` (an empty label
- * between two dots) passed, and it never looked at trailing punctuation at
- * all, so `"jane@example.com."` and `"jane@example.com,"` — the shape a typo
- * or a sentence's own full stop produces — both passed too.
- */
-export declare function isValidEmail(value: string): boolean;

package/dist/types/lib/values/phone.d.ts

@@ -1,68 +0,0 @@
-/**
- * Ten stored digits → `"(555) 123-4567"`. `null` / `undefined` / `""` → `"—"`.
- *
- * A non-empty value that is not exactly ten digits after parsing is returned
- * UNCHANGED — the same "show the corruption, don't hide it behind absence"
- * rule `formatDate` documents. A stored value should already be `parsePhone`'s
- * output; if it is not, that is a data problem worth seeing in the row, not
- * a blank field that looks like nobody ever entered a number.
- *
- * Reuses `formatPhonePartial` for the ten-digit case (SG-909 review) rather
- * than repeating the same three-slice punctuation a second time — passing it
- * exactly ten digits always produces the identical `"(XXX) XXX-XXXX"` string,
- * since `formatPhonePartial` only ever appends a raw, unformatted tail past
- * the tenth digit and there is no tail here.
- */
-export declare function formatPhone(value: string | null | undefined): string;
-/**
- * A human-typed phone number → ten stored digits, or `null`.
- *
- * Strips everything but digits, so `"(555) 123-4567"`, `"555.123.4567"`,
- * `"555-123-4567 "` and `"5551234567"` all normalise the same way. A leading
- * US country code (`"1"`, making 11 digits total) is dropped — `"+1 (555)
- * 123-4567"` is the same number as `"(555) 123-4567"` and should be stored
- * identically. Anything that is not exactly 10 digits after that — too few,
- * too many, or an 11-digit number NOT starting with `1` (a foreign number
- * mis-typed into a US field, not a US number with an extra digit) — returns
- * `null` rather than truncating or padding a guess into place.
- *
- * THIS is the one place in the file the 11-digit-leading-`1` rule is written
- * (SG-909 review — it used to also live in `digitsOfPhoneInProgress`, which
- * no longer transforms digits at all; see that function's own doc for why).
- */
-export declare function parsePhone(input: string): string | null;
-/**
- * Every non-digit stripped — nothing else. `PhoneField` (SG-909) keeps this
- * as ITS state while a person is still typing.
- *
- * Deliberately NOT capped at ten and NOT country-code-aware, unlike an
- * earlier revision of this function. That revision silently dropped every
- * digit past the tenth and stripped a leading `"1"` off an 11-digit run —
- * which meant pasting `"555-123-4567 x12"` or `"44 20 7946 0958"` (a UK
- * number) landed at commit as `parsePhone` accepting whatever ten-or-eleven
- * digits happened to survive the cap, saving a DIFFERENT phone number than
- * the one actually typed, with no error and no visible sign anything had
- * been thrown away. `PhoneField` now keeps the full digit sequence — see its
- * own module comment for how it is FORMATTED (first ten punctuated, any rest
- * appended raw) and how `parsePhone` alone decides, at commit, whether the
- * full sequence resolves to a real ten-digit number.
- */
-export declare function digitsOfPhoneInProgress(input: string): string;
-/**
- * A digit sequence of any length → what the box shows WHILE TYPING —
- * progressively punctuated as each of the first ten digits lands, with any
- * digit past the tenth appended after a space, UNFORMATTED, rather than
- * silently dropped (SG-909 review). `formatPhone` above is the too-late-to-
- * use-here sibling: it takes the STORED ten-digit form and either renders it
- * or hands back a non-ten-digit value unchanged, which would show a partial
- * number completely unpunctuated until the last digit arrived, and would
- * have nowhere to put an eleventh digit at all.
- *
- * The trailing digits past ten are shown, not hidden, specifically so a
- * too-long paste or a stray extra keystroke stays visible for the person to
- * see and correct — `parsePhone` will refuse anything that is not exactly
- * ten digits (or eleven with a leading `1`) at commit, and a refusal against
- * a box that visibly still has extra digits in it is legible; a refusal
- * against a box that silently ate them is not.
- */
-export declare function formatPhonePartial(digits: string): string;

package/dist/types/lib/values/url.d.ts

@@ -1,6 +0,0 @@
-/**
- * Whether `value` reads as a plausible web address. An empty (or
- * whitespace-only) value is treated as VALID — see `isValidEmail`'s identical
- * reasoning.
- */
-export declare function isValidUrl(value: string): boolean;