@truenas/ui-components 0.8.12 → 0.8.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@truenas/ui-components",
-  "version": "0.8.12",
+  "version": "0.8.14",
   "publishConfig": {
     "registry": "https://registry.npmjs.org",
     "access": "public"

package/types/truenas-ui-components.d.ts

@@ -11591,6 +11591,11 @@ export declare class TnTableComponent<T = unknown> implements OnInit {
    * <!-- <tr data-testid="row-jane-doe"> -->
    * ```
    *
+   * The controls the table draws for the row are derived from the same base, in both layouts:
+   * `checkbox-select-<base>` on its selection checkbox and `button-expand-<base>` on its expand
+   * chevron or Details toggle. The select-all is `checkbox-all-rows` with or without this input —
+   * deliberately outside `checkbox-select-*`, so no row base (not even `all`) can produce it.
+   *
    * Cells are not covered by this: a suite that has to read one cell of a row still needs an id
    * on the element that cell renders. Tagging the row is what makes the row itself reachable —
    * which is the part a consumer cannot add from the outside.
@@ -11881,6 +11886,18 @@ export declare class TnTableComponent<T = unknown> implements OnInit {
    * identical between passes, and correct after a reload hands back new row objects.
    */
   protected readonly rowTestIds: Signal<TnTestIdValue[]>;
+  /**
+   * Base for each row's selection checkbox, `['select', ...row base]` — so a row tagged
+   * `row-job-42` gets `checkbox-select-job-42`. Role leads, as in `tn-dialog-shell`'s chrome.
+   *
+   * The same array serves table and card mode, so a narrow viewport does not rename a row's
+   * controls any more than it renames the row. Without a usable row base the entry is
+   * `undefined` rather than `['select']`, which would give every row the same `checkbox-select`.
+   */
+  protected readonly rowSelectTestIds: Signal<TnTestIdValue[]>;
+  /** Base for each row's expand control — the table-mode chevron and the card's Details toggle. */
+  protected readonly rowExpandTestIds: Signal<TnTestIdValue[]>;
+  private rowControlTestIds;
   effectiveDisplayedColumns: Signal<string[]>;
   /**
    * Every column the table actually renders, including the trailing actions column, which
@@ -18240,6 +18257,22 @@ export interface FilePickerCreateActionEvent {
   /** Directory being browsed when the action was triggered. */
   parentPath: string;
 }
+/**
+ * Payload of `itemSelectionChange`: the committed value together with the
+ * listed items it refers to, for consumers that need more than the path
+ * (e.g. to require that a FILE was picked).
+ */
+export interface FilePickerSelection {
+  /** The committed value — the same payload `selectionChange` carries. */
+  value: string | string[];
+  /**
+   * One entry per selected path, in value order. `null` when the picker has
+   * not listed that path in this session — e.g. a typed path the user never
+   * browsed to, or the browsed directory itself submitted on an empty
+   * selection before its parent was listed. Empty for a cleared selection.
+   */
+  items: (FileSystemItem | null)[];
+}
 export interface FilePickerError {
   type: 'navigation' | 'permission' | 'creation' | 'validation';
   message: string;
@@ -18264,6 +18297,24 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
   /** Consumer-defined creation flows shown as buttons in the popup footer. */
   createActions: import("@angular/core").InputSignal<FilePickerCreateAction[]>;
   allowManualInput: import("@angular/core").InputSignal<boolean>;
+  /**
+   * Commit typed input verbatim instead of treating it as a path to validate:
+   * no `rootPath` confinement, no `callbacks.validatePath`, no `valueRoot`
+   * mapping — the text the user typed is the value. Lets a field accept
+   * entries the browser cannot list, e.g. `EXTERNAL:192.168.0.200\SHARE` or
+   * a dataset name for a pool that is not imported. With `multiSelect`, the
+   * text is split on commas into one entry per comma-separated part (trimmed,
+   * empty parts dropped), so commas cannot appear inside an entry. Committing
+   * closes the popup. Popup selections are unaffected. Requires
+   * `allowManualInput`.
+   */
+  allowFreeText: import("@angular/core").InputSignal<boolean>;
+  /**
+   * Explicit accessible name for the path input. Inside a `tn-form-field` the
+   * input is named by the field label automatically (via `aria-labelledby`),
+   * so leave this unset there unless the field has no visible label.
+   */
+  ariaLabel: import("@angular/core").InputSignal<string | undefined>;
   /**
    * Open the picker popup when the input is clicked while no path is selected
    * yet — an empty field means the user is about to pick something, so the
@@ -18302,6 +18353,11 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
   fileExtensions: import("@angular/core").InputSignal<string[] | undefined>;
   callbacks: import("@angular/core").InputSignal<FilePickerCallbacks | undefined>;
   selectionChange: import("@angular/core").OutputEmitterRef<string | string[]>;
+  /**
+   * Emitted alongside every `selectionChange` with the listed
+   * `FileSystemItem` behind each selected path (or `null` when unknown).
+   */
+  itemSelectionChange: import("@angular/core").OutputEmitterRef<FilePickerSelection>;
   pathChange: import("@angular/core").OutputEmitterRef<string>;
   /** Re-emitted from the popup when one of the `createActions` buttons is pressed. */
   createAction: import("@angular/core").OutputEmitterRef<FilePickerCreateActionEvent>;
@@ -18319,6 +18375,20 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
   loading: import("@angular/core").WritableSignal<boolean>;
   hasError: import("@angular/core").WritableSignal<boolean>;
   private formDisabled;
+  /**
+   * Field-derived ARIA for the path input when projected into a
+   * `tn-form-field` (label, description, invalid, required). All-null when
+   * standalone or when `ariaLabel` overrides.
+   */
+  protected readonly fieldAria: import("@truenas/ui-components").TnFormFieldAriaBindings;
+  /**
+   * Every item the picker has listed, by absolute path, so a selection can be
+   * resolved back to its item even after browsing elsewhere (multi-select
+   * across directories, `selectPath`, typed paths). Kept for the picker's
+   * lifetime: a stale entry only means a stale `type` for a path that changed
+   * on disk after it was listed.
+   */
+  private listedItems;
   isDisabled: import("@angular/core").Signal<boolean>;
   /** Explicit `testId` wins; otherwise the bound control's name (formControlName etc.). */
   protected resolvedTestId: import("@angular/core").Signal<TnTestIdValue>;
@@ -18348,6 +18418,14 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
    * and spam `validatePath` with paths the user never meant.
    */
   onPathCommit(event: Event): void;
+  /**
+   * `allowFreeText` commit: the typed text is the value, verbatim (single
+   * mode keeps even surrounding whitespace, as the field shows it), and a
+   * field holding only whitespace clears the selection like an empty one.
+   * Selection state still tracks the absolute form of each trimmed entry (the
+   * same mapping `writeValue` applies) so reopening the popup reflects it.
+   */
+  private commitFreeText;
   /** `openOnClick` entry point. */
   onInputClick(): void;
   /**
@@ -18429,6 +18507,14 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
    * would be the surprising behavior.
    */
   private updateSelection;
+  /**
+   * Emits `selectionChange` and `itemSelectionChange` for a committed value.
+   * Items are looked up by the absolute form of each trimmed entry, which is
+   * how listings are indexed — a free-text value keeps any surrounding
+   * whitespace the user typed, but still resolves to the item it names.
+   */
+  private emitSelection;
+  private indexListedItems;
   private normalizedValueRoot;
   /** Maps an internal absolute path into the `valueRoot`-relative value space. */
   private toValueSpace;
@@ -18458,6 +18544,16 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
       "required": false;
       "isSignal": true;
     };
+    "allowFreeText": {
+      "alias": "allowFreeText";
+      "required": false;
+      "isSignal": true;
+    };
+    "ariaLabel": {
+      "alias": "ariaLabel";
+      "required": false;
+      "isSignal": true;
+    };
     "openOnClick": {
       "alias": "openOnClick";
       "required": false;
@@ -18505,6 +18601,7 @@ export declare class TnFilePickerComponent implements ControlValueAccessor, OnIn
     };
   }, {
     "selectionChange": "selectionChange";
+    "itemSelectionChange": "itemSelectionChange";
     "pathChange": "pathChange";
     "createAction": "createAction";
     "error": "error";
@@ -18588,31 +18685,35 @@ export declare class TnFilePickerHarness extends ComponentHarness {
    */
   getValue(): Promise<string>;
   /**
-   * Sets the picker's value by typing a single path into the path input and
-   * committing it via the input's `change` event, exactly as a user pressing
-   * Enter would.
+   * Sets the picker's value by typing into the path input and committing it
+   * via the input's `change` event, exactly as a user pressing Enter would.
    *
-   * Unlike `IxExplorerHarness.setValue` there is no `string[]` overload:
-   * tn-file-picker treats typed input as ONE path even in multi-select mode
-   * (commas are legal in paths, so they are never list separators). In
-   * multi-select, committing a typed path REPLACES the whole selection with
-   * that single path; build a real multi-selection through the popup with
-   * {@link clickItem} + {@link clickSelect}.
+   * By default tn-file-picker treats typed input as ONE path even in
+   * multi-select mode (commas are legal in paths, so they are never list
+   * separators): committing a typed path REPLACES the whole selection with
+   * that single path, and commits go through the component's normal
+   * validation — paths outside `rootPath` are rejected (the value stays
+   * unchanged and an `error` is emitted), and `callbacks.validatePath` is
+   * consulted when provided. Build a real multi-selection through the popup
+   * with {@link clickItem} + {@link clickSelect}.
+   *
+   * With `allowFreeText`, the typed text is committed verbatim with no
+   * validation, and in multi-select it is split on commas — so passing a
+   * `string[]` (typed joined with `', '`) sets one entry per element.
    *
-   * Commits go through the component's normal validation: paths outside
-   * `rootPath` are rejected (the value stays unchanged and an `error` is
-   * emitted), and `callbacks.validatePath` is consulted when provided.
    * Setting an empty string clears the selection. Has no effect when
    * `allowManualInput` is false (the input is readonly).
    *
-   * @param value The path to set.
+   * @param value The path to set, or several entries for a free-text
+   *   multi-select picker.
    *
    * @example
    * ```typescript
    * await picker.setValue('/mnt/tank/media');
+   * await freeTextMultiPicker.setValue(['/mnt/tank/a', 'EXTERNAL:host\\share']);
    * ```
    */
-  setValue(value: string): Promise<void>;
+  setValue(value: string | string[]): Promise<void>;
   /**
    * Gets the path input's placeholder text.
    *