@arsedizioni/ars-utils 22.6.85 → 22.6.88

package/types/arsedizioni-ars-utils-ui.dialogs.prompt.d.ts

@@ -1,8 +1,6 @@
-import * as _angular_forms_signals from '@angular/forms/signals';
-import * as _angular_core from '@angular/core';
-import { PromptDialogResult, PromptDialogData, PromptDateDialogResult, PromptTimeDialogData } from '@arsedizioni/ars-utils/ui';
-import { SignalsUtils } from '@arsedizioni/ars-utils/core.validators';
-
+import { PromptDateDialogResult, PromptDialogData, PromptDialogResult, PromptTimeDialogData } from "@arsedizioni/ars-utils/ui";
+import { SignalsUtils } from "@arsedizioni/ars-utils/core.validators";
+import * as i0 from "@angular/core";
 /**
  * Form model of the generic prompt.
  *
@@ -11,50 +9,51 @@ import { SignalsUtils } from '@arsedizioni/ars-utils/core.validators';
  * always owns the field. `value` stays `any` because its shape follows the prompt type.
  */
 interface PromptForm {
-    /** The prompted value: `''` for textual types, `null` for the number and list types. */
-    value: any;
+  /** The prompted value: `''` for textual types, `null` for the number and list types. */
+  value: any;
 }
-declare class PromptDialogComponent {
-    /** Error text of a field: the message declared in the schema, or the shared fallback. */
-    protected readonly getErrorMessage: typeof SignalsUtils.getFieldErrorMessage;
-    readonly done: _angular_core.OutputEmitterRef<PromptDialogResult>;
-    private readonly dialogService;
-    protected readonly dialogData: _angular_core.WritableSignal<PromptDialogData>;
-    /** Model backing the signal form. `value` type depends on the prompt type. */
-    private readonly model;
-    /**
-     * Builds the form model from the value carried by the dialog data.
-     *
-     * Ad-hoc because the empty value follows the prompt type: native inputs bound via
-     * `[formField]` report an empty number or an unselected option as `null`, while a
-     * text, date or textarea input reports `''`. The list type never takes an initial
-     * value: its options are matched by the template.
-     * @returns A fresh form model.
-     */
-    private toForm;
-    /**
-     * Builds the dialog result from the current form model.
-     *
-     * Ad-hoc because the result also carries the prompt type and the caller's `options`,
-     * which are not part of the form model; the value itself goes through
-     * {@link DtoUtils.toPayload}, so an input left empty travels as absent instead of as
-     * an empty string or a `null`.
-     * @returns The result to emit through `done`.
-     */
-    private toPayload;
-    /**
-     * Signal form for the prompt value. Validators mirror the previous template-driven
-     * form: `required` follows the dialog data, `min`/`max` apply to the Number type.
-     */
-    protected readonly form: _angular_forms_signals.FieldTree<PromptForm, string | number, "writable">;
-    /**
-     * Validates the form and emits the result, or shows an error if validation fails.
-     */
-    protected ok(): void;
-    static ɵfac: _angular_core.ɵɵFactoryDeclaration<PromptDialogComponent, never>;
-    static ɵcmp: _angular_core.ɵɵComponentDeclaration<PromptDialogComponent, "ng-component", never, {}, { "done": "done"; }, never, never, true, never>;
+export declare class PromptDialogComponent {
+  /** Error text of a field: the message declared in the schema, or the shared fallback. */
+  protected readonly getErrorMessage: typeof SignalsUtils.getFieldErrorMessage;
+  readonly done: import("@angular/core").OutputEmitterRef<PromptDialogResult>;
+  private readonly dialogService;
+  protected readonly dialogData: import("@angular/core").WritableSignal<PromptDialogData>;
+  /** Model backing the signal form. `value` type depends on the prompt type. */
+  private readonly model;
+  /**
+   * Builds the form model from the value carried by the dialog data.
+   *
+   * Ad-hoc because the empty value follows the prompt type: native inputs bound via
+   * `[formField]` report an empty number or an unselected option as `null`, while a
+   * text, date or textarea input reports `''`. The list type never takes an initial
+   * value: its options are matched by the template.
+   * @returns A fresh form model.
+   */
+  private toForm;
+  /**
+   * Builds the dialog result from the current form model.
+   *
+   * Ad-hoc because the result also carries the prompt type and the caller's `options`,
+   * which are not part of the form model; the value itself goes through
+   * {@link DtoUtils.toPayload}, so an input left empty travels as absent instead of as
+   * an empty string or a `null`.
+   * @returns The result to emit through `done`.
+   */
+  private toPayload;
+  /**
+   * Signal form for the prompt value. Validators mirror the previous template-driven
+   * form: `required` follows the dialog data, `min`/`max` apply to the Number type.
+   */
+  protected readonly form: import("@angular/forms/signals").FieldTree<PromptForm, string | number, "writable">;
+  /**
+   * Validates the form and emits the result, or shows an error if validation fails.
+   */
+  protected ok(): void;
+  static ɵfac: i0.ɵɵFactoryDeclaration<PromptDialogComponent, never>;
+  static ɵcmp: i0.ɵɵComponentDeclaration<PromptDialogComponent, "ng-component", never, {}, {
+    "done": "done";
+  }, never, never, true, never>;
 }
-
 /**
  * Form model of the date prompt.
  *
@@ -65,90 +64,91 @@ declare class PromptDialogComponent {
  * when a datepicker input is cleared.
  */
 interface PromptDateForm {
-    /** Value of the single-date type; `null` when the input is empty. */
-    date: Date | null;
-    /** Start of the range of the date-interval type; `null` when the input is empty. */
-    from: Date | null;
-    /** End of the range of the date-interval type; `null` when the input is empty. */
-    to: Date | null;
+  /** Value of the single-date type; `null` when the input is empty. */
+  date: Date | null;
+  /** Start of the range of the date-interval type; `null` when the input is empty. */
+  from: Date | null;
+  /** End of the range of the date-interval type; `null` when the input is empty. */
+  to: Date | null;
 }
-declare class PromptDateDialogComponent {
-    /** Error text of a field: the message declared in the schema, or the shared fallback. */
-    protected readonly getErrorMessage: typeof SignalsUtils.getFieldErrorMessage;
-    /**
-     * Error text for a date range: whichever end is in error speaks for the pair.
-     * @param from - Errors of the start field, from `f.from().errors()`.
-     * @param to   - Errors of the end field, from `f.to().errors()`.
-     * @returns The text to show under the range, or `undefined` when neither end is in error.
-     */
-    protected rangeErrorMessage(from: readonly {
-        kind: string;
-        message?: string;
-    }[], to: readonly {
-        kind: string;
-        message?: string;
-    }[]): string | undefined;
-    readonly done: _angular_core.OutputEmitterRef<PromptDateDialogResult>;
-    private readonly dialogService;
-    protected readonly dialogData: _angular_core.WritableSignal<PromptDialogData>;
-    /**
-     * Model backing the signal form: `date` serves the single-date type, while
-     * `from`/`to` serve the date-interval type. Empty values are `null` (not
-     * `undefined`) because signal forms only build child fields for keys whose
-     * value is defined, and Material's datepicker accessors report an empty
-     * input as `null` anyway; values are normalized to `undefined` on emit.
-     */
-    private readonly model;
-    /**
-     * Builds the form model from the value carried by the dialog data: a `Date` for the
-     * single-date type, a {@link DateInterval} for the date-interval one.
-     * @returns A fresh form model, empty when the dialog was opened without a value.
-     */
-    private toForm;
-    /**
-     * Builds the dialog result from the current form model.
-     *
-     * Ad-hoc because the two prompt types produce different values out of the same model
-     * — a `Date` or a {@link DateInterval} — and because the result also carries the type
-     * and the caller's `options`, which are not part of the form model. The dates
-     * themselves go through {@link DtoUtils.toPayload}, so a bound left empty travels as
-     * absent instead of as `null`.
-     * @returns The result to emit through `done`.
-     */
-    private toPayload;
-    /**
-     * Signal form for the date value(s). `required` follows the dialog data and only
-     * applies to the fields of the active prompt type; the datepicker's own parse
-     * validators are picked up through the ControlValueAccessor interop.
-     */
-    protected readonly form: _angular_forms_signals.FieldTree<PromptDateForm, string | number, "writable">;
-    /** Debounced stream of keyup events on the interval inputs (shorthand typing support). */
-    private readonly intervalKeyup;
-    constructor();
-    /**
-     * Blocks the space key on the interval inputs; it is reserved as the
-     * "copy the other bound" shortcut handled by onIntervalKeyup.
-     * @param event - The keydown event from the start or end date input.
-     */
-    protected onIntervalKeydown(event: KeyboardEvent): void;
-    /**
-     * Forwards keyup events of the interval inputs to the debounced shorthand parser.
-     * @param event - The keyup event from the start or end date input.
-     * @param end   - `true` when the event comes from the end-date input.
-     */
-    protected onIntervalKeyup(event: KeyboardEvent, end: boolean): void;
-    /**
-     * Clears both bounds of the date interval.
-     */
-    protected clearInterval(): void;
-    /**
-     * Validates the form and emits the result, or shows an error if validation fails.
-     */
-    protected ok(): void;
-    static ɵfac: _angular_core.ɵɵFactoryDeclaration<PromptDateDialogComponent, never>;
-    static ɵcmp: _angular_core.ɵɵComponentDeclaration<PromptDateDialogComponent, "ng-component", never, {}, { "done": "done"; }, never, never, true, never>;
+export declare class PromptDateDialogComponent {
+  /** Error text of a field: the message declared in the schema, or the shared fallback. */
+  protected readonly getErrorMessage: typeof SignalsUtils.getFieldErrorMessage;
+  /**
+   * Error text for a date range: whichever end is in error speaks for the pair.
+   * @param from - Errors of the start field, from `f.from().errors()`.
+   * @param to   - Errors of the end field, from `f.to().errors()`.
+   * @returns The text to show under the range, or `undefined` when neither end is in error.
+   */
+  protected rangeErrorMessage(from: readonly {
+    kind: string;
+    message?: string;
+  }[], to: readonly {
+    kind: string;
+    message?: string;
+  }[]): string | undefined;
+  readonly done: import("@angular/core").OutputEmitterRef<PromptDateDialogResult>;
+  private readonly dialogService;
+  protected readonly dialogData: import("@angular/core").WritableSignal<PromptDialogData>;
+  /**
+   * Model backing the signal form: `date` serves the single-date type, while
+   * `from`/`to` serve the date-interval type. Empty values are `null` (not
+   * `undefined`) because signal forms only build child fields for keys whose
+   * value is defined, and Material's datepicker accessors report an empty
+   * input as `null` anyway; values are normalized to `undefined` on emit.
+   */
+  private readonly model;
+  /**
+   * Builds the form model from the value carried by the dialog data: a `Date` for the
+   * single-date type, a {@link DateInterval} for the date-interval one.
+   * @returns A fresh form model, empty when the dialog was opened without a value.
+   */
+  private toForm;
+  /**
+   * Builds the dialog result from the current form model.
+   *
+   * Ad-hoc because the two prompt types produce different values out of the same model
+   * — a `Date` or a {@link DateInterval} — and because the result also carries the type
+   * and the caller's `options`, which are not part of the form model. The dates
+   * themselves go through {@link DtoUtils.toPayload}, so a bound left empty travels as
+   * absent instead of as `null`.
+   * @returns The result to emit through `done`.
+   */
+  private toPayload;
+  /**
+   * Signal form for the date value(s). `required` follows the dialog data and only
+   * applies to the fields of the active prompt type; the datepicker's own parse
+   * validators are picked up through the ControlValueAccessor interop.
+   */
+  protected readonly form: import("@angular/forms/signals").FieldTree<PromptDateForm, string | number, "writable">;
+  /** Debounced stream of keyup events on the interval inputs (shorthand typing support). */
+  private readonly intervalKeyup;
+  constructor();
+  /**
+   * Blocks the space key on the interval inputs; it is reserved as the
+   * "copy the other bound" shortcut handled by onIntervalKeyup.
+   * @param event - The keydown event from the start or end date input.
+   */
+  protected onIntervalKeydown(event: KeyboardEvent): void;
+  /**
+   * Forwards keyup events of the interval inputs to the debounced shorthand parser.
+   * @param event - The keyup event from the start or end date input.
+   * @param end   - `true` when the event comes from the end-date input.
+   */
+  protected onIntervalKeyup(event: KeyboardEvent, end: boolean): void;
+  /**
+   * Clears both bounds of the date interval.
+   */
+  protected clearInterval(): void;
+  /**
+   * Validates the form and emits the result, or shows an error if validation fails.
+   */
+  protected ok(): void;
+  static ɵfac: i0.ɵɵFactoryDeclaration<PromptDateDialogComponent, never>;
+  static ɵcmp: i0.ɵɵComponentDeclaration<PromptDateDialogComponent, "ng-component", never, {}, {
+    "done": "done";
+  }, never, never, true, never>;
 }
-
 /**
  * Form model of the time prompt.
  *
@@ -157,42 +157,42 @@ declare class PromptDateDialogComponent {
  * is none, while the form always owns the field and holds `''` when empty.
  */
 interface PromptTimeForm {
-    /** The `"HH:MM"` time value; `''` when the input is empty. */
-    value: string;
+  /** The `"HH:MM"` time value; `''` when the input is empty. */
+  value: string;
 }
-declare class PromptTimeDialogComponent {
-    /** Error text of a field: the message declared in the schema, or the shared fallback. */
-    protected readonly getErrorMessage: typeof SignalsUtils.getFieldErrorMessage;
-    readonly done: _angular_core.OutputEmitterRef<PromptDialogResult>;
-    private readonly dialogService;
-    protected readonly dialogData: _angular_core.WritableSignal<PromptTimeDialogData>;
-    /** Model backing the signal form. The value is a `"HH:MM"` time string. */
-    private readonly model;
-    /**
-     * Builds the form model from the value carried by the dialog data.
-     * @returns A fresh form model, empty when the dialog was opened without a value.
-     */
-    private toForm;
-    /**
-     * Builds the dialog result from the current form model.
-     *
-     * Ad-hoc because the result also carries the caller's `options`, which are not part
-     * of the form model; the time itself goes through {@link DtoUtils.toPayload}, so an
-     * empty input travels as absent instead of as an empty string.
-     * @returns The result to emit through `done`.
-     */
-    private toPayload;
-    /**
-     * Signal form for the time value: `required` follows the dialog data and the
-     * time validator enforces format and the optional allowed slots.
-     */
-    protected readonly form: _angular_forms_signals.FieldTree<PromptTimeForm, string | number, "writable">;
-    /**
-     * Validates the form and emits the result, or shows an error if validation fails.
-     */
-    protected ok(): void;
-    static ɵfac: _angular_core.ɵɵFactoryDeclaration<PromptTimeDialogComponent, never>;
-    static ɵcmp: _angular_core.ɵɵComponentDeclaration<PromptTimeDialogComponent, "ng-component", never, {}, { "done": "done"; }, never, never, true, never>;
-}
-
-export { PromptDateDialogComponent, PromptDialogComponent, PromptTimeDialogComponent };
+export declare class PromptTimeDialogComponent {
+  /** Error text of a field: the message declared in the schema, or the shared fallback. */
+  protected readonly getErrorMessage: typeof SignalsUtils.getFieldErrorMessage;
+  readonly done: import("@angular/core").OutputEmitterRef<PromptDialogResult>;
+  private readonly dialogService;
+  protected readonly dialogData: import("@angular/core").WritableSignal<PromptTimeDialogData>;
+  /** Model backing the signal form. The value is a `"HH:MM"` time string. */
+  private readonly model;
+  /**
+   * Builds the form model from the value carried by the dialog data.
+   * @returns A fresh form model, empty when the dialog was opened without a value.
+   */
+  private toForm;
+  /**
+   * Builds the dialog result from the current form model.
+   *
+   * Ad-hoc because the result also carries the caller's `options`, which are not part
+   * of the form model; the time itself goes through {@link DtoUtils.toPayload}, so an
+   * empty input travels as absent instead of as an empty string.
+   * @returns The result to emit through `done`.
+   */
+  private toPayload;
+  /**
+   * Signal form for the time value: `required` follows the dialog data and the
+   * time validator enforces format and the optional allowed slots.
+   */
+  protected readonly form: import("@angular/forms/signals").FieldTree<PromptTimeForm, string | number, "writable">;
+  /**
+   * Validates the form and emits the result, or shows an error if validation fails.
+   */
+  protected ok(): void;
+  static ɵfac: i0.ɵɵFactoryDeclaration<PromptTimeDialogComponent, never>;
+  static ɵcmp: i0.ɵɵComponentDeclaration<PromptTimeDialogComponent, "ng-component", never, {}, {
+    "done": "done";
+  }, never, never, true, never>;
+}