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

package/dist/ai/BbCheckbox.md

@@ -447,8 +447,6 @@ for the children.
 				v-model="granted"
 				class="pl-5"
 				hide-legend
-				item-text="label"
-				item-value="value"
 				:items="scopes"
 				legend="Scopes"
 				name="scope-list"

package/dist/ai/BbCheckboxGroup.md

@@ -58,18 +58,14 @@ Reach elsewhere when the shape differs:
 
 ### Items are your domain objects
 
-**Object items need `item-text`.** Without it each label is
-`JSON.stringify(item)`, and without `item-value` the whole object is the value.
-`{ label, value }` items take both:
+**`{ label, value }` and `{ text, value }` items work as they are; any other
+shape needs `item-text` / `item-value`.** With neither prop an option reads its
+own `label` (else its own `text`) and its own `value`, whatever it holds (`null`
+included). An object with none of those fields falls back to
+`JSON.stringify(item)` as text and the whole object as value.
 
 ```vue
-<BbCheckboxGroup
-	v-model="plans"
-	legend="Plans"
-	:items="options"
-	item-text="label"
-	item-value="value"
-/>
+<BbCheckboxGroup v-model="plans" legend="Plans" :items="options" />
 ```
 
 Pass backend rows straight to `items` and select the display text and stored
@@ -92,7 +88,6 @@ mapped (here, channel ids), which is what you send back to the server.
 			v-model="selected"
 			compact
 			hint="Choose one or more channels."
-			item-text="label"
 			item-value="id"
 			:items="channels"
 			legend="Channels"
@@ -141,7 +136,8 @@ Two items that resolve to the **same** `item-value` collapse to one option
 
 #### Additional row fields: `item-props`
 
-`item-text` and `item-value` are the option's label and identity. Anything
+The option's text and value (from `item-text` / `item-value`, or the item's own
+`label` and `value`) are its label and identity. Anything
 **additional** about a row comes from `item-props` — for option groups that is
 one field, `description`: a muted line **under** the option's label, beside the
 control.
@@ -333,7 +329,6 @@ on the row, feed that field to the predicate.
 			v-model="selected"
 			compact
 			hint="SMS unlocks once a sender number is configured."
-			item-text="label"
 			item-value="id"
 			:items="channels"
 			legend="Channels"
@@ -665,7 +660,6 @@ border) — floating mode is not supported for checkbox groups.
 					? 'Select at least one contact method.'
 					: undefined
 			"
-			item-text="label"
 			item-value="id"
 			:items="options"
 			legend="Contact permissions"
@@ -731,7 +725,6 @@ Read-only, with no cleanup code.
 		<BbRadioGroup
 			v-model="role"
 			compact
-			item-text="label"
 			item-value="id"
 			:items="roles"
 			legend="Token role"
@@ -745,7 +738,6 @@ Read-only, with no cleanup code.
 			:deps-debounce-time="150"
 			enforce-coherence
 			hint="Scopes outside the selected role are removed automatically."
-			item-text="label"
 			item-value="id"
 			:items="loadScopes"
 			legend="Scopes"
@@ -947,8 +939,9 @@ for a preset that fits any row type (never `<any>`), not an imported
   `disabled`.
 - `readonly` still submits its values and stays focusable; use `disabled` only
   for choices that genuinely don't apply.
-- Don't pre-map `items` into `{ label, value }` — pass raw rows and resolve with
-  `item-text` / `item-value`.
+- Don't pre-map domain rows into `{ label, value }` copies — pass raw rows and
+  resolve with `item-text` / `item-value` (a list that already is
+  `{ label, value }` needs neither).
 - A native (non-JS) form post needs `name`: the group generates none, unlike
   `BbRadioGroup`, where the name is what ties the options together. Independent
   boxes need no tie, so with `v-model` alone leave it off.
@@ -1004,8 +997,8 @@ for a preset that fits any row type (never `<any>`), not an imported
 | `itemProps` | `BbOptionGroupItemProps<T> \| undefined` |  |  | ADDITIONAL row fields resolved from each item — never its text or value (those stay on `itemText` / `itemValue`). Option groups accept one field: - `description` — a muted line under the option label, beside the control; it may wrap. Either an object with a path or getter per field (`{ description: 'email' }`) or a function returning the fields (`(item) => ({ description: item.email })`). Without it no field renders — an item's own `description` is never read implicitly — and an empty value renders nothing for that item. The description is announced as the option's description, never part of its name. To disable individual options use `selectable`. |
 | `itemReverse` | `boolean \| undefined` | `false` |  | Swaps each row's input and label from their natural order (input first), in every `item-layout`. `reverse` swaps the legend and the options instead. |
 | `items` | `T[] \| ((context: BbCheckboxGroupItemsContext) => T[] \| Promise<T[]>)` |  | yes | The options: an array, or a provider function called with ONE context object and returning the rows, sync or async. The context carries: - `reason` — why this call happened: `'initial'` (the first load, on mount), `'dependencies'` (a `dependencies` entry or the `items` function changed; a retry arrives this way) or `'model'` (the model changed from outside and the options cannot resolve it). The group has no search field, so it never passes `query`; - `modelValue` — the `v-model` as-is; - `signal` — an `AbortSignal`, aborted when a newer call starts or the group is disposed; pass it to every request. A provider signals a failure by THROWING, never by returning `[]`: the rows are cleared, nothing is pruned, and `#empty` receives the `error` (`failed-text` is shown). Zero-argument providers keep working. Annotate the parameter `BbCheckboxGroupItemsContext` (`BbSwitchGroupItemsContext` on a switch group, the same shape). |
-| `itemText` | `ItemAccessor<T, string> \| undefined` | `JSON.stringify(item)` |  | Defines a path that returns a property of the object to use as text or a function that returns a string. |
-| `itemValue` | `ItemAccessor<T> \| undefined` | `the whole item` |  | Defines a path that returns a property of the object to use as value or a function that returns any value. |
+| `itemText` | `ItemAccessor<T, string> \| undefined` | `own `label`, else `text`, else `JSON.stringify(item)`` |  | Defines a path that returns a property of the object to use as text or a function that returns a string. Unset: own `label`, else `text` (`{ label, value }` needs no accessor). |
+| `itemValue` | `ItemAccessor<T> \| undefined` | `own `value`, else the whole item` |  | Defines a path that returns a property of the object to use as value or a function that returns any value. Unset: own `value`, even `null`. |
 | `labelAlign` | `'top'` \| `'center'` \| `'bottom'` |  |  | Vertical position of the label block in a side-by-side row; not `labelPosition`, the horizontal one. Omitted, the label's first line meets the control's. |
 | `layout` | `FieldLayout \| undefined` |  |  | How the label and the input sit together: `'vertical'`, `'horizontal'` (50/50), `'auto'`, `'label-fill'` (the label takes the free space, the input keeps its size), `'input-fill'` (the other way round), or a two-word ratio pattern like `'xx xxxxx'`. |
 | `legend` | `string` |  | yes | Text content of the legend. |

package/dist/ai/BbDatePickerInput.md

@@ -179,7 +179,9 @@ entirely, reach for `disableWriting` (below), not `range`.
 The value is edited as three separate inputs — day, month, year — not one free
 string. Their **order and separator follow `config.locale`**, read from the
 locale's own format hint: `en` renders `MM/DD/YYYY`, `it` `DD/MM/YYYY`, `de`
-`TT.MM.JJJJ`, `ja` `YYYY/MM/DD`. Typing is forgiving:
+`TT.MM.JJJJ`, `ja` `YYYY/MM/DD`. A region writes its own order with its
+language's letters: `en-GB` `DD/MM/YYYY`, `fr-CA` `AAAA-MM-JJ`. Typing is
+forgiving:
 
 - digits **auto-advance** to the next segment when a segment fills (or can't
   take another digit — e.g. `4` in a day segment becomes `04` and moves on);
@@ -214,7 +216,7 @@ to catch config mistakes early — always pass the `YYYY-MM-DD` shape.
 For non-contiguous rules (no weekends, no holidays, only in-stock slots), pass a
 `selectable` predicate: it receives each date string and returns `false` to
 disable that day. The grid's week starts on the locale's day (Monday for
-`it` or `de`, Sunday for bare `en` and `pt`); `firstDayOfWeek` pins it
+`it`, `de` or `en-GB`, Sunday for bare `en`, `pt` and `en-CA`); `firstDayOfWeek` pins it
 (`0` = Sunday … `6` = Saturday) when the app's week differs from its
 language's.
 

package/dist/ai/BbDialog.md

@@ -402,14 +402,7 @@ dismissed invite doesn't resurface half-typed:
 				placeholder="teammate@company.com"
 				type="email"
 			/>
-			<BbSelect
-				v-model="role"
-				compact
-				item-text="label"
-				item-value="value"
-				:items="roles"
-				label="Role"
-			/>
+			<BbSelect v-model="role" compact :items="roles" label="Role" />
 			<p class="m-0 text-xs text-(--bb-text-muted)">
 				They'll get an email with a link that expires in 7 days.
 			</p>