@pipelex/mthds-form 0.21.0 → 0.23.0

package/dist/field-renderer-B3g16qZT.d.ts

@@ -1,74 +0,0 @@
-import * as react from 'react';
-import { RunField } from './core/descriptor.js';
-import { FileSource } from './core/sources.js';
-
-/**
- * Ambient state that any field in the tree may need, threaded unchanged through
- * the recursion so containers don't have to re-plumb it for every child.
- */
-interface FieldEnv {
-    disabled?: boolean;
-    /**
-     * A file field asks its parent to upload; the parent sets the value later.
-     *
-     * Its presence is the capability. A host that supplies it gets a dropzone on
-     * every file field; a host that does not gets no dropzone and no file picker,
-     * because a file taken with nowhere to go used to be dropped without a word.
-     * See docs/upload-seam.md, "Which ways into a file value a host offers".
-     */
-    onDropFile?: (id: string, file: File) => void;
-    /**
-     * Whether a file field offers a link input, the way in that needs no upload.
-     * `true` when absent; `false` hides the "paste a URL instead" toggle and the
-     * input behind it on every file field.
-     *
-     * It governs that input and nothing else. A file value is a URL whichever way
-     * it arrived, so this says nothing about which values are valid: a web link
-     * the host writes is still shown on the field's card and can still be
-     * cleared. Setting it to `false` with no `onDropFile` leaves a file field no
-     * way in at all, and the field throws, naming its path, when it renders.
-     */
-    allowUrl?: boolean;
-    /** Ids currently mid-upload. */
-    uploadingIds?: ReadonlySet<string>;
-    /**
-     * Why an upload failed, keyed by the same id `onDropFile` was handed, so the
-     * message shows on the field that took the file rather than under the whole
-     * form, where only its wording could say which input failed.
-     *
-     * The map is the host's truth about each upload attempt: a host removes an
-     * entry when the next file is dropped at that id, and sets it again if that
-     * upload fails too. A clear or a typed link on the field hides the message
-     * until the host sends a different one or removes it, and a list holds back
-     * the entries a row removal left at a renumbered position.
-     */
-    uploadErrors?: ReadonlyMap<string, string>;
-    /** Resolve a `pipelex-storage://` URI to a browser-viewable URL (for previews
-     *  of already-stored files). */
-    resolveUrl?: (uri: string) => Promise<string | null>;
-    /**
-     * Where a file field can take a file the host already stores. Its presence
-     * is the capability, as `onDropFile`'s is: every empty file field then
-     * offers "Choose from your team's files", and a list of files offers it for
-     * several at once. The choice is written as `{ url, filename }`, exactly as
-     * an upload's result is. See docs/sources.md.
-     */
-    fileSource?: FileSource;
-}
-interface FieldRendererProps {
-    field: RunField;
-    value: unknown;
-    onChange: (value: unknown) => void;
-    /** Unique, stable id used for label linkage and upload tracking. */
-    id: string;
-    error?: string;
-    env?: FieldEnv;
-}
-/**
- * The single dispatch point: a normalized `RunField` → the matching control.
- * Object and list fields recurse back through here, so the whole form is one
- * data-driven tree with no per-type branching anywhere else.
- */
-declare function FieldRenderer({ field, value, onChange, id, error, env }: FieldRendererProps): react.JSX.Element;
-
-export { type FieldEnv as F, FieldRenderer as a, type FieldRendererProps as b };