import type { ReactNode } from "react";
import type { SlotProps } from "../slotProps.ts";
export type MarkdownImageUpload = {
    /** Alt text. Defaults to the file's name when omitted. */
    alt?: string;
    /** Where the image now lives. Inserted verbatim. */
    url: string;
};
/**
 * The toolbar's glyphs, by action.
 *
 * **No default, and none shipped** — this package ships no icons,
 * and a `⋯`/`▨` default renders as nothing where the font lacks it
 * ([decision](../../../../docs/decisions/2026-07-29-ship-no-icons-and-no-symbol-glyphs.md)).
 * With no icons the toolbar is nine word buttons, which works
 * everywhere and collapses into the overflow menu early; an app
 * that brings lucide gets a compact bar and keeps the words as the
 * accessible names.
 *
 * `overflow` is the odd one out: it is not a markdown command, it
 * is the **bar's own** trigger. It lives here because an app that
 * passes the nine and not the tenth gets nine icons followed by
 * the words *"More actions"* — which is the one width where an
 * icon bar looks unfinished, and there was no prop to fix it with.
 */
export type MarkdownEditorIcons = Partial<Record<"bold" | "bulletedList" | "code" | "heading" | "image" | "italic" | "link" | "numberedList" | "overflow" | "quote" | "taskList", ReactNode>>;
export type MarkdownEditorProps = SlotProps & {
    className?: string;
    /**
     * **Initial** only. This control is uncontrolled, and the long
     * reason is in the doc comment below — it is the whole design.
     */
    defaultValue?: string;
    /** See `MarkdownEditorIcons`. */
    icons?: MarkdownEditorIcons;
    isDisabled?: boolean;
    isReadOnly?: boolean;
    /**
     * The accessible name, as `aria-label`. Omit it inside a `Field`,
     * which supplies a real `<label htmlFor>` — same contract as
     * `Select`.
     */
    label?: string;
    onChange?: (value: string) => void;
    /**
     * A failed upload, after the placeholder has been taken back out
     * of the text. Pair it with a `Toast`; this component does not
     * own one.
     */
    onUploadError?: (file: File, error: unknown) => void;
    /**
     * Paste or drop an image and this runs. **The component does not
     * own storage** — it hands you a `File`, you put it somewhere,
     * and the URL you return is inserted at the caret as
     * `![alt](url)`. Docket keeps its own blob storage precisely so
     * the URL stays stable and theirs.
     *
     * Omit it and image paste is simply not offered: a `<textarea>`
     * ignores a pasted image on its own, which is the correct
     * fallback rather than a broken one.
     */
    onUploadImage?: (file: File) => Promise<MarkdownImageUpload>;
    placeholder?: string;
    /** The editing surface's accessible name in the toolbar's label. */
    toolbarLabel?: string;
};
/**
 * A live hybrid markdown editor whose stored value is markdown and
 * only ever markdown.
 *
 * Docket asked for this one and the requirement is unusually sharp,
 * because the tracker it replaces destroyed data by storing HTML in
 * a field it later tried to read back as text. So the constraint
 * here is not "prefer markdown" — it is that **an HTML tag must not
 * be able to reach the stored string**, and the design is chosen to
 * make that mechanical rather than policed:
 *
 *  - the editing surface is a `<textarea>`, which takes
 *    `text/plain` off the clipboard and nothing else. Copy a
 *    styled paragraph out of a browser and the `text/html` flavour
 *    is simply not read;
 *  - every command in `markdownCommands.ts` returns markdown, and
 *    there is no serialiser anywhere in the component;
 *  - the painted layer emits `{ kind, text }` spans that React
 *    renders as **text nodes**. No `innerHTML`, no sanitiser, and
 *    nothing to get wrong — a `<script>` in the source is four
 *    coloured characters on screen.
 *
 * `MarkdownEditor.test.tsx` round-trips a value full of the
 * characters that tempt escaping and asserts no tag ever appears.
 *
 * ## Why a `<textarea>` and not an editor core
 *
 * Charcuterie is published, so a dependency here is a permanent
 * cost to every consumer of the package — measured, for a markdown
 * setup: CodeMirror 6 at 176 KB gzipped, Lexical at 148 KB, TipTap
 * at 238 KB. This component adds **nothing**. The full argument,
 * with the numbers and with what the choice gives up, is
 * `docs/decisions/2026-08-19-the-markdown-editor-is-a-textarea-with-a-painted-layer.md`.
 *
 * The accessibility half of that argument is worth repeating here,
 * because it is the half that is hard to buy back later. A
 * `<textarea>` arrives with caret movement, word-wise selection,
 * `Home`/`End`, IME composition, spellcheck, autocorrect, the
 * platform's own undo stack, `role="textbox"` and
 * `aria-multiline="true"` — all of it, in every browser, tested by
 * the vendors. A `contenteditable` starts with none of those and
 * re-earns each one, and the ones it never fully re-earns are IME
 * and undo. This library's central claim is that an agent and a
 * keyboard can drive every component; starting from the platform's
 * own text control is the cheapest way to keep it.
 *
 * ## It is uncontrolled, and that is not a shortcut
 *
 * `defaultValue` in, `onChange` out — the same contract as `Select`
 * ([decision](../../../../docs/decisions/2026-07-31-select-is-uncontrolled-because-the-platform-owns-the-value.md)),
 * and here it protects something specific. A controlled React
 * `<textarea>` round-trips every keystroke through render, and any
 * programmatic `value` assignment **wipes the browser's undo
 * stack**: Ctrl+Z after a toolbar click then skips the paragraph
 * you typed before it, or does nothing at all.
 *
 * So the textarea is never handed a `value`. Its text is mirrored
 * into state for *painting* only, and every programmatic edit — a
 * toolbar action, a shortcut, an image insertion — is applied as a
 * range replacement through `document.execCommand("insertText")`,
 * which is deprecated, is the only API that appends to the native
 * undo stack, and is exactly why `getMinimalEdit` exists.
 *
 * A consumer that must swap the whole document — Docket opening a
 * different task — remounts with a `key`. That is one line, and it
 * is honest about the fact that the old undo history belonged to
 * the old document.
 *
 * ## Composition, and the one component that did not fit
 *
 * The toolbar is this package's `Toolbar`, so the row collapses
 * into a menu **by measurement** rather than at a breakpoint —
 * which is what the Narrow View actually needs, since a lane in a
 * three-up board is narrow on a 4K display. `Field` wraps it
 * through `SlotProps`, so a label, a description and an error wire
 * themselves to the textarea.
 *
 * `FileDropZone` does **not** wrap it, and that is the interesting
 * one. That component is a `<label>` around a file input covering
 * its whole area — correct for "drop a disc image here", and wrong
 * for a text surface, where the drop has to land *at a character
 * offset* and the area has to keep taking clicks as caret
 * placement. So the editor handles its own drop, and `FileDropZone`
 * stays the right answer for the attachment list beside it.
 */
export declare const MarkdownEditor: ({ className, defaultValue, icons, isDisabled, isReadOnly, label, onChange, onUploadError, onUploadImage, placeholder, toolbarLabel, ...receivedSlotProps }: MarkdownEditorProps) => ReactNode;
//# sourceMappingURL=MarkdownEditor.d.ts.map