@orianatech/pire 0.21.0 → 0.23.0

package/dist/components/forms/DatePicker.d.cts

@@ -1,12 +1,30 @@
 import type * as React from 'react';
 import type { DateValue } from 'react-aria-components';
-export interface DatePickerProps {
+export interface DatePickerProps<TFormat extends 'object' | 'iso' = 'object'> {
     label?: React.ReactNode;
-    value?: DateValue | null;
-    defaultValue?: DateValue | null;
-    onChange?: (value: DateValue | null) => void;
-    minValue?: DateValue;
-    maxValue?: DateValue;
+    /** A `DateValue`, or the `YYYY-MM-DD` string one arrived as — a value straight off a JSON
+     *  response needs no conversion. A datetime is accepted and trimmed to its date (`date`
+     *  columns commonly serialise as `"2026-08-14T00:00:00.000000Z"`); the time and zone are
+     *  discarded, because a `DateValue` is a calendar date and holds neither. A malformed date
+     *  shows as an empty field rather than throwing. */
+    value?: DateValue | string | null;
+    defaultValue?: DateValue | string | null;
+    onChange?: (value: (TFormat extends 'iso' ? string : DateValue) | null) => void;
+    /**
+     * The shape `onChange` emits.
+     *
+     * `'object'` (the default) emits the `@internationalized/date` `DateValue` this component has
+     * always emitted. `'iso'` emits the `YYYY-MM-DD` string a consumer sends back to its API, and
+     * `null` for an empty field. Input accepts both shapes in either mode.
+     */
+    valueFormat?: TFormat;
+    /** Earliest date that can be picked, in either shape `value` accepts. `null` and `undefined`
+     *  both mean "no bound", so a bound read out of the same state as the value needs no `??
+     *  undefined` on the way in. An unreadable bound stops applying rather than throwing. */
+    minValue?: DateValue | string | null;
+    /** Latest date that can be picked — see `minValue`. In a from/to pair each end bounds the
+     *  other, and both ends come out of the same state in the same shape. */
+    maxValue?: DateValue | string | null;
     /** Return true for dates that cannot be picked — factory calendar, blocked periods. */
     isDateUnavailable?: (date: DateValue) => boolean;
     description?: React.ReactNode;
@@ -24,4 +42,4 @@ export interface DatePickerProps {
 /** Date entry with a segmented field and a calendar popover. Segments follow the user's locale,
  *  so a German user types dd.mm.yyyy without any prop change. Wrap the app in React Aria's
  *  I18nProvider to pin a locale. */
-export declare function DatePicker({ label, description, errorMessage, size, fullWidth, className, style, ...rest }: DatePickerProps): React.JSX.Element;
+export declare function DatePicker<TFormat extends 'object' | 'iso' = 'object'>({ label, description, errorMessage, size, fullWidth, className, style, value, defaultValue, onChange, valueFormat, minValue, maxValue, ...rest }: DatePickerProps<TFormat>): React.JSX.Element;

package/dist/components/forms/DatePicker.d.ts

@@ -1,12 +1,30 @@
 import type * as React from 'react';
 import type { DateValue } from 'react-aria-components';
-export interface DatePickerProps {
+export interface DatePickerProps<TFormat extends 'object' | 'iso' = 'object'> {
     label?: React.ReactNode;
-    value?: DateValue | null;
-    defaultValue?: DateValue | null;
-    onChange?: (value: DateValue | null) => void;
-    minValue?: DateValue;
-    maxValue?: DateValue;
+    /** A `DateValue`, or the `YYYY-MM-DD` string one arrived as — a value straight off a JSON
+     *  response needs no conversion. A datetime is accepted and trimmed to its date (`date`
+     *  columns commonly serialise as `"2026-08-14T00:00:00.000000Z"`); the time and zone are
+     *  discarded, because a `DateValue` is a calendar date and holds neither. A malformed date
+     *  shows as an empty field rather than throwing. */
+    value?: DateValue | string | null;
+    defaultValue?: DateValue | string | null;
+    onChange?: (value: (TFormat extends 'iso' ? string : DateValue) | null) => void;
+    /**
+     * The shape `onChange` emits.
+     *
+     * `'object'` (the default) emits the `@internationalized/date` `DateValue` this component has
+     * always emitted. `'iso'` emits the `YYYY-MM-DD` string a consumer sends back to its API, and
+     * `null` for an empty field. Input accepts both shapes in either mode.
+     */
+    valueFormat?: TFormat;
+    /** Earliest date that can be picked, in either shape `value` accepts. `null` and `undefined`
+     *  both mean "no bound", so a bound read out of the same state as the value needs no `??
+     *  undefined` on the way in. An unreadable bound stops applying rather than throwing. */
+    minValue?: DateValue | string | null;
+    /** Latest date that can be picked — see `minValue`. In a from/to pair each end bounds the
+     *  other, and both ends come out of the same state in the same shape. */
+    maxValue?: DateValue | string | null;
     /** Return true for dates that cannot be picked — factory calendar, blocked periods. */
     isDateUnavailable?: (date: DateValue) => boolean;
     description?: React.ReactNode;
@@ -24,5 +42,5 @@ export interface DatePickerProps {
 /** Date entry with a segmented field and a calendar popover. Segments follow the user's locale,
  *  so a German user types dd.mm.yyyy without any prop change. Wrap the app in React Aria's
  *  I18nProvider to pin a locale. */
-export declare function DatePicker({ label, description, errorMessage, size, fullWidth, className, style, ...rest }: DatePickerProps): React.JSX.Element;
+export declare function DatePicker<TFormat extends 'object' | 'iso' = 'object'>({ label, description, errorMessage, size, fullWidth, className, style, value, defaultValue, onChange, valueFormat, minValue, maxValue, ...rest }: DatePickerProps<TFormat>): React.JSX.Element;
 //# sourceMappingURL=DatePicker.d.ts.map

package/dist/components/forms/DatePicker.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DatePicker.d.ts","sourceRoot":"","sources":["../../../src/components/forms/DatePicker.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,KAAK,MAAM,OAAO,CAAC;AAIpC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAKvD,MAAM,WAAW,eAAe;IAC9B,KAAK,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACxB,KAAK,CAAC,EAAE,SAAS,GAAG,IAAI,CAAC;IACzB,YAAY,CAAC,EAAE,SAAS,GAAG,IAAI,CAAC;IAChC,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,SAAS,GAAG,IAAI,KAAK,IAAI,CAAC;IAC7C,QAAQ,CAAC,EAAE,SAAS,CAAC;IACrB,QAAQ,CAAC,EAAE,SAAS,CAAC;IACrB,uFAAuF;IACvF,iBAAiB,CAAC,EAAE,CAAC,IAAI,EAAE,SAAS,KAAK,OAAO,CAAC;IACjD,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC9B,YAAY,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC/B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,IAAI,CAAC,EAAE,IAAI,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,KAAK,CAAC,aAAa,CAAC;CAC7B;AAED;;oCAEoC;AACpC,wBAAgB,UAAU,CAAC,EAAE,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,IAAW,EAAE,SAAgB,EAC1F,SAAS,EAAE,KAAK,EAAE,GAAG,IAAI,EAAE,EAAE,eAAe,qBA6C7C"}
+{"version":3,"file":"DatePicker.d.ts","sourceRoot":"","sources":["../../../src/components/forms/DatePicker.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,KAAK,MAAM,OAAO,CAAC;AAIpC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAMvD,MAAM,WAAW,eAAe,CAAC,OAAO,SAAS,QAAQ,GAAG,KAAK,GAAG,QAAQ;IAC1E,KAAK,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACxB;;;;wDAIoD;IACpD,KAAK,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IAClC,YAAY,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IACzC,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,CAAC,OAAO,SAAS,KAAK,GAAG,MAAM,GAAG,SAAS,CAAC,GAAG,IAAI,KAAK,IAAI,CAAC;IAChF;;;;;;OAMG;IACH,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB;;6FAEyF;IACzF,QAAQ,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IACrC;6EACyE;IACzE,QAAQ,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IACrC,uFAAuF;IACvF,iBAAiB,CAAC,EAAE,CAAC,IAAI,EAAE,SAAS,KAAK,OAAO,CAAC;IACjD,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC9B,YAAY,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC/B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,IAAI,CAAC,EAAE,IAAI,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,KAAK,CAAC,aAAa,CAAC;CAC7B;AAED;;oCAEoC;AACpC,wBAAgB,UAAU,CAAC,OAAO,SAAS,QAAQ,GAAG,KAAK,GAAG,QAAQ,EAAE,EAAE,KAAK,EAAE,WAAW,EAC1F,YAAY,EAAE,IAAW,EAAE,SAAgB,EAAE,SAAS,EAAE,KAAK,EAAE,KAAK,EAAE,YAAY,EAAE,QAAQ,EAC5F,WAAW,EAAE,QAAQ,EAAE,QAAQ,EAAE,GAAG,IAAI,EAAE,EAAE,eAAe,CAAC,OAAO,CAAC,qBAqDrE"}

package/dist/components/forms/DateRangePicker.d.cts

@@ -1,22 +1,56 @@
 import type * as React from 'react';
 import type { DateValue } from 'react-aria-components';
+/** A complete range: what this component emits, and what `rangeLengthInDays` measures. */
 export interface DateRange {
     start: DateValue;
     end: DateValue;
 }
+/** A complete range as ISO strings — what `onChange` emits under `valueFormat="iso"`. */
+export interface IsoDateRange {
+    start: string;
+    end: string;
+}
+/**
+ * What `value` accepts: either end in either shape, and either end absent.
+ *
+ * The two ends are read separately on purpose. An unreadable or empty end leaves *that* end
+ * without a date instead of voiding the whole range, so a caller can pass the two halves of its
+ * state straight through rather than guarding that both parsed before building an object. Deciding
+ * what counts as a usable range is this component's job, which is the point of the prop.
+ */
+export interface DateRangeInput {
+    start?: DateValue | string | null;
+    end?: DateValue | string | null;
+}
 export interface DateRangePreset {
     id: string;
     label: string;
-    /** The app computes the range: Pire cannot know when a customer's fiscal year starts. */
-    range: () => DateRange;
+    /** The app computes the range: Pire cannot know when a customer's fiscal year starts. It also
+     *  computes in whatever shape it stores, so either shape is accepted here. */
+    range: () => DateRangeInput;
 }
-export interface DateRangePickerProps {
+export interface DateRangePickerProps<TFormat extends 'object' | 'iso' = 'object'> {
     label?: React.ReactNode;
-    value?: DateRange | null;
-    defaultValue?: DateRange | null;
-    onChange?: (value: DateRange | null) => void;
-    minValue?: DateValue;
-    maxValue?: DateValue;
+    /** Either end in either shape — see `DateRangeInput`. A range whose ends are both empty is an
+     *  empty field. */
+    value?: DateRangeInput | null;
+    defaultValue?: DateRangeInput | null;
+    onChange?: (value: (TFormat extends 'iso' ? IsoDateRange : DateRange) | null) => void;
+    /**
+     * The shape `onChange` emits.
+     *
+     * `'object'` (the default) emits the `DateValue` pair this component has always emitted. `'iso'`
+     * emits `{ start: 'YYYY-MM-DD', end: 'YYYY-MM-DD' }`, the shape a consumer sends back to its API.
+     *
+     * Either way the emitted range is always complete or `null`: React Aria never reports half a
+     * range, even though it will happily *display* one while a caller is still filling it in.
+     */
+    valueFormat?: TFormat;
+    /** Earliest date either end can take, in either shape `value` accepts. `null` and `undefined`
+     *  both mean "no bound". An unreadable bound stops applying rather than throwing. */
+    minValue?: DateValue | string | null;
+    /** Latest date either end can take — see `minValue`. */
+    maxValue?: DateValue | string | null;
     /** Return true for dates that cannot be picked — blocked periods, closed books. */
     isDateUnavailable?: (date: DateValue) => boolean;
     /**
@@ -43,8 +77,15 @@ export interface DateRangePickerProps {
     className?: string;
     style?: React.CSSProperties;
 }
-/** Whole days between the two ends, inclusive of both. */
+/**
+ * Whole days between the two ends, inclusive of both.
+ *
+ * A complete `DateRange` measures to a number, which is the signature this has always had. Given
+ * the looser shape `value` now takes — either end a string, either end absent — it returns `null`
+ * for a range it cannot measure, so a caller holding two strings can pass them straight in.
+ */
 export declare function rangeLengthInDays(range: DateRange): number;
+export declare function rangeLengthInDays(range: DateRangeInput | null | undefined): number | null;
 /**
  * Two dates that belong together — the default filter on 24 ERP screens.
  *
@@ -52,4 +93,4 @@ export declare function rangeLengthInDays(range: DateRange): number;
  * between them, and locale-driven segment order. Wrap the app in `I18nProvider` to pin a locale:
  * `es-PY` reads dd/mm/yyyy and `en-US` mm/dd/yyyy off the same value.
  */
-export declare function DateRangePicker({ label, description, errorMessage, maxRangeDays, presets, size, fullWidth, startName, endName, className, style, ...rest }: DateRangePickerProps): React.JSX.Element;
+export declare function DateRangePicker<TFormat extends 'object' | 'iso' = 'object'>({ label, description, errorMessage, maxRangeDays, presets, size, fullWidth, startName, endName, className, style, value, defaultValue, onChange, valueFormat, minValue, maxValue, ...rest }: DateRangePickerProps<TFormat>): React.JSX.Element;

package/dist/components/forms/DateRangePicker.d.ts

@@ -1,22 +1,56 @@
 import type * as React from 'react';
 import type { DateValue } from 'react-aria-components';
+/** A complete range: what this component emits, and what `rangeLengthInDays` measures. */
 export interface DateRange {
     start: DateValue;
     end: DateValue;
 }
+/** A complete range as ISO strings — what `onChange` emits under `valueFormat="iso"`. */
+export interface IsoDateRange {
+    start: string;
+    end: string;
+}
+/**
+ * What `value` accepts: either end in either shape, and either end absent.
+ *
+ * The two ends are read separately on purpose. An unreadable or empty end leaves *that* end
+ * without a date instead of voiding the whole range, so a caller can pass the two halves of its
+ * state straight through rather than guarding that both parsed before building an object. Deciding
+ * what counts as a usable range is this component's job, which is the point of the prop.
+ */
+export interface DateRangeInput {
+    start?: DateValue | string | null;
+    end?: DateValue | string | null;
+}
 export interface DateRangePreset {
     id: string;
     label: string;
-    /** The app computes the range: Pire cannot know when a customer's fiscal year starts. */
-    range: () => DateRange;
+    /** The app computes the range: Pire cannot know when a customer's fiscal year starts. It also
+     *  computes in whatever shape it stores, so either shape is accepted here. */
+    range: () => DateRangeInput;
 }
-export interface DateRangePickerProps {
+export interface DateRangePickerProps<TFormat extends 'object' | 'iso' = 'object'> {
     label?: React.ReactNode;
-    value?: DateRange | null;
-    defaultValue?: DateRange | null;
-    onChange?: (value: DateRange | null) => void;
-    minValue?: DateValue;
-    maxValue?: DateValue;
+    /** Either end in either shape — see `DateRangeInput`. A range whose ends are both empty is an
+     *  empty field. */
+    value?: DateRangeInput | null;
+    defaultValue?: DateRangeInput | null;
+    onChange?: (value: (TFormat extends 'iso' ? IsoDateRange : DateRange) | null) => void;
+    /**
+     * The shape `onChange` emits.
+     *
+     * `'object'` (the default) emits the `DateValue` pair this component has always emitted. `'iso'`
+     * emits `{ start: 'YYYY-MM-DD', end: 'YYYY-MM-DD' }`, the shape a consumer sends back to its API.
+     *
+     * Either way the emitted range is always complete or `null`: React Aria never reports half a
+     * range, even though it will happily *display* one while a caller is still filling it in.
+     */
+    valueFormat?: TFormat;
+    /** Earliest date either end can take, in either shape `value` accepts. `null` and `undefined`
+     *  both mean "no bound". An unreadable bound stops applying rather than throwing. */
+    minValue?: DateValue | string | null;
+    /** Latest date either end can take — see `minValue`. */
+    maxValue?: DateValue | string | null;
     /** Return true for dates that cannot be picked — blocked periods, closed books. */
     isDateUnavailable?: (date: DateValue) => boolean;
     /**
@@ -43,8 +77,15 @@ export interface DateRangePickerProps {
     className?: string;
     style?: React.CSSProperties;
 }
-/** Whole days between the two ends, inclusive of both. */
+/**
+ * Whole days between the two ends, inclusive of both.
+ *
+ * A complete `DateRange` measures to a number, which is the signature this has always had. Given
+ * the looser shape `value` now takes — either end a string, either end absent — it returns `null`
+ * for a range it cannot measure, so a caller holding two strings can pass them straight in.
+ */
 export declare function rangeLengthInDays(range: DateRange): number;
+export declare function rangeLengthInDays(range: DateRangeInput | null | undefined): number | null;
 /**
  * Two dates that belong together — the default filter on 24 ERP screens.
  *
@@ -52,5 +93,5 @@ export declare function rangeLengthInDays(range: DateRange): number;
  * between them, and locale-driven segment order. Wrap the app in `I18nProvider` to pin a locale:
  * `es-PY` reads dd/mm/yyyy and `en-US` mm/dd/yyyy off the same value.
  */
-export declare function DateRangePicker({ label, description, errorMessage, maxRangeDays, presets, size, fullWidth, startName, endName, className, style, ...rest }: DateRangePickerProps): React.JSX.Element;
+export declare function DateRangePicker<TFormat extends 'object' | 'iso' = 'object'>({ label, description, errorMessage, maxRangeDays, presets, size, fullWidth, startName, endName, className, style, value, defaultValue, onChange, valueFormat, minValue, maxValue, ...rest }: DateRangePickerProps<TFormat>): React.JSX.Element;
 //# sourceMappingURL=DateRangePicker.d.ts.map

package/dist/components/forms/DateRangePicker.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"DateRangePicker.d.ts","sourceRoot":"","sources":["../../../src/components/forms/DateRangePicker.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,KAAK,MAAM,OAAO,CAAC;AAMpC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAKvD,MAAM,WAAW,SAAS;IACxB,KAAK,EAAE,SAAS,CAAC;IACjB,GAAG,EAAE,SAAS,CAAC;CAChB;AAED,MAAM,WAAW,eAAe;IAC9B,EAAE,EAAE,MAAM,CAAC;IACX,KAAK,EAAE,MAAM,CAAC;IACd,yFAAyF;IACzF,KAAK,EAAE,MAAM,SAAS,CAAC;CACxB;AAED,MAAM,WAAW,oBAAoB;IACnC,KAAK,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACxB,KAAK,CAAC,EAAE,SAAS,GAAG,IAAI,CAAC;IACzB,YAAY,CAAC,EAAE,SAAS,GAAG,IAAI,CAAC;IAChC,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,SAAS,GAAG,IAAI,KAAK,IAAI,CAAC;IAC7C,QAAQ,CAAC,EAAE,SAAS,CAAC;IACrB,QAAQ,CAAC,EAAE,SAAS,CAAC;IACrB,mFAAmF;IACnF,iBAAiB,CAAC,EAAE,CAAC,IAAI,EAAE,SAAS,KAAK,OAAO,CAAC;IACjD;;;;;;OAMG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,mEAAmE;IACnE,OAAO,CAAC,EAAE,eAAe,EAAE,CAAC;IAC5B,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC9B,YAAY,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC/B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,IAAI,CAAC,EAAE,IAAI,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,0CAA0C;IAC1C,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,KAAK,CAAC,aAAa,CAAC;CAC7B;AAED,0DAA0D;AAC1D,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,SAAS,GAAG,MAAM,CAG1D;AAED;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,EAC9B,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,YAAY,EAAE,OAAO,EAAE,IAAW,EAAE,SAAgB,EACtF,SAAS,EAAE,OAAO,EAAE,SAAS,EAAE,KAAK,EAAE,GAAG,IAAI,EAC9C,EAAE,oBAAoB,qBAiFtB"}
+{"version":3,"file":"DateRangePicker.d.ts","sourceRoot":"","sources":["../../../src/components/forms/DateRangePicker.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,KAAK,MAAM,OAAO,CAAC;AAMpC,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAMvD,0FAA0F;AAC1F,MAAM,WAAW,SAAS;IACxB,KAAK,EAAE,SAAS,CAAC;IACjB,GAAG,EAAE,SAAS,CAAC;CAChB;AAED,yFAAyF;AACzF,MAAM,WAAW,YAAY;IAC3B,KAAK,EAAE,MAAM,CAAC;IACd,GAAG,EAAE,MAAM,CAAC;CACb;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,cAAc;IAC7B,KAAK,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IAClC,GAAG,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;CACjC;AAED,MAAM,WAAW,eAAe;IAC9B,EAAE,EAAE,MAAM,CAAC;IACX,KAAK,EAAE,MAAM,CAAC;IACd;kFAC8E;IAC9E,KAAK,EAAE,MAAM,cAAc,CAAC;CAC7B;AAqBD,MAAM,WAAW,oBAAoB,CAAC,OAAO,SAAS,QAAQ,GAAG,KAAK,GAAG,QAAQ;IAC/E,KAAK,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACxB;uBACmB;IACnB,KAAK,CAAC,EAAE,cAAc,GAAG,IAAI,CAAC;IAC9B,YAAY,CAAC,EAAE,cAAc,GAAG,IAAI,CAAC;IACrC,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,CAAC,OAAO,SAAS,KAAK,GAAG,YAAY,GAAG,SAAS,CAAC,GAAG,IAAI,KAAK,IAAI,CAAC;IACtF;;;;;;;;OAQG;IACH,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB;yFACqF;IACrF,QAAQ,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IACrC,wDAAwD;IACxD,QAAQ,CAAC,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;IACrC,mFAAmF;IACnF,iBAAiB,CAAC,EAAE,CAAC,IAAI,EAAE,SAAS,KAAK,OAAO,CAAC;IACjD;;;;;;OAMG;IACH,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,mEAAmE;IACnE,OAAO,CAAC,EAAE,eAAe,EAAE,CAAC;IAC5B,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC9B,YAAY,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC/B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,IAAI,CAAC,EAAE,IAAI,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,0CAA0C;IAC1C,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,KAAK,CAAC,aAAa,CAAC;CAC7B;AAED;;;;;;GAMG;AACH,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,SAAS,GAAG,MAAM,CAAC;AAC5D,wBAAgB,iBAAiB,CAAC,KAAK,EAAE,cAAc,GAAG,IAAI,GAAG,SAAS,GAAG,MAAM,GAAG,IAAI,CAAC;AAQ3F;;;;;;GAMG;AACH,wBAAgB,eAAe,CAAC,OAAO,SAAS,QAAQ,GAAG,KAAK,GAAG,QAAQ,EAAE,EAC3E,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,YAAY,EAAE,OAAO,EAAE,IAAW,EAAE,SAAgB,EACtF,SAAS,EAAE,OAAO,EAAE,SAAS,EAAE,KAAK,EAAE,KAAK,EAAE,YAAY,EAAE,QAAQ,EAAE,WAAW,EAChF,QAAQ,EAAE,QAAQ,EAAE,GAAG,IAAI,EAC5B,EAAE,oBAAoB,CAAC,OAAO,CAAC,qBA6G/B"}

package/dist/components/forms/NumberField.d.cts

@@ -1,12 +1,27 @@
 import type * as React from 'react';
-export interface NumberFieldProps {
+export interface NumberFieldProps<TEmpty extends '' | null = never> {
     label?: React.ReactNode;
     /** Accessible name when `label` is omitted — e.g. in a table cell where the column header
      *  already carries the visible text. A field with neither is unnamed and fails axe. */
     'aria-label'?: string;
-    value?: number;
-    defaultValue?: number;
-    onChange?: (value: number) => void;
+    /** A figure, or the string one arrived as — a `decimal` column serialises as `"1500.00"`, so
+     *  a value straight off a JSON response needs no conversion. Strings are read with `Number`,
+     *  which is machine format only: `"1500.00"`, never the `"1.500,00"` the field *displays*
+     *  under es-PY. Anything unparseable shows as empty rather than as `NaN`. */
+    value?: number | string | null;
+    defaultValue?: number | string | null;
+    onChange?: (value: number | NoInfer<TEmpty>) => void;
+    /**
+     * What this field uses to mean "empty", in both directions: accepted in `value` and emitted by
+     * `onChange`.
+     *
+     * Defaults to `NaN`, which is what React Aria uses internally and what this component has
+     * always emitted. Declare `''` or `null` when the form is serialised to JSON: `NaN` does not
+     * survive `JSON.stringify` (it becomes `null`) and compares `false` against everything
+     * including itself, so a guard like `Math.abs(total) > 0` reads an empty field as a balanced
+     * one.
+     */
+    emptyValue?: TEmpty;
     minValue?: number;
     maxValue?: number;
     step?: number;
@@ -45,4 +60,4 @@ export interface NumberFieldProps {
  * Enable the action and validate when it is pressed, surfacing the reason. A disabled control that
  * does not say why is a worse affordance regardless, so the fix costs nothing.
  */
-export declare function NumberField({ label, suffix, description, errorMessage, hideStepper, size, fullWidth, className, style, ...rest }: NumberFieldProps): React.JSX.Element;
+export declare function NumberField<TEmpty extends '' | null = never>({ label, suffix, description, errorMessage, hideStepper, size, fullWidth, className, style, value, defaultValue, onChange, emptyValue, ...rest }: NumberFieldProps<TEmpty>): React.JSX.Element;

package/dist/components/forms/NumberField.d.ts

@@ -1,12 +1,27 @@
 import type * as React from 'react';
-export interface NumberFieldProps {
+export interface NumberFieldProps<TEmpty extends '' | null = never> {
     label?: React.ReactNode;
     /** Accessible name when `label` is omitted — e.g. in a table cell where the column header
      *  already carries the visible text. A field with neither is unnamed and fails axe. */
     'aria-label'?: string;
-    value?: number;
-    defaultValue?: number;
-    onChange?: (value: number) => void;
+    /** A figure, or the string one arrived as — a `decimal` column serialises as `"1500.00"`, so
+     *  a value straight off a JSON response needs no conversion. Strings are read with `Number`,
+     *  which is machine format only: `"1500.00"`, never the `"1.500,00"` the field *displays*
+     *  under es-PY. Anything unparseable shows as empty rather than as `NaN`. */
+    value?: number | string | null;
+    defaultValue?: number | string | null;
+    onChange?: (value: number | NoInfer<TEmpty>) => void;
+    /**
+     * What this field uses to mean "empty", in both directions: accepted in `value` and emitted by
+     * `onChange`.
+     *
+     * Defaults to `NaN`, which is what React Aria uses internally and what this component has
+     * always emitted. Declare `''` or `null` when the form is serialised to JSON: `NaN` does not
+     * survive `JSON.stringify` (it becomes `null`) and compares `false` against everything
+     * including itself, so a guard like `Math.abs(total) > 0` reads an empty field as a balanced
+     * one.
+     */
+    emptyValue?: TEmpty;
     minValue?: number;
     maxValue?: number;
     step?: number;
@@ -45,5 +60,5 @@ export interface NumberFieldProps {
  * Enable the action and validate when it is pressed, surfacing the reason. A disabled control that
  * does not say why is a worse affordance regardless, so the fix costs nothing.
  */
-export declare function NumberField({ label, suffix, description, errorMessage, hideStepper, size, fullWidth, className, style, ...rest }: NumberFieldProps): React.JSX.Element;
+export declare function NumberField<TEmpty extends '' | null = never>({ label, suffix, description, errorMessage, hideStepper, size, fullWidth, className, style, value, defaultValue, onChange, emptyValue, ...rest }: NumberFieldProps<TEmpty>): React.JSX.Element;
 //# sourceMappingURL=NumberField.d.ts.map

package/dist/components/forms/NumberField.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"NumberField.d.ts","sourceRoot":"","sources":["../../../src/components/forms/NumberField.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,KAAK,MAAM,OAAO,CAAC;AAkCpC,MAAM,WAAW,gBAAgB;IAC/B,KAAK,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACxB;2FACuF;IACvF,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,KAAK,IAAI,CAAC;IACnC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,sGAAsG;IACtG,aAAa,CAAC,EAAE,IAAI,CAAC,mBAAmB,CAAC;IACzC,uDAAuD;IACvD,MAAM,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACzB,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC9B,YAAY,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC/B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,+EAA+E;IAC/E,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,IAAI,CAAC,EAAE,IAAI,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,KAAK,CAAC,aAAa,CAAC;CAC7B;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,WAAW,CAAC,EAAE,KAAK,EAAE,MAAM,EAAE,WAAW,EAAE,YAAY,EAAE,WAAW,EAAE,IAAW,EAC9F,SAAgB,EAAE,SAAS,EAAE,KAAK,EAAE,GAAG,IAAI,EAAE,EAAE,gBAAgB,qBA2DhE"}
+{"version":3,"file":"NumberField.d.ts","sourceRoot":"","sources":["../../../src/components/forms/NumberField.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,KAAK,KAAK,MAAM,OAAO,CAAC;AAkCpC,MAAM,WAAW,gBAAgB,CAAC,MAAM,SAAS,EAAE,GAAG,IAAI,GAAG,KAAK;IAChE,KAAK,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACxB;2FACuF;IACvF,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB;;;iFAG6E;IAC7E,KAAK,CAAC,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAAC;IAC/B,YAAY,CAAC,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAAC;IAMtC,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,KAAK,IAAI,CAAC;IACrD;;;;;;;;;OASG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,sGAAsG;IACtG,aAAa,CAAC,EAAE,IAAI,CAAC,mBAAmB,CAAC;IACzC,uDAAuD;IACvD,MAAM,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IACzB,WAAW,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC9B,YAAY,CAAC,EAAE,KAAK,CAAC,SAAS,CAAC;IAC/B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,+EAA+E;IAC/E,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,IAAI,CAAC,EAAE,IAAI,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1B,SAAS,CAAC,EAAE,OAAO,CAAC;IACpB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,KAAK,CAAC,aAAa,CAAC;CAC7B;AAeD;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,WAAW,CAAC,MAAM,SAAS,EAAE,GAAG,IAAI,GAAG,KAAK,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,WAAW,EACxF,YAAY,EAAE,WAAW,EAAE,IAAW,EAAE,SAAgB,EAAE,SAAS,EAAE,KAAK,EAAE,KAAK,EAAE,YAAY,EAC/F,QAAQ,EAAE,UAAU,EAAE,GAAG,IAAI,EAAE,EAAE,gBAAgB,CAAC,MAAM,CAAC,qBA+D1D"}

package/dist/components/forms/dateValues.d.cts

@@ -0,0 +1,22 @@
+import type { DateValue } from 'react-aria-components';
+/**
+ * What React Aria is given for a date. `undefined` stays `undefined`, since that is what keeps an
+ * uncontrolled field uncontrolled — coercing it to `null` would silently disable `defaultValue`
+ * and freeze the field.
+ *
+ * The rest is why this belongs in the library: `parseDate` *throws* on a malformed date, and a bad
+ * date arriving from a server must empty one field, never unmount the screen. A datetime is
+ * trimmed to its date, because a `DateValue` is a calendar date and holds neither time nor zone.
+ */
+export declare function coerceDateValue(value: DateValue | string | null | undefined): DateValue | null | undefined;
+/**
+ * The same coercion for `minValue` / `maxValue`, where the two ways of saying "no bound" — `null`
+ * and `undefined` — collapse into the one React Aria's own types accept.
+ *
+ * Worth knowing which way this degrades: an unreadable *value* is visible, because the field shows
+ * empty. An unreadable *bound* is not — the constraint simply stops applying, and the user can
+ * pick a date the screen meant to forbid. Degrading still beats throwing, since a bound arriving
+ * malformed from a server should not take the screen down, but it is the quieter failure of the
+ * two.
+ */
+export declare function coerceBound(value: DateValue | string | null | undefined): DateValue | undefined;

package/dist/components/forms/dateValues.d.ts

@@ -0,0 +1,23 @@
+import type { DateValue } from 'react-aria-components';
+/**
+ * What React Aria is given for a date. `undefined` stays `undefined`, since that is what keeps an
+ * uncontrolled field uncontrolled — coercing it to `null` would silently disable `defaultValue`
+ * and freeze the field.
+ *
+ * The rest is why this belongs in the library: `parseDate` *throws* on a malformed date, and a bad
+ * date arriving from a server must empty one field, never unmount the screen. A datetime is
+ * trimmed to its date, because a `DateValue` is a calendar date and holds neither time nor zone.
+ */
+export declare function coerceDateValue(value: DateValue | string | null | undefined): DateValue | null | undefined;
+/**
+ * The same coercion for `minValue` / `maxValue`, where the two ways of saying "no bound" — `null`
+ * and `undefined` — collapse into the one React Aria's own types accept.
+ *
+ * Worth knowing which way this degrades: an unreadable *value* is visible, because the field shows
+ * empty. An unreadable *bound* is not — the constraint simply stops applying, and the user can
+ * pick a date the screen meant to forbid. Degrading still beats throwing, since a bound arriving
+ * malformed from a server should not take the screen down, but it is the quieter failure of the
+ * two.
+ */
+export declare function coerceBound(value: DateValue | string | null | undefined): DateValue | undefined;
+//# sourceMappingURL=dateValues.d.ts.map

package/dist/components/forms/dateValues.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"dateValues.d.ts","sourceRoot":"","sources":["../../../src/components/forms/dateValues.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,uBAAuB,CAAC;AAKvD;;;;;;;;GAQG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,SAAS,GAAG,IAAI,GAAG,SAAS,CAW1G;AAED;;;;;;;;;GASG;AACH,wBAAgB,WAAW,CAAC,KAAK,EAAE,SAAS,GAAG,MAAM,GAAG,IAAI,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,CAE/F"}