bitboss-ui 3.0.0-beta.49 → 3.0.0-beta.50

package/dist/composables/formSubmitLock.d.ts

@@ -2,5 +2,7 @@ import { InjectionKey } from 'vue';
 export type FormSubmitLock = {
     /** A submit promise is pending and the form locks while it runs. */
     locked: () => boolean;
+    /** A submit promise is pending (with or without the lock): submit buttons spin. */
+    saving: () => boolean;
 };
 export declare const BB_FORM_SUBMIT_LOCK: InjectionKey<FormSubmitLock>;

package/dist/llms-full.txt

@@ -20757,7 +20757,8 @@ the save (nothing spins forever), and the error goes to
 save, for anything else you show meanwhile.
 
 To keep the fields editable during the save, set `disable-submit-lock` on the
-form.
+form. The submit button still spins while the save is pending: the prop only
+lifts the read-only lock.
 
 ### Saving in place: `snapshot()`
 
@@ -21316,7 +21317,7 @@ marker stays consistent with the rules.
 
 | Prop | Type | Default | Required | Description |
 | --- | --- | --- | --- | --- |
-| `disableSubmitLock` | `boolean \| undefined` | `false` |  | Keep the fields editable while a save runs. By default, while a `@submit` that returned a promise is pending, every field joined to the form is read-only (never disabled: values stay readable and focusable) and every `type="submit"` BbButton inside the form shows its spinner; both end when the promise settles. A `@submit` that returns nothing never locks. |
+| `disableSubmitLock` | `boolean \| undefined` | `false` |  | Keep the fields editable while a save runs. By default, while a `@submit` that returned a promise is pending, every field joined to the form is read-only (never disabled: values stay readable and focusable); it ends when the promise settles. A `@submit` that returns nothing never locks. The `type="submit"` BbButtons inside the form show their spinner while the save is pending either way: this prop does not stop that. |
 | `fieldErrors` | `Record<string, unknown> \| null \| undefined` |  |  | A server's validation errors, shown on the fields they name, for as long as they are in the object: `form.errors` from Inertia's `useForm()`, `$page.props.errors`, a Laravel 422 body you kept in a `ref`. Keys are field paths (`email`, `address.city`, `address[city]`, `lines.0.qty`); a value is a message or a list of them; a nested object reads as dot paths. `null`, `undefined` and anything that is not a message show nothing. A key no field on the form has is in `unmatchedErrors`. The page owns them: editing the field does not hide its message, the next object you pass does. They never block a submit, and a field's own rule errors show first. When new messages arrive after a submit, the first field that has one takes focus. For a one-off message the form drops once the user edits the field, call `setErrors` instead. |
 | `id` | `string \| undefined` |  |  | Explicit id, so anything outside the form can read and drive it through `useBbFormContext(id)` — a dialog footer's submit button, a page toolbar, a leave guard. It is also the `<form>`'s own id, so a native `<button form="id" type="submit">` outside it submits it. Omit it when the form is self-contained: the slot scope already carries the same state for chrome that lives inside. |
 | `keepValuesOnUnmount` | `boolean \| Ref<boolean, boolean> \| undefined` |  |  | Keep a field's value (and its place in `@submit`) when it unmounts — the `v-if` wizard step you left, a collapsed section. Off, an unmounted field drops out of the values. |
@@ -23157,7 +23158,8 @@ symbol alone does nothing. Clearing the last digit leaves the field empty (no
 lone `$`), so the placeholder and `required` keep working. A pasted amount,
 symbol and all (`$1,234.56`, `1.234,56 €`, `1,234 kg`), is read as the number;
 another currency's symbol is dropped and the amount kept, with no conversion.
-The unit follows the number's plural (`1 hr`, `2 hrs`), and at rest a screen
+The unit follows the number's plural (`1 day`, `2 days`; Greek `1 κιλό`,
+`2 κιλά`), and at rest a screen
 reader hears the amount spelled out (`1,234.50 US dollars`, `20 kilograms`).
 Percent is written the locale's way: `15%` in English and Italian, `15 %` in
 German and French, `%15` in Turkish. `unit` is typed: `kilowatt` and
@@ -23514,12 +23516,13 @@ Parts: `root` (the container), `label`, `description`, `message` (the errors / w
 States: `errors`, `warnings` (never beside errors), `loading`, `disabled`, `readonly`, `hasValue` (written `pt:box:has-value`). A name outside that list is a type error and an
 ESLint error.
 
-The currency line item above, restyled through those parts: muted affixes on
-`pt:prefix` / `pt:suffix`, tabular figures on `pt:input`, a primary edge on
+The currency line item above, restyled through those parts: the `$` comes
+from `currency` (it is text, so `pt:input` styles it), a muted note on
+`pt:suffix`, tabular figures on `pt:input`, a primary edge on
 `pt:box:has-value` (`0` still counts). The stepper buttons in the slot ring
 are yours, not a part.
 
-**pt:prefix / pt:suffix / pt:input — the invoice unit price**
+**pt:suffix / pt:input — the invoice unit price**
 
 ```vue
 <template>
@@ -23529,24 +23532,22 @@ are yours, not a part.
 		<div>
 			<p class="text-sm font-medium">Line item · INV-2048</p>
 			<p class="text-xs text-(--bb-text-muted)">
-				Currency stays in the chrome; the model is a clean number.
+				The dollar sign sits in the text; the model is a clean number.
 			</p>
 		</div>
 		<BbNumberInput
 			v-model="price"
 			compact
+			currency="USD"
 			label="Unit price"
-			:max-precision="2"
 			:min="0"
 			name="unit-price"
 			pt:box:has-value="border-(--bb-primary)"
 			pt:input="tabular-nums"
-			pt:prefix="text-(--bb-text-muted)"
 			pt:suffix="text-(--bb-text-muted)"
 			:step="0.5"
 		>
-			<template #prefix>$</template>
-			<template #suffix>USD</template>
+			<template #suffix>per unit</template>
 		</BbNumberInput>
 	</div>
 </template>
@@ -23556,8 +23557,9 @@ import { ref } from 'vue';
 import { BbNumberInput } from 'bitboss-ui';
 
 // Same currency line item as `PriceCurrencyAffixes.vue`, restyled through
-// passthrough: muted affixes on `pt:prefix` / `pt:suffix`, tabular figures
-// on `pt:input`, a primary edge on `pt:box:has-value` (`0` counts).
+// passthrough: the `$` comes from `currency` (inside the text, never in
+// `#prefix`), a muted note on `pt:suffix`, tabular figures on `pt:input`, a
+// primary edge on `pt:box:has-value` (`0` counts).
 const price = ref<number | null>(49.99);
 </script>
 ```
@@ -60330,7 +60332,8 @@ Global locale for the library's built-in strings (empty states, close/clear
 labels, screen-reader announcements, confirm buttons, …) and for the formats
 around them (dates, numbers, week start). The list is fixed and typed (see
 [Locales](#locales) below): a language (`it`, `de`, …), a region (`en-GB`,
-`de-CH`, `fr-CA`, …), or `pt-BR` / `pt-PT` / `zh-CN` / `zh-TW`. Shipping ≠
+`de-CH`, `fr-CA`, …), or a language with its own dictionaries per
+region: `es-MX`, `pt-BR` / `pt-PT`, `zh-CN` / `zh-TW` / `zh-HK`. Shipping ≠
 bundling: only the **enabled** locales enter your build (next option). Runtime
 switching: `useBbConfig().setConfig({ locale })` — to a locale you enabled.
 
@@ -66351,7 +66354,7 @@ Nothing here fails to compile — these change what existing code does.
     A `:loading="isSubmitting"` on the submit button is now redundant (drop
     it); a submit button outside the form still binds `loading` itself. A
     page that wants the fields editable during the save sets
-    `disable-submit-lock` on the form.
+    `disable-submit-lock` on the form (the submit button still spins).
 
 54. **A set of `group` toggle buttons is one Tab stop** (since
     3.0.0-beta.49). Adjacent `group` `BbButton`s that each bind a `v-model`

package/dist/llms-medium.txt

@@ -1551,7 +1551,8 @@ Global locale for the library's built-in strings (empty states, close/clear
 labels, screen-reader announcements, confirm buttons, …) and for the formats
 around them (dates, numbers, week start). The list is fixed and typed (see
 [Locales](#locales) below): a language (`it`, `de`, …), a region (`en-GB`,
-`de-CH`, `fr-CA`, …), or `pt-BR` / `pt-PT` / `zh-CN` / `zh-TW`. Shipping ≠
+`de-CH`, `fr-CA`, …), or a language with its own dictionaries per
+region: `es-MX`, `pt-BR` / `pt-PT`, `zh-CN` / `zh-TW` / `zh-HK`. Shipping ≠
 bundling: only the **enabled** locales enter your build (next option). Runtime
 switching: `useBbConfig().setConfig({ locale })` — to a locale you enabled.