@sesamehr/react-design-system 2.0.0-beta.7 → 2.0.0-beta.9

package/dist/Data/Table/hooks/useTableVirtual/useTableVirtual.types.d.ts

@@ -26,9 +26,10 @@ export interface UseTableVirtualOptions {
      * This is what turns a scroll position into a row index, so it is worth
      * getting right: the error is paid on every row crossed, which is nothing at
      * one click of the wheel and hundreds of rows after a flick. The default,
-     * 48px, is the height `TableRow` gives itself with plain text in it. Rows
-     * with an avatar or two lines of text are taller, and those tables should say
-     * so here.
+     * 52px, is `--table-row-height` on `.oxTableRoot` — the minimum a row's cells
+     * give it with plain text in them. (Not `TableRow`'s own CSS: `height` on a
+     * `<tr>` is ignored by the table layout algorithm.) Rows with an avatar or two
+     * lines of text are taller, and those tables should say so here.
      *
      * It is deliberately a number you give rather than one measured from the
      * page. Measuring as you scroll means the total height changes as you scroll,

package/dist/Display/ChatBubble/ChatBubble.d.ts

@@ -1,10 +1,27 @@
 import { ReactNode } from 'react';
-import { ChatBubbleVariants } from './index.ts';
+import { ChatBubbleDelivery, ChatBubbleVariants } from './index.ts';
 export interface ChatBubbleProps extends React.HTMLAttributes<HTMLDivElement> {
     /** Who said it: the reader, or someone else */
     author?: ChatBubbleVariants['author'];
-    /** The line under the message — the timestamp, and a receipt if there is one */
-    meta?: ReactNode;
+    /**
+     * When the message went and whether it arrived, drawn as the footer line.
+     *
+     * Each key stands alone, so `{ time }`, `{ status }`, both or neither all
+     * work and an omitted key renders nothing — there is no flag to set and no
+     * line to assemble. Anything this cannot express (a delivery error, an
+     * "edited" marker, an avatar) goes in `footer` instead, which replaces this
+     * line wholesale when both are given.
+     */
+    delivery?: ChatBubbleDelivery;
+    /**
+     * The line under the message, drawn by hand. Ports the Vue `#footer` slot,
+     * and wins over `delivery` when both are supplied.
+     *
+     * Spelled `ReactNode` inline rather than behind an alias because
+     * `orxata/max-props` discounts a slot by reading the type *text*, and an alias
+     * hides it.
+     */
+    footer?: ReactNode;
     dataTestid: string;
 }
 /** ChatBubble — mirrors `@sesame/orxata-core` ChatBubble. */

package/dist/Display/ChatBubble/index.d.ts

@@ -1,5 +1,36 @@
 import { VariantProps } from 'class-variance-authority';
+import { ChatBubbleStatusVariants } from './ChatBubbleStatus/index.ts';
 export { ChatBubble, type ChatBubbleProps } from './ChatBubble.tsx';
+/**
+ * When the message went and whether it arrived — the bubble's footer, as data
+ * rather than as markup.
+ *
+ * One object rather than a prop each, for the same reason `ChatInput` takes one
+ * `actionLabels`: the parts belong together, they are all optional, and spending
+ * a prop per part would put a two-field component against the five-prop cap for
+ * no gain. Every key is independent — a time with no receipt, a receipt with no
+ * time, both, or neither — and an omitted key renders nothing at all, so the
+ * four combinations need no flags to select between them.
+ *
+ * Nothing here is prose the design system invents. `time` is a string the caller
+ * has already formatted, because formatting a date needs a locale, a timezone
+ * and a house style, and this package ships no strings and knows none of those.
+ * `status` is not text at all — it is an enum the bubble draws as an icon.
+ */
+export interface ChatBubbleDelivery {
+    /**
+     * The timestamp, already formatted — `'13 mar'`, `'09:41'`, whatever the
+     * product shows. Omit it for a bubble that carries only a receipt.
+     */
+    time?: string;
+    /**
+     * How far along the message is, drawn as a receipt.
+     *
+     * Only your own messages have one: there is no receipt for what somebody else
+     * said, so a bubble with `author: 'other'` normally omits this.
+     */
+    status?: NonNullable<ChatBubbleStatusVariants['status']>;
+}
 /**
  * Who said it, which is the only thing that varies.
  *

package/dist/Feedback/Popover/PopoverContent.d.ts

@@ -3,11 +3,4 @@ export interface PopoverContentProps extends React.ComponentPropsWithoutRef<type
     showArrow?: boolean;
     dataTestid: string;
 }
-/**
- * PopoverContent — portalled Radix popover content with optional arrow.
- *
- * `asChild` draws it on the shared `Surface`, which is what keeps a popover
- * and a select open on the same screen from having different corners. Only the
- * padding is a popover's own.
- */
 export declare const PopoverContent: import('react').ForwardRefExoticComponent<PopoverContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/Feedback/Tooltip/TooltipContent.d.ts

@@ -3,5 +3,4 @@ export interface TooltipContentProps extends React.ComponentPropsWithoutRef<type
     showArrow?: boolean;
     dataTestid: string;
 }
-/** TooltipContent — portalled Radix tooltip content with optional arrow. */
 export declare const TooltipContent: import('react').ForwardRefExoticComponent<TooltipContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/Forms/Inputs/Combobox/ComboboxContent.d.ts

@@ -4,15 +4,4 @@ export interface ComboboxContentProps extends Omit<React.ComponentPropsWithoutRe
     sideOffset?: number;
     align?: 'start' | 'center' | 'end';
 }
-/**
- * ComboboxContent — the popover surface and the scrollable list in one.
- * `@radix-ui/react-popover` provides the portal + positioning; `cmdk`'s `Command`
- * provides item filtering. A visually-hidden `CommandInput` receives the shared
- * search string so typing in the anchored input filters the list.
- *
- * `asChild` puts the shared `Surface` where the popover content element would
- * be, and the shared viewport where cmdk's list would be, so a combobox and a
- * select are the same card with the same padding by construction rather than
- * by two stylesheets agreeing.
- */
 export declare const ComboboxContent: import('react').ForwardRefExoticComponent<ComboboxContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/Forms/Inputs/SearchPanel/SearchPanelList.d.ts

@@ -1,36 +1,5 @@
 import { CommandList } from 'cmdk';
 export type SearchPanelListProps = React.ComponentPropsWithoutRef<typeof CommandList>;
-/**
- * The scrolling list of groups and rows — `role="listbox"` and the rows in it —
- * on a card that floats over the page.
- *
- * **It floats, and that is the point.** In the flow it pushed everything below
- * the panel down the moment an answer landed, which is not what a dropdown does
- * and is disqualifying for a search that lives in a header. The card is
- * positioned by Radix's popper against the anchor `SearchPanel` wraps around
- * itself, so it is exactly the field's width, it flips above the field when
- * there is no room below, and it is `position: fixed` — no ancestor's
- * `overflow` can clip it.
- *
- * **No portal, and that is also the point.** Everything the keyboard is made of
- * is a relationship between this list and the field above it: cmdk gathers the
- * rows by querying the `Command` element they sit inside, `aria-activedescendant`
- * on the field points at a row's `id`, and the panel's custom properties reach
- * the rows by inheriting down the tree. A `Popover.Portal` would move the rows
- * out of `Command` entirely, and the arrows would stop finding them.
- * Popper-positioned content does not need a portal to escape the flow —
- * `position: fixed` already does — so it does not get one.
- *
- * The two auto-focus events are prevented for the same reason. A popover
- * focuses its content when it opens and hands focus back when it closes; both
- * would take focus off the search field, which is the one thing the arrow keys
- * depend on. `role="presentation"` and the blanked `aria-labelledby` finish the
- * job: the primitive believes it is a dialog, a screen reader must not, and the
- * name it points at belongs to a trigger this panel does not have. Radix
- * spreads the caller's props *after* its own `role`, so saying so here is
- * enough — the Vue port has to write the same two attributes one level further
- * down, where reka merges last.
- */
 export declare const SearchPanelList: import('react').ForwardRefExoticComponent<Omit<{
     children?: React.ReactNode;
 } & Pick<Pick<import('react').DetailedHTMLProps<import('react').HTMLAttributes<HTMLDivElement>, HTMLDivElement>, "key" | keyof import('react').HTMLAttributes<HTMLDivElement>> & {

package/dist/Forms/Inputs/Select/SelectContent.d.ts

@@ -4,14 +4,4 @@ export interface SelectContentProps extends Omit<React.ComponentPropsWithoutRef<
     sideOffset?: number;
     align?: 'start' | 'center' | 'end';
 }
-/**
- * The floating list. Always positioned against the trigger rather than over it,
- * so the popup matches the trigger's width and never covers it.
- *
- * `asChild` hands the primitive's positioning, `data-state` and `data-side` to
- * the shared `Surface`, which is the one element `Popover`, `Select`,
- * `Combobox` and `SearchPanel` may have in common. Exactly one child sits at
- * each slot position — Radix's `Slot` throws on a second, which is the whole
- * reason the arrangement is safe to read at a glance.
- */
 export declare const SelectContent: import('react').ForwardRefExoticComponent<SelectContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/main.d.ts

@@ -25,7 +25,7 @@ export { NumberFlow as OxNumberFlow, resolveNumberFlowPreset, NUMBER_FLOW_PRESET
 export { PaymentCard as OxPaymentCard, paymentCardVariants, type PaymentCardVariants, type BadgeType, type CardData, } from './Display/PaymentCard/index.ts';
 export { FileCard as OxFileCard } from './Display/FileCard/index.ts';
 export { FilePreviewCard as OxFilePreviewCard } from './Display/FilePreviewCard/index.ts';
-export { ChatBubble as OxChatBubble, chatBubbleVariants, type ChatBubbleVariants, } from './Display/ChatBubble/index.ts';
+export { ChatBubble as OxChatBubble, chatBubbleVariants, type ChatBubbleDelivery, type ChatBubbleVariants, } from './Display/ChatBubble/index.ts';
 export { ChatBubbleStatus as OxChatBubbleStatus, chatBubbleStatusVariants, type ChatBubbleStatusVariants, } from './Display/ChatBubble/ChatBubbleStatus/index.ts';
 export { Chip as OxChip, chipVariants, type ChipVariants, } from './Display/Chip/index.ts';
 export { PointMarker as OxPointMarker, pointMarkerVariants, type PointMarkerVariants, } from './Display/PointMarker/index.ts';