rei-kit 3.1.0 → 3.2.1

package/dist/components/BaseDatePicker.vue.d.ts

@@ -34,6 +34,14 @@ declare const __VLS_export: <M extends "single" | "range" = "single">(__VLS_prop
         size?: "sm" | "md" | undefined;
         labelHidden?: boolean | undefined;
         disabled?: boolean | undefined;
+        /**
+         * Ties the generated id to a name you choose, so `ErrorSummary` can link
+         * to this field. Its links point at nothing without it, and the kit's
+         * own `FormField` has taken one since 2.22.0 while the fields built on
+         * it did not — which left building a form out of these and summarising
+         * its errors impossible without hand-writing the control.
+         */
+        fieldId?: string | undefined;
     } & {
         /** The chosen day, or range, with `v-model`. */
         modelValue?: (M extends "range" ? DateRange : string) | undefined;

package/dist/components/BaseInput.vue.d.ts

@@ -34,6 +34,14 @@ declare const __VLS_export: <T extends string | number | undefined = string>(__V
          * paint.
          */
         variant?: "default" | "unstyled" | undefined;
+        /**
+         * Ties the generated id to a name you choose, so `ErrorSummary` can link
+         * to this field. Its links point at nothing without it, and the kit's
+         * own `FormField` has taken one since 2.22.0 while the fields built on
+         * it did not — which left building a form out of these and summarising
+         * its errors impossible without hand-writing the control.
+         */
+        fieldId?: string | undefined;
     } & Omit<InputHTMLAttributes, "type" | "size">) & {
         "onUpdate:modelValue"?: (value: T) => any;
     }> & (typeof globalThis extends {

package/dist/components/BaseSelect.vue.d.ts

@@ -36,6 +36,14 @@ declare const __VLS_export: <T extends string | number>(__VLS_props: NonNullable
          * paint.
          */
         variant?: "default" | "unstyled" | undefined;
+        /**
+         * Ties the generated id to a name you choose, so `ErrorSummary` can link
+         * to this field. Its links point at nothing without it, and the kit's
+         * own `FormField` has taken one since 2.22.0 while the fields built on
+         * it did not — which left building a form out of these and summarising
+         * its errors impossible without hand-writing the control.
+         */
+        fieldId?: string | undefined;
     } & {
         modelValue?: T | undefined;
     }) & {

package/dist/components/BaseTextarea.vue.d.ts

@@ -27,6 +27,14 @@ type __VLS_Props = {
      * paint.
      */
     variant?: 'default' | 'unstyled' | undefined;
+    /**
+     * Ties the generated id to a name you choose, so `ErrorSummary` can link
+     * to this field. Its links point at nothing without it, and the kit's
+     * own `FormField` has taken one since 2.22.0 while the fields built on
+     * it did not — which left building a form out of these and summarising
+     * its errors impossible without hand-writing the control.
+     */
+    fieldId?: string | undefined;
 };
 declare const __VLS_export: import('vue').DefineComponent<__VLS_Props, {}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {
     "update:modelValue": (value: string) => any;

package/dist/components/ColorPicker.vue.d.ts

@@ -48,6 +48,14 @@ type __VLS_Props = {
     error?: string | undefined;
     disabled?: boolean | undefined;
     labelHidden?: boolean | undefined;
+    /**
+     * Ties the generated id to a name you choose, so `ErrorSummary` can link
+     * to this field. Its links point at nothing without it, and the kit's
+     * own `FormField` has taken one since 2.22.0 while the fields built on
+     * it did not — which left building a form out of these and summarising
+     * its errors impossible without hand-writing the control.
+     */
+    fieldId?: string | undefined;
 };
 declare const __VLS_export: import('vue').DefineComponent<__VLS_Props, {}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {
     "update:modelValue": (value: string) => any;

package/dist/components/NumberInput.vue.d.ts

@@ -27,6 +27,14 @@ type __VLS_Props = {
     size?: 'sm' | 'md' | undefined;
     labelHidden?: boolean | undefined;
     disabled?: boolean | undefined;
+    /**
+     * Ties the generated id to a name you choose, so `ErrorSummary` can link
+     * to this field. Its links point at nothing without it, and the kit's
+     * own `FormField` has taken one since 2.22.0 while the fields built on
+     * it did not — which left building a form out of these and summarising
+     * its errors impossible without hand-writing the control.
+     */
+    fieldId?: string | undefined;
 };
 type __VLS_ModelProps = {
     /** The number, with `v-model`. `undefined` while the field is empty. */

package/dist/components/SectionHeading.vue.d.ts

@@ -16,6 +16,12 @@ export interface Tone {
  * that knows its own categories anyway.
  */
 type __VLS_Props = {
+    /**
+     * The colour classes for the dot and the label, as written-out class names.
+     * `Tone` is a pair rather than a role token because the categories here are
+     * the app's own, and Tailwind reads source as plain text: a class assembled
+     * at runtime never reaches the stylesheet.
+     */
     tone: Tone;
     label: string;
     /** Hidden when zero, so an empty group's heading stays quiet. */

package/dist/components/StatCard.vue.d.ts

@@ -8,6 +8,11 @@
  * flat figure.
  */
 type __VLS_Props = {
+    /**
+     * Already formatted — "₺1.240", "68%", "12 days". A number would make this
+     * component choose a currency, a locale and a number of decimals, which are
+     * three product decisions it has no way to be right about.
+     */
     value: string;
     label: string;
     trend?: 'up' | 'down' | 'flat' | null | undefined;

package/dist/components/TagsInput.vue.d.ts

@@ -27,6 +27,14 @@ type __VLS_Props = {
     size?: 'sm' | 'md' | undefined;
     labelHidden?: boolean | undefined;
     disabled?: boolean | undefined;
+    /**
+     * Ties the generated id to a name you choose, so `ErrorSummary` can link
+     * to this field. Its links point at nothing without it, and the kit's
+     * own `FormField` has taken one since 2.22.0 while the fields built on
+     * it did not — which left building a form out of these and summarising
+     * its errors impossible without hand-writing the control.
+     */
+    fieldId?: string | undefined;
 };
 type __VLS_ModelProps = {
     /** The tags, with `v-model`. */

package/dist/components/TimePicker.vue.d.ts

@@ -28,6 +28,14 @@ type __VLS_Props = {
     size?: 'sm' | 'md' | undefined;
     labelHidden?: boolean | undefined;
     disabled?: boolean | undefined;
+    /**
+     * Ties the generated id to a name you choose, so `ErrorSummary` can link
+     * to this field. Its links point at nothing without it, and the kit's
+     * own `FormField` has taken one since 2.22.0 while the fields built on
+     * it did not — which left building a form out of these and summarising
+     * its errors impossible without hand-writing the control.
+     */
+    fieldId?: string | undefined;
 };
 type __VLS_ModelProps = {
     /** The time as `HH:mm`, with `v-model`. */