@lotics/ui 46.8.2 → 46.9.0

package/docs/catalog.md

@@ -1032,7 +1032,14 @@ source (`src/<module>.tsx`/`.ts`) is the API reference.
   differs from the visible text is what breaks label-in-name.
 - **`select`** — `Select`: rich/custom-rendered, single/multi, select-all, chips via
   `renderSelected(item, { remove })` + `searchable` + `allowCustom` — the tag field is just
-  a multi Select; opens `OptionList`. **Set `searchPlaceholder` whenever `allowCustom` is on**:
+  a multi Select; opens `OptionList`. **`emptyText` replaces the list's "No results" when the
+  caller knows what the reader should DO about it** — where the missing thing gets created, why the
+  set is narrowed. A select cannot know that; the reader is stuck at exactly that moment, and it is
+  the one place a list may speak without becoming permanent furniture, since it shows only when the
+  search finds nothing. Reach for it instead of a create-in-place row wherever the missing record
+  cannot be validly made from this screen: a vehicle needs its documents, a party needs its tax id,
+  and a stub minted here is a record that fails the next gate it meets.
+  **Set `searchPlaceholder` whenever `allowCustom` is on**:
   the create row only exists once there is a query, so on an untyped menu the placeholder is the
   only always-visible place that can say a new value is allowed. `customOptionLabel` names what
   the create row will

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "46.8.2",
+  "version": "46.9.0",
   "type": "module",
   "exports": {
     "./accordion": "./src/accordion.tsx",

package/src/inline_select.tsx

@@ -45,6 +45,13 @@ interface InlineSelectBaseProps<T extends string, D = unknown> {
   accessibilityLabel?: string;
   /** Show an in-menu search box; default false. */
   searchable?: boolean;
+  /** What the list says when it has nothing to offer — no options at all, or a
+   *  search that matched none. The default states the fact ("No results"); pass
+   *  this when the caller knows what the reader should DO about it, which the
+   *  list cannot know: where the missing thing is created, why the set is
+   *  narrowed. It is the one moment a select may speak without becoming
+   *  permanent furniture, because it appears only when the reader is stuck. */
+  emptyText?: string;
   /** Offer a "create" row when the query matches no option — picking it commits the
    *  typed value (single) / adds it to the set (multi). Implies `searchable`. */
   allowCustom?: boolean;
@@ -150,7 +157,7 @@ function InlineSelectShell(props: {
 }
 
 export function InlineSelect<T extends string, D = unknown>(props: InlineSelectProps<T, D>) {
-  const { options, renderOptionContent, getOptionDescription, placeholder, disabled, accessibilityLabel, searchable = false, allowCustom = false, customOptionLabel, customOptionPlacement, variant, actions, autoFocus = false } = props;
+  const { options, renderOptionContent, getOptionDescription, placeholder, disabled, accessibilityLabel, searchable = false, emptyText, allowCustom = false, customOptionLabel, customOptionPlacement, variant, actions, autoFocus = false } = props;
   const labels = useLoticsLocale().inline;
   const [open, setOpen] = useState(autoFocus);
   const [saving, setSaving] = useState(false);
@@ -239,6 +246,8 @@ export function InlineSelect<T extends string, D = unknown>(props: InlineSelectP
         <OptionList<T, true, D>
           multi
           getOptionDescription={getOptionDescription}
+          emptyText={emptyText}
+
           search={{ mode: searchMode }}
           options={options}
           value={draft}
@@ -286,6 +295,8 @@ export function InlineSelect<T extends string, D = unknown>(props: InlineSelectP
     >
       <OptionList<T, false, D>
         getOptionDescription={getOptionDescription}
+        emptyText={emptyText}
+
         search={{ mode: searchMode }}
         options={options}
         value={value}