@jobber/components-native 0.112.0 → 0.112.1

package/dist/docs/InputNumber/InputNumber.md

@@ -1,20 +1,410 @@
 # InputNumber
 
-InputNumber is used in forms that accept numbers as an answer.
+## Summary
 
-## Design & usage guidelines
+`InputNumber` collects a single numeric value in a form. Reach for it when the
+value benefits from being nudged up or down, such as quantities, prices,
+durations, or counts.
 
-This is best suited for input data that benefits from being modified in
-increments, such as quantity, price, or days (ie 2 days -> 3 days).
+Most fields only need the props shown below. For rare layouts the props can't
+handle, you can build the same field from smaller pieces. See the **Implement**
+tab.
 
-While some types of data may technically be numbers, they can be ill-suited for
-using a number input. For example, phone numbers and credit card numbers provide
-no value to the user by offering an incrementer.
+### When to use
 
-## Clearable
+* The value is a number the user increments or decrements, like a quantity,
+  price, day count, or number of repetitions
+* A stepper, min/max bounds, or number formatting would help the user
 
-InputNumber does not show a clear button. The component enforces
-`clearable="never"` to align with numeric, increment/decrement-focused usage.
+### When not to use
+
+* The value is a sequence of digits that is never calculated with, such as phone
+  numbers, credit-card numbers, or postal codes. A stepper adds no value there;
+  use [InputText](../InputText/InputText.md) instead.
+
+## Anatomy
+
+`InputNumber` typically includes:
+
+* Label (required): names the value the field collects
+* Value field (required): the number the user types or steps through
+* Stepper (optional): increment and decrement controls that change the value by
+  `step`
+* Prefix or suffix (optional): a unit or symbol shown alongside the value, like
+  $ or kg
+* Loading indicator (optional): replaces the stepper while background work runs
+
+## Behavior
+
+* The field is controlled through `value`, where a number sets the value and
+  `null` leaves it empty.
+* `onValueCommitted` fires when the user commits a value: on blur, on Enter, or
+  when they use the stepper or arrow keys. Use `onValueChange` for per-keystroke
+  updates.
+* The stepper buttons and the Up and Down arrow keys change the value by `step`
+  (default 1).
+* `min` and `max` bound the value, and the stepper stops at each limit.
+* `loading` hides the stepper and shows an indicator in its place. The field
+  stays editable, so use `readOnly` or `disabled` to lock it.
+
+## Options
+
+### Basic
+
+Pass `label`, a controlled `value`, and `onValueCommitted`. Bounds (`min` /
+`max`) and `step` are optional.
+
+```tsx
+import React, { useState } from "react";
+import type { InputNumberProps } from "@jobber/components";
+import { InputNumber } from "@jobber/components";
+
+export function InputNumberBasicExample(props: Partial<InputNumberProps>) {
+  const [value, setValue] = useState<number | null>(3);
+
+  return (
+    <InputNumber
+      label="Quantity"
+      min={0}
+      max={100}
+      {...props}
+      value={value}
+      onValueCommitted={setValue}
+    />
+  );
+}
+```
+
+### Prefixes and suffixes
+
+Use `prefix` or `suffix` to add a unit or symbol. A suffix can be a label, an
+icon, or a clickable icon that runs an action (give it an `ariaLabel`).
+
+```tsx
+import React, { useState } from "react";
+import { InputNumber } from "@jobber/components";
+import { Content } from "@jobber/components/Content";
+
+export function InputNumberAffixesExample() {
+  const [price, setPrice] = useState<number | null>(42);
+  const [days, setDays] = useState<number | null>(7);
+  const [reps, setReps] = useState<number | null>(3);
+
+  return (
+    <Content>
+      <InputNumber
+        label="Price"
+        prefix={{ label: "$" }}
+        suffix={{ label: "USD" }}
+        value={price}
+        onValueCommitted={setPrice}
+      />
+
+      <InputNumber
+        label="Follow-up in"
+        suffix={{ icon: "calendar", label: "days" }}
+        value={days}
+        onValueCommitted={setDays}
+      />
+
+      <InputNumber
+        label="Repetitions"
+        suffix={{
+          icon: "cross",
+          ariaLabel: "Clear value",
+          onClick: () => setReps(null),
+        }}
+        value={reps}
+        onValueCommitted={setReps}
+      />
+    </Content>
+  );
+}
+```
+
+### Sizes
+
+3 sizes are available. `default` fits almost every form; use `small` only in
+tight spaces and `large` only in especially spacious layouts.
+
+```tsx
+import React, { useState } from "react";
+import { InputNumber } from "@jobber/components";
+import { Content } from "@jobber/components/Content";
+
+export function InputNumberSizesExample() {
+  const [small, setSmall] = useState<number | null>(42);
+  const [base, setBase] = useState<number | null>(42);
+  const [large, setLarge] = useState<number | null>(42);
+
+  return (
+    <Content>
+      <InputNumber
+        label="Small"
+        size="small"
+        suffix={{ label: "items" }}
+        value={small}
+        onValueCommitted={setSmall}
+      />
+      <InputNumber
+        label="Default"
+        size="default"
+        suffix={{ label: "items" }}
+        value={base}
+        onValueCommitted={setBase}
+      />
+      <InputNumber
+        label="Large"
+        size="large"
+        suffix={{ label: "items" }}
+        value={large}
+        onValueCommitted={setLarge}
+      />
+    </Content>
+  );
+}
+```
+
+### Formatting
+
+`format` takes any `Intl.NumberFormatOptions` and controls only how the value is
+displayed; the committed value stays a plain number. See the **Implement** tab
+for how percent and currency values map to the underlying number.
+
+```tsx
+import React, { useState } from "react";
+import { InputNumber } from "@jobber/components";
+import { Content } from "@jobber/components/Content";
+
+export function InputNumberFormattingExample() {
+  const [currency, setCurrency] = useState<number | null>(1234.5);
+  const [percent, setPercent] = useState<number | null>(0.5);
+  const [decimal, setDecimal] = useState<number | null>(11.13);
+
+  return (
+    <Content>
+      <InputNumber
+        label="Currency"
+        description='{ style: "currency", currency: "USD" }'
+        format={{ style: "currency", currency: "USD" }}
+        value={currency}
+        onValueCommitted={setCurrency}
+      />
+      <InputNumber
+        label="Percent"
+        description='{ style: "percent" } — value is a ratio: 0.5 → 50%'
+        format={{ style: "percent", maximumFractionDigits: 2 }}
+        value={percent}
+        onValueCommitted={setPercent}
+      />
+      <InputNumber
+        label="Decimal"
+        description="{ maximumFractionDigits: 2 }"
+        format={{ maximumFractionDigits: 2 }}
+        value={decimal}
+        onValueCommitted={setDecimal}
+      />
+    </Content>
+  );
+}
+```
+
+### Loading
+
+`loading` shows a non-blocking indicator in the stepper's slot for background
+work, like saving. The field stays editable and the stepper is hidden while
+loading.
+
+```tsx
+import React, { useState } from "react";
+import { InputNumber } from "@jobber/components";
+
+export function InputNumberLoadingExample() {
+  const [value, setValue] = useState<number | null>(42);
+
+  return (
+    <InputNumber
+      loading
+      label="Quantity"
+      suffix={{ label: "items" }}
+      value={value}
+      onValueCommitted={setValue}
+    />
+  );
+}
+```
+
+## Content guidelines
+
+### Label the unit, don't repeat it
+
+Put the unit in the label or an affix, not both.
+
+| ✅ Do                            | ❌ Don't                                 |
+| ------------------------------- | --------------------------------------- |
+| Label "Weight", suffix "kg"     | Label "Weight (kg)", suffix "kg"        |
+| Label "Duration", suffix "days" | Label "Duration in days", suffix "days" |
+
+### Keep labels short and sentence case
+
+| ✅ Do     | ❌ Don't                 |
+| -------- | ----------------------- |
+| Quantity | Enter the quantity here |
+| Discount | DISCOUNT %              |
+
+### Put the symbol where it's read
+
+Use a prefix for a leading symbol and a suffix for a trailing unit, matching how
+the value is spoken.
+
+| ✅ Do                 | ❌ Don't              |
+| -------------------- | -------------------- |
+| Prefix "$", value 40 | Suffix "$", value 40 |
+| Suffix "%", value 15 | Prefix "%", value 15 |
+
+### Keep validation errors helpful
+
+When a value breaks `min` or `max`, provide helpful guidance on what values will
+be accepted as opposed to just providing a generic error.
+
+| ✅ Do                           | ❌ Don't       |
+| ------------------------------ | ------------- |
+| Enter a value between 1 and 99 | Invalid input |
+| Quantity can't be more than 50 | Error         |
+
+### Use numbers as opposed to spelling them
+
+Use numerals in labels, helper text, affixes, and bounds.
+
+| ✅ Do        | ❌ Don't         |
+| ----------- | --------------- |
+| Max 3 items | Max three items |
+
+## Do's and Don'ts
+
+#### Do:
+
+* ✅ Use for values the user increments or decrements
+* ✅ Set `min` and `max` when the value has real bounds
+* ✅ Use `format` for currency, percent, and decimals rather than formatting the
+  value yourself
+* ✅ Use `loading` for background work so the field stays usable
+
+#### Don't:
+
+* ❌ Use it for digit sequences that are never calculated with, like phone or
+  credit card numbers
+* ❌ Disable the field to communicate an error; show an `error` message instead
+* ❌ Repeat the unit in both the label and an affix
+
+## Accessibility notes
+
+The field is a native number input, so it is reachable and operable by keyboard
+and assistive technology.
+
+| Key              | Behavior                        |
+| ---------------- | ------------------------------- |
+| Tab              | Moves focus to the field        |
+| Up / Down arrows | Increment / decrement by `step` |
+| Enter            | Commits the current value       |
+| Type             | Replaces the value              |
+
+Give a clickable affix a clear `ariaLabel` describing its action, like "Clear
+value".
+
+## Related components
+
+* For digit sequences that are not calculated with, like phone or credit card
+  numbers, use [InputText](../InputText/InputText.md).
+* For dates, use [InputDate](../InputDate/InputDate.md).
+
+
+## Anatomy
+
+The prop-driven `<InputNumber>` composes a set of parts. You only need these
+when the props can't express a layout; otherwise reach for the props shown on
+the **Design** tab.
+
+| Part                    | Description                                                          |
+| ----------------------- | -------------------------------------------------------------------- |
+| `Wrapper`               | Owns the field configuration and state; provides it to the parts     |
+| `Group`                 | The bordered field row                                               |
+| `Input`                 | The input area; holds the `Label` and the `Stepper` / `Loading` slot |
+| `Label`                 | Floating field label                                                 |
+| `Stepper`               | The increment / decrement button pair                                |
+| `Increment` `Decrement` | The individual stepper buttons                                       |
+| `Affix`                 | Prefix / suffix content (label, icon, or clickable icon)             |
+| `Loading`               | Non-blocking loading indicator slot                                  |
+| `Footer`                | Below-field row that holds `Description` and `Error`                 |
+| `Description`           | Helper text below the field                                          |
+| `Error`                 | Styled error message below the field                                 |
+
+## Composition
+
+The prop-driven component is sugar: it renders exactly the tree you would write
+by hand with `<InputNumber.Wrapper>` and the parts. To customize a single piece,
+compose the tree yourself and swap that one part — the other parts keep their
+defaults. The sugar does not merge consumer-provided parts into its render, so
+there is no per-slot precedence to reason about.
+
+`Wrapper` owns the field state and shares it with the parts through context, so
+every part must be rendered inside a `Wrapper` (a part used outside one throws).
+
+The example below replaces the default stepper icons with `+` / `−` and leaves
+everything else as the default:
+
+```tsx
+import React, { useState } from "react";
+import { InputNumber } from "@jobber/components";
+
+export function InputNumberCompositionExample() {
+  const [value, setValue] = useState<number | null>(3);
+
+  return (
+    <InputNumber.Wrapper value={value} onValueCommitted={setValue}>
+      <InputNumber.Group>
+        <InputNumber.Input>
+          <InputNumber.Label>Quantity</InputNumber.Label>
+          <InputNumber.Stepper>
+            <InputNumber.Increment ariaLabel="Increase Quantity">
+              +
+            </InputNumber.Increment>
+            <InputNumber.Decrement ariaLabel="Decrease Quantity">
+              −
+            </InputNumber.Decrement>
+          </InputNumber.Stepper>
+        </InputNumber.Input>
+      </InputNumber.Group>
+    </InputNumber.Wrapper>
+  );
+}
+```
+
+## Controlled usage
+
+The field is controlled: pass `value` (a `number`, or `null` for empty) and read
+changes back through one of two callbacks.
+
+| Callback           | Fires                                                       | Use for                            |
+| ------------------ | ----------------------------------------------------------- | ---------------------------------- |
+| `onValueChange`    | On every parsed change (typing, paste, stepper, arrow step) | Live-updating UI as the user types |
+| `onValueCommitted` | When the user commits (blur, Enter, stepper, arrow step)    | Saving / validating a final value  |
+
+Both emit `null` when the field is empty. Prefer `onValueCommitted` for
+persistence so you are not writing on every keystroke.
+
+## Formatting semantics
+
+`format` is forwarded to Base UI's `NumberField` `format` and accepts any
+`Intl.NumberFormatOptions`. It changes the display only; the committed value is
+always a plain number. Two things to know:
+
+* **Percent** (`{ style: "percent" }`) treats the value as a ratio: `0.5`
+  renders `50%`, and the stepper moves in ratio units. If you want the value to
+  be the number itself (`50` → `50%`), use `{ style: "unit", unit: "percent" }`.
+* With no `format`, typed decimals are preserved (up to 12 fractional digits)
+  and thousands grouping follows the locale default, so `1234.5` renders as
+  `1,234.5`. Pass `{ useGrouping: false }` to render without separators.
 
 
 ## Props

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@jobber/components-native",
-    "version": "0.112.0",
+    "version": "0.112.1",
     "license": "MIT",
     "description": "React Native implementation of Atlantis",
     "repository": {
@@ -74,7 +74,7 @@
         "@babel/runtime": "^7.29.2",
         "@gorhom/bottom-sheet": "^5.2.8",
         "@jobber/design": "0.111.0",
-        "@jobber/hooks": "2.21.0",
+        "@jobber/hooks": "2.21.1",
         "@react-native-community/datetimepicker": "^8.4.5",
         "@react-native/babel-preset": "^0.82.1",
         "@storybook/addon-a11y": "10.3.5",
@@ -124,5 +124,5 @@
         "react-native-screens": ">=4.18.0",
         "react-native-svg": ">=12.0.0"
     },
-    "gitHead": "71ed27026cd539889c5ce6c627bd74a8d283112e"
+    "gitHead": "2557e3892ae9903c706aebba90ff44bbb349618c"
 }