@keboola/design 11.9.0 → 13.0.0

package/dist/{FieldItem-vhIJW4pj.d.ts → FieldItem-CPN1xjN5.d.ts}

@@ -39,10 +39,7 @@ declare const CHANGE_CLASS: {
 type ChangeClassification = (typeof CHANGE_CLASS)[keyof typeof CHANGE_CLASS];
 //#endregion
 //#region src/blocks/Form/connectors/FieldItem.d.ts
-/**
- * The a11y wiring `FieldItem` derives from the field and hands back to the control — spread it onto
- * whatever element the field renders. Callers never author these attributes themselves.
- */
+/** The a11y wiring `FieldItem` derives for the control — spread it onto the rendered element. */
 type FieldControlProps = {
   id: string;
   name: string;
@@ -57,28 +54,19 @@ type RequiredMark = 'required' | 'optional' | 'hidden';
 /**
  * How the control takes its accessible name from the label.
  *
- * - `'for'` (default) — `<label for>` points at the control's `id`. Correct for the *labelable*
- *   elements: `input`, `textarea`, `select`, `button`, and anything rendering one.
- * - `'aria-labelledby'` — the label gets an id and it comes back in `control['aria-labelledby']`,
- *   with no `for` emitted. For controls that are **not** labelable elements: a CodeMirror or Lexical
- *   editable region, or a composite widget whose focusable node is a `div[role]`. `<label for>`
- *   pointing at one of those is invalid HTML and silently names nothing.
+ * - `'for'` (default) — `<label for>` at the control's `id`; for labelable elements (`input` etc.).
+ * - `'aria-labelledby'` — the label id comes back in `control['aria-labelledby']`, no `for`. For
+ *   non-labelable controls (CodeMirror, Lexical, `div[role]`), which `<label for>` never names.
  */
 type Labelling = 'for' | 'aria-labelledby';
 type Props = {
   label?: ReactNode;
-  /**
-   * Optional node rendered at the trailing edge of the label row (opposite the label) — e.g. a
-   * "Forgot password?" link beside a Password label. Presentational placement only; it is a sibling
-   * of the `<Label>`, not part of the field's accessible name. Provide an interactive element
-   * (`ButtonInline` / `Link`).
-   */
+  /** Trailing node on the label row (e.g. a `Link`); not part of the accessible name. */
   action?: ReactNode;
   required?: boolean;
   /**
-   * Which marker to show beside the label — gated by `required` so it never lies: `'required'`
-   * renders `*` only when the field is `required`; `'optional'` renders `(optional)` only when it
-   * is not; `'hidden'` renders neither. Defaults to `'required'`.
+   * Gated by `required`: `'required'` shows `*` only if required, `'optional'` shows `(optional)`
+   * only if not, `'hidden'` neither. Defaults to `'required'`.
    */
   requiredMark?: RequiredMark;
   /** See {@link Labelling}. Defaults to `'for'`. */
@@ -90,14 +78,12 @@ type Props = {
   children: (control: FieldControlProps) => ReactNode;
 };
 /**
- * The frame props a connector re-exposes to its own callers.
+ * The frame props a connector re-exposes to its callers.
  *
- * - `labelling` is not among them: which mechanism names the control follows from what the control
- *   *is*, so the connector picks it, not the call site.
- * - Leaving it in would type-check and do nothing — no connector forwards it — and land in the rest
- *   spread instead, which for `TextField` / `TextareaField` reaches the DOM `<input>`.
+ * - No `labelling`: the connector picks it from what its control is.
+ * - Left in, it would fall into the rest spread and reach the DOM `<input>`.
  */
 type FieldItemProps = Omit<Props, 'children' | 'labelling'>;
 //#endregion
 export { ChangeClassification, DiffChunk, FieldItemProps, MergeConflict };
-//# sourceMappingURL=FieldItem-vhIJW4pj.d.ts.map
+//# sourceMappingURL=FieldItem-CPN1xjN5.d.ts.map

package/dist/{FileUpload-DYQCTGjU.js → FileUpload-Ch2hrIWq.js}

@@ -1,7 +1,7 @@
 import { __commonJSMin, __toESM } from "./rolldown-runtime-Bdc48AWt.js";
 import { cn } from "./classNames-BzrkDnOD.js";
-import { File, FileSpreadsheet, FileText, Upload, X } from "./icons-Cek151jC.js";
-import { Button } from "./Button-DsRrU5F1.js";
+import { File, FileSpreadsheet, FileText, Upload, X } from "./icons-wcA70iQx.js";
+import { Button } from "./Button-B21oVcPU.js";
 import React, { Fragment, createContext, forwardRef, use, useCallback, useEffect, useImperativeHandle, useMemo, useReducer, useRef } from "react";
 import { cva } from "class-variance-authority";
 import { Fragment as Fragment$1, jsx, jsxs } from "react/jsx-runtime";
@@ -1281,7 +1281,7 @@ var require_es = /* @__PURE__ */ __commonJSMin(((exports) => {
 	};
 }));
 //#endregion
-//#region ../../node_modules/.pnpm/react-dropzone@14.2.3_react@19.2.7/node_modules/react-dropzone/dist/es/utils/index.js
+//#region ../../node_modules/.pnpm/react-dropzone@14.2.3_react@19.3.0/node_modules/react-dropzone/dist/es/utils/index.js
 var import_prop_types = /* @__PURE__ */ __toESM(require_prop_types());
 var import_es = /* @__PURE__ */ __toESM(require_es());
 function _toConsumableArray$1(arr) {
@@ -1583,7 +1583,7 @@ function isExt(v) {
 * @typedef {"file-invalid-type"|"file-too-large"|"file-too-small"|"too-many-files"} ErrorCode
 */
 //#endregion
-//#region ../../node_modules/.pnpm/react-dropzone@14.2.3_react@19.2.7/node_modules/react-dropzone/dist/es/index.js
+//#region ../../node_modules/.pnpm/react-dropzone@14.2.3_react@19.3.0/node_modules/react-dropzone/dist/es/index.js
 var _excluded = ["children"];
 var _excluded2 = ["open"];
 var _excluded3 = [
@@ -2481,18 +2481,13 @@ const useFileDropTarget = ({ accept, maxSize, maxFiles, multiple = true, disable
 //#endregion
 //#region src/components/FileUpload/FileUpload.tsx
 /**
-* Drop-zone primitive — caller owns the file array; the component signals drops.
+* Drop-zone primitive — the caller owns the `File[]`; the component only signals drops.
 *
-* Brand-neutral: the chrome is semantic tokens, so it follows whichever brand is active (there is
-* no argo-only runtime gate) and renders under legacy chrome too.
-*
-* **When to use:** any in-page file-picker flow (Card body, Modal, page content).
-* **When NOT to use:** for upload progress or pipeline orchestration, build app-level state on top of
-* `onFilesChange`; this primitive does not own the upload lifecycle. When the drop affordance is an
-* existing subtree you style yourself, reach for `useFileDropTarget` instead.
-* **Composition:** wrap `<FileUpload.DropZone />` for the drop target and `<FileUpload.FileList />`
-* for the selected-files list. The caller stores the `File[]` and renders it back into `FileList`.
-* Rejection copy is the caller's — read it with `useFileUploadRejections()`.
+* - Brand-neutral (semantic tokens), so it renders under legacy chrome too.
+* - Compose `<FileUpload.DropZone />` + `<FileUpload.FileList />`; pass the `File[]` to `FileList`.
+* - Upload progress/lifecycle is app-level state on top of `onFilesChange`.
+* - For a drop target you style yourself, use `useFileDropTarget`.
+* - Rejection copy is the caller's — read it with `useFileUploadRejections()`.
 */
 const FileUploadInner = ({ accept, maxSize, maxFiles, multiple, disabled = false, onFilesChange, onFilesRejected, forcedState, children, className, ...rest }) => {
 	const dropTarget = useFileDropTarget({
@@ -2524,4 +2519,4 @@ const FileUpload = Object.assign(FileUploadInner, {
 //#endregion
 export { FileUpload, useFileDropTarget, useFileUploadRejections };
 
-//# sourceMappingURL=FileUpload-DYQCTGjU.js.map
+//# sourceMappingURL=FileUpload-Ch2hrIWq.js.map