@eifi1/ui-kit 0.53.0 → 0.55.0

package/src/feedback/feedback-dialog.tsx

@@ -1,440 +0,0 @@
-import { useId, useState } from "react";
-import type { ReactNode } from "react";
-import { Button } from "../components/button";
-import { Input } from "../components/input";
-import { Select } from "../components/select";
-import { Textarea } from "../components/textarea";
-import type { ButtonSize, ButtonVariant } from "../components/button-look";
-import { Modal } from "../components/modal";
-import { isApplePlatform } from "../hooks/use-hotkey";
-import { usePhoneLayout } from "../hooks/use-breakpoint";
-import { useKitLabels, type LabelOverride } from "../i18n/kit-labels";
-import { hasContent } from "../lib/presence";
-import {
-  DEFAULT_ATTACHMENT_ACCEPT,
-  DEFAULT_FEEDBACK_ATTACHMENT_LABELS,
-  DEFAULT_MAX_ATTACHMENT_BYTES,
-  FeedbackAttachmentField,
-  type FeedbackAttachmentError,
-  type FeedbackAttachmentErrorInfo,
-} from "./feedback-attachment";
-import { DEFAULT_FEEDBACK_DIALOG_LABELS } from "./feedback-dialog-labels";
-
-/** One category the dialog offers. `C` (0.52): the app's category type — the kit's
- *  `FeedbackCategory`, or `string` (the default) for a vocabulary of the app's own. */
-export interface FeedbackCategoryOption<C extends string = string> {
-  value: C;
-  label: string;
-}
-
-export interface FeedbackAttachmentLabels {
-  /** The heading over the field. Optional: a note editor puts the buttons
-   *  straight under its textarea, where a second heading is noise. */
-  attachment?: string;
-  attachmentAdd: string;
-  /** Label for the "capture screenshot" button. Optional — falls back to the provider's
-   *  `feedbackAttachment.attachmentCapture`, then English. */
-  attachmentCapture?: string;
-  /** The line under the attachment buttons saying a screenshot can be pasted
-   *  straight in. Optional — falls back to the provider's `feedbackAttachment`, then English. */
-  attachmentPaste?: string;
-  attachmentRemove: string;
-  /** `multiple` mode (0.15.5): the chip list's accessible name — and, in
-   *  `<FeedbackDialog attachments="multiple">`, the heading over it (0.16.0). Optional,
-   *  as are the keys below — they fall back to the provider's `feedbackAttachment`,
-   *  then English. */
-  attachmentList?: string;
-  /** `multiple` mode (0.16.0): the screenshot slot's chip title, in place of its file name. */
-  attachmentScreenshot?: string;
-  /** `multiple` mode: one chip's remove button, given the file's name. */
-  attachmentRemoveFile?: (name: string) => string;
-  /** `multiple` mode: the line shown once `max` files are attached. */
-  attachmentLimit?: (max: number) => string;
-  /** `refs` mode (0.22.0): the second line of a chip whose upload is still running. */
-  attachmentUploading?: string;
-}
-
-export interface FeedbackDialogLabels extends FeedbackAttachmentLabels {
-  title: string;
-  category: string;
-  subject: string;
-  body: string;
-  attachment: string;
-  /** See {@link FeedbackDialogTextLabels.submitHint}. */
-  submitHint: FeedbackSubmitHint;
-  cancel: string;
-  save: string;
-}
-
-/** The submit hint: a string, or the line for the platform (`apple`: Mac, iPhone, iPad). */
-export type FeedbackSubmitHint = string | ((apple: boolean) => string);
-
-/**
- * The dialog's own strings — the `feedbackDialog` namespace of `<UiKitProvider
- * labels>` (0.12.0). The attachment keys are not repeated here: they are the
- * `feedbackAttachment` namespace's, which the field inside already reads.
- *
- * Before, every key was required at the call site, so each app restated ten strings
- * wherever it mounted the dialog (kastlan feedback-button.tsx built the object inline).
- */
-export interface FeedbackDialogTextLabels {
-  title: string;
-  category: string;
-  subject: string;
-  body: string;
-  /** The body's label when `requireBody={false}`: "What happened? (optional)".
-   *  Optional, so a complete `UiKitLabels` typed before 0.14.2 still compiles. */
-  bodyOptional?: string;
-  /** The heading over the attachment buttons. */
-  attachment: string;
-  /**
-   * The line beside the buttons naming the shortcut. Since 0.27.0 a function of the
-   * platform, like `form.submitShortcut`: `apple` is true on a Mac, iPhone or iPad, where
-   * the key is Cmd — "⌘ Enter to send" there, keksdose's "Ctrl+Enter to send" elsewhere
-   * (§7.12). A plain string is still taken and shown everywhere, as before 0.27.0.
-   */
-  submitHint: FeedbackSubmitHint;
-  cancel: string;
-  save: string;
-  /** 0.38 (docs/feedback-harmonization.md §9.2 decision 6): the line under the body when
-   *  reports are public — `useFeedbackSubmit({ publicNotice: true })` shows it. Optional,
-   *  so a complete `UiKitLabels` typed before 0.38 still compiles. de-CH "Andere Personen
-   *  sehen Titel und Text (nie Ihre Screenshots oder Dateien)." */
-  publicNotice?: string;
-}
-
-// Defined in ./feedback-dialog-labels, which holds no component code (0.34, KS U8).
-export { DEFAULT_FEEDBACK_DIALOG_LABELS };
-
-export interface FeedbackSubmission<C extends string = string> {
-  title: string;
-  body: string;
-  category: C;
-  attachment: File | null;
-}
-
-/**
- * What `onSubmit` gets under `attachments="multiple"` (0.15.5): the screenshot and
- * the picked/pasted files apart, because an app files them differently — keksdose
- * attaches the screenshot to the report and the photos as its evidence list. No
- * `attachment`: there is no one file it could name.
- */
-export interface FeedbackMultipleSubmission<C extends string = string> {
-  title: string;
-  body: string;
-  category: C;
-  /** What `onCaptureScreenshot` returned, or `null` — at most one. */
-  screenshot: File | null;
-  /** Picked and pasted files, in the order they were added; at most `maxAttachments`. */
-  attachments: File[];
-}
-
-/**
- * `C` (0.52, refactor audit 2026-10-30, API-7): the category type, inferred from
- * `categories` and `category` — `FeedbackCategory` hands `onCategoryChange` and
- * `onSubmit` a `FeedbackCategory` back, where a plain `string` had to be cast (the kit's
- * own `useFeedbackSubmit` did). `string` by default, so an app's own vocabulary fits.
- */
-interface FeedbackDialogBaseProps<C extends string = string> {
-  open: boolean;
-  onClose: () => void;
-  /** `readonly` since 0.52: the dialog never changes it. */
-  categories: readonly FeedbackCategoryOption<C>[];
-  category: C;
-  onCategoryChange: (value: C) => void;
-  /** Prop > `<UiKitProvider labels={{ feedbackDialog, feedbackAttachment }}>` >
-   *  English. Optional since 0.12.0; a whole `FeedbackDialogLabels` still fits. */
-  labels?: LabelOverride<FeedbackDialogLabels>;
-  submitting?: boolean;
-  contextSlot?: ReactNode;
-  attachmentAccept?: string[];
-  maxAttachmentBytes?: number;
-  /**
-   * Optional: capture a screenshot of the underlying app view and return it as a
-   * File. When provided, a "Capture screenshot" button is shown next to "Add
-   * attachment"; the returned file is fed through the same validation + preview.
-   */
-  onCaptureScreenshot?: () => Promise<File | null>;
-  /**
-   * `false`: a report with only a subject can be sent, and the body's label says it is
-   * optional (`bodyOptional`, unless `labels.body` is passed). Default `true`, the
-   * dialog's behaviour until 0.14.2 (keksdose K1: its backend takes title-only reports).
-   */
-  requireBody?: boolean;
-  /**
-   * The attachment field's add and capture buttons: its `buttonVariant` (0.25.0),
-   * Button's own `variant`. Default `"secondary"`, the look they always had.
-   *
-   * The field took `buttonVariant` / `buttonSize` in 0.24.0 (keksdose's support chat),
-   * but the dialog builds its field itself and passed neither, so a host that wanted
-   * quieter buttons here — a dialog that already ends in a row of Cancel / Send — had
-   * no way to say so short of rebuilding the dialog. Named after the dialog's other
-   * attachment options (`attachmentAccept`, `onAttachmentError`) and handed through
-   * unchanged, in both `attachments` modes.
-   */
-  attachmentButtonVariant?: ButtonVariant;
-  /** The attachment field's `buttonSize` (0.25.0) — with {@link attachmentButtonVariant}.
-   *  Default `"md"`; `"sm"` draws the paperclip and camera at 14px. */
-  attachmentButtonSize?: ButtonSize;
-  /**
-   * A muted line under the body saying who will read it (0.38, docs/feedback-harmonization.md
-   * §9.2 decision 6) — the kit's sentence is `feedbackDialog.publicNotice`, "Other users
-   * will see the title and text (never your screenshots or files)", which
-   * `useFeedbackSubmit({ publicNotice: true })` passes. Attached to the body field with
-   * `aria-describedby`, so it is heard where the text is written. Left out: no line.
-   */
-  publicNotice?: ReactNode;
-}
-
-/** One attachment — a screenshot, a picked or a pasted image; a second replaces
- *  nothing, it has to wait for the first to be removed. The default. */
-export interface FeedbackDialogSingleProps<C extends string = string> extends FeedbackDialogBaseProps<C> {
-  attachments?: "single";
-  onSubmit: (data: FeedbackSubmission<C>) => void | Promise<void>;
-  /** `info` (0.23.0) names the refused file and the limit — see
-   *  {@link FeedbackAttachmentErrorInfo}. */
-  onAttachmentError?: (kind: "type" | "size", info: FeedbackAttachmentErrorInfo) => void;
-  /** Multiple mode only — refused here rather than silently ignored. */
-  maxAttachments?: never;
-}
-
-/**
- * One screenshot plus up to `maxAttachments` picked or pasted files (0.15.5, keksdose
- * dev#578: "pasted two photos, the second overwrote the first"). The capture button is
- * offered while there is no screenshot yet; the add button while there is room.
- */
-export interface FeedbackDialogMultipleProps<C extends string = string> extends FeedbackDialogBaseProps<C> {
-  attachments: "multiple";
-  /** Default `DEFAULT_MAX_ATTACHMENTS` (5). The screenshot does not count. */
-  maxAttachments?: number;
-  onSubmit: (data: FeedbackMultipleSubmission<C>) => void | Promise<void>;
-  /** `"count"`: more files arrived at once than there was room for; the surplus was
-   *  dropped. `info` (0.23.0) names the refused file(s) and the limit. */
-  onAttachmentError?: (kind: FeedbackAttachmentError, info: FeedbackAttachmentErrorInfo) => void;
-}
-
-export type FeedbackDialogProps<C extends string = string> =
-  FeedbackDialogSingleProps<C> | FeedbackDialogMultipleProps<C>;
-
-/**
- * The generic feedback form dialog: category + subject + body + an optional image
- * attachment, with Ctrl/Cmd+Enter to submit. Domain-free — the app supplies the
- * category options, labels and an `onSubmit` that talks to its own backend, plus
- * an optional `contextSlot` for app-specific context (user, current URL, …).
- *
- * **A screenshot can be pasted straight in.** Ctrl/Cmd+V anywhere in the dialog
- * takes an image off the clipboard and makes it the attachment, through the same
- * validation and the same preview as the file picker. It is the gesture the two
- * ways in did not cover: `onCaptureScreenshot` snapshots the *whole* app view,
- * and the file picker needs a file — so somebody who wanted to show one panel,
- * or one region of one, had to save a crop to disk first and then find it again
- * (Steering Design feedback #39). The clipboard is where a region snip already
- * is on every platform.
- *
- * **`attachments="multiple"`** (0.15.5) takes several: every paste and pick adds a
- * chip, and `onSubmit` gets `{ screenshot, attachments }` ({@link
- * FeedbackMultipleSubmission}) instead of `attachment`. Opt-in, so a caller typed
- * against the one-file submission keeps compiling and behaving as before.
- */
-export function FeedbackDialog<C extends string = string>(props: FeedbackDialogProps<C>) {
-  const {
-    open,
-    onClose,
-    categories,
-    category,
-    onCategoryChange,
-    labels: labelsProp,
-    submitting = false,
-    contextSlot,
-    attachmentAccept = DEFAULT_ATTACHMENT_ACCEPT,
-    maxAttachmentBytes = DEFAULT_MAX_ATTACHMENT_BYTES,
-    onCaptureScreenshot,
-    requireBody = true,
-    attachmentButtonVariant,
-    attachmentButtonSize,
-    publicNotice,
-  } = props;
-  const [title, setTitle] = useState("");
-  const [body, setBody] = useState("");
-  const [attachment, setAttachment] = useState<File | null>(null);
-  // `attachments="multiple"` only: the capture, apart from the picked/pasted files.
-  const [screenshot, setScreenshot] = useState<File | null>(null);
-  const [files, setFiles] = useState<File[]>([]);
-  const isMobile = usePhoneLayout();
-  const noticeId = useId();
-  const hasNotice = hasContent(publicNotice);
-  const labels = useKitLabels("feedbackDialog", DEFAULT_FEEDBACK_DIALOG_LABELS, labelsProp);
-  const attachmentText = useKitLabels("feedbackAttachment", DEFAULT_FEEDBACK_ATTACHMENT_LABELS, labelsProp);
-  // Under `multiple` the heading is `attachmentList` — a screenshot AND photos — which
-  // also names the chip list beneath it: one string, so the two cannot disagree. Its old
-  // second name, `feedbackDialog.attachments`, went in 0.34.
-  const listHeading =
-    labelsProp?.attachmentList ?? attachmentText.attachmentList ?? DEFAULT_FEEDBACK_ATTACHMENT_LABELS.attachmentList!;
-  // The attachment field resolves its own keys from `feedbackAttachment`; it gets the
-  // prop's (so a caller's `attachmentAdd` still wins) plus the resolved heading.
-  const attachmentLabels =
-    props.attachments === "multiple"
-      ? { ...labelsProp, attachment: listHeading, attachmentList: listHeading }
-      : { ...labelsProp, attachment: labels.attachment };
-
-  // Reset the form whenever the dialog is (re)opened — during render, on the
-  // closed-to-open transition, so the old draft never paints for a frame.
-  const [wasOpen, setWasOpen] = useState(open);
-  if (open !== wasOpen) {
-    setWasOpen(open);
-    if (open) {
-      setTitle("");
-      setBody("");
-      setAttachment(null);
-      setScreenshot(null);
-      setFiles([]);
-    }
-  }
-
-  // Trimmed: a subject or body of spaces is empty (keksdose's API answers a blank title
-  // with a 422, and a blank report is no report).
-  const canSubmit = !!title.trim() && (!requireBody || !!body.trim()) && !submitting;
-  const trySubmit = () => {
-    if (!canSubmit) return;
-    if (props.attachments === "multiple") {
-      void props.onSubmit({ title, body, category, screenshot, attachments: files });
-    } else {
-      void props.onSubmit({ title, body, category, attachment });
-    }
-  };
-
-  if (!open) return null;
-
-  const categoryField = (
-    // The select offers exactly `categories`' values, so what it answers is one of them.
-    <Select label={labels.category} value={category} onChange={(e) => onCategoryChange(e.target.value as C)}>
-      {categories.map((c) => (
-        <option key={c.value} value={c.value}>
-          {c.label}
-        </option>
-      ))}
-    </Select>
-  );
-  // On a phone the subject leads as a heading rather than as the second of two
-  // identical boxes under a select (Keksdose feedback #179). `variant="display"`
-  // is a no-op above the phone breakpoint, so the desktop dialog is unchanged.
-  const subjectField = (
-    <Input label={labels.subject} value={title} onChange={(e) => setTitle(e.target.value)} variant="display" />
-  );
-  const bodyTextarea = (
-    <Textarea
-      rows={5}
-      label={requireBody ? labels.body : (labelsProp?.body ?? labels.bodyOptional ?? labels.body)}
-      value={body}
-      onChange={(e) => setBody(e.target.value)}
-      aria-describedby={hasNotice ? noticeId : undefined}
-    />
-  );
-  // 0.38: who will read it, right under what they are writing (§9.2 decision 6).
-  const bodyField = hasNotice ? (
-    <div className="space-y-1">
-      {bodyTextarea}
-      <p id={noticeId} className="text-xs text-muted" data-feedback-public-notice="">
-        {publicNotice}
-      </p>
-    </div>
-  ) : (
-    bodyTextarea
-  );
-  const fieldProps = {
-    labels: attachmentLabels,
-    accept: attachmentAccept,
-    maxBytes: maxAttachmentBytes,
-    onCaptureScreenshot,
-    // Left undefined they are the field's own defaults (secondary / md).
-    buttonVariant: attachmentButtonVariant,
-    buttonSize: attachmentButtonSize,
-    // On `document`, not on the panel: the Modal focuses its own panel on open
-    // and traps Tab inside it, so while this dialog is up every paste in the
-    // page is meant for it — including the one made with nothing in
-    // particular focused, which never reaches a React `onPaste` on a child.
-    documentPaste: open,
-  };
-  const attachmentField =
-    props.attachments === "multiple" ? (
-      <FeedbackAttachmentField
-        {...fieldProps}
-        multiple
-        value={files}
-        onChange={setFiles}
-        max={props.maxAttachments}
-        // The capture goes to its own slot, so it is offered once and never crowds
-        // out a photo; a paste is a photo (a region snip is chosen evidence, not "the
-        // screenshot").
-        screenshot={screenshot}
-        onScreenshotChange={setScreenshot}
-        onError={props.onAttachmentError}
-      />
-    ) : (
-      <FeedbackAttachmentField
-        {...fieldProps}
-        value={attachment}
-        onChange={setAttachment}
-        onError={props.onAttachmentError}
-      />
-    );
-
-  return (
-    <Modal
-      onClose={onClose}
-      // The one dialog whose subject is the page behind it (Keksdose dev#460: "Make
-      // the feedback dialog draggable so I can see behind it if it blocks
-      // something") — you are describing what is under it while you type.
-      draggable
-      onKeyDown={(e) => {
-        if ((e.ctrlKey || e.metaKey) && e.key === "Enter") {
-          e.preventDefault();
-          trySubmit();
-        }
-      }}
-    >
-      {/* Also the drag handle: pressing anywhere on the panel's own chrome moves it,
-          and the heading is the strip a user reaches for. */}
-      <h2 className="mb-3 text-lg font-semibold">{labels.title}</h2>
-      <div className="space-y-3">
-        {isMobile ? (
-          // Phone shape, the same reasoning as the transaction editor's (#177):
-          // the desktop order is the DATA MODEL's order — category, then subject,
-          // then body — but nobody opens this dialog to pick a category. What they
-          // came to do is say the thing, so that leads; the classification and the
-          // evidence follow, a tier down.
-          <>
-            {subjectField}
-            {bodyField}
-            <div className="space-y-3 border-t border-subtle pt-3">
-              {categoryField}
-              {attachmentField}
-              {contextSlot}
-            </div>
-          </>
-        ) : (
-          <>
-            {categoryField}
-            {subjectField}
-            {bodyField}
-            {attachmentField}
-            {contextSlot}
-          </>
-        )}
-        <div className="flex items-center justify-between gap-2">
-          <div className="text-xs text-placeholder">
-            {typeof labels.submitHint === "function" ? labels.submitHint(isApplePlatform()) : labels.submitHint}
-          </div>
-          <div className="flex gap-2">
-            <Button variant="ghost" onClick={onClose}>
-              {labels.cancel}
-            </Button>
-            <Button onClick={trySubmit} disabled={!canSubmit}>
-              {labels.save}
-            </Button>
-          </div>
-        </div>
-      </div>
-    </Modal>
-  );
-}

package/src/feedback/feedback-entry-file.tsx

@@ -1,150 +0,0 @@
-import { useState } from "react";
-import { AuthedImage } from "../components/authed-image";
-import { toast } from "../components/toast";
-import type { AuthedFetcher } from "../hooks/use-authed-src";
-import { useKitLabels } from "../i18n/kit-labels";
-import { cn } from "../lib/cn";
-import { DEFAULT_FEEDBACK_ATTACHMENT_LABELS, DEFAULT_MAX_ATTACHMENT_BYTES } from "./feedback-attachment";
-import type { FeedbackNoteAttachment } from "./feedback-inbox";
-import { useFeedbackToastLabels } from "./feedback-labels";
-import { FeedbackAttachmentDownload, plainFeedbackFetch } from "./feedback-attachment-download";
-import { FEEDBACK_ATTACHMENT_ACCEPT, isImageAttachment } from "./feedback-record";
-import { DEFAULT_FEEDBACK_DETAIL_LABELS } from "./feedback-row-detail-labels";
-import type { FeedbackComposerAttachment } from "./feedback-thread";
-
-/**
- * One file of a conversation entry, and the upload behind an entry's composer
- * (docs/feedback-harmonization.md §12, round 0.47; keksdose run 82 R1, live #447).
- *
- * - {@link FeedbackEntryFile}: a picture drawn INLINE — a thumbnail fetched through the
- *   app's authenticated GET, a tap opens it full size in a tab — and any other file a
- *   download button, as the row detail's Attachment section draws them. The reply
- *   timeline, the rework entries and the comment thread all draw their file with it.
- * - {@link useFeedbackEntryUpload}: the rework note's one-file field (paste from the
- *   clipboard, capture, pick; the contract's types and 10 MB, §3.5) for a
- *   {@link ChatComposer}, and the upload that runs FIRST on send, so an entry never names
- *   a file that did not arrive.
- */
-
-export interface FeedbackEntryFileProps {
-  /** The entry's `attachment_url` — `/api/v1/feedback/attachments/<key>`. */
-  url: string;
-  /** The app's authenticated GET (`AuthedImage`'s): the attachment route wants the
-   *  bearer token (§3.5). Left out, the browser's own fetch with same-origin cookies. */
-  fetcher?: AuthedFetcher | null;
-  className?: string;
-}
-
-/**
- * An entry's one file (§12): a picture (`png`, `jpg`, `webp`, `gif` — by the key's
- * extension, which the server minted from the sniffed bytes) as an inline thumbnail that
- * opens full size in a new tab (`AuthedImage`'s `link`: the `blob:` URL, never the API
- * path); anything else a download button. A picture that will not load falls back to the
- * download button, so a broken file still says it is there. `alt`:
- * `feedbackDetail.attachment`.
- */
-export function FeedbackEntryFile({ url, fetcher, className }: FeedbackEntryFileProps) {
-  const labels = useKitLabels("feedbackDetail", DEFAULT_FEEDBACK_DETAIL_LABELS);
-  const fetchFile = fetcher ?? plainFeedbackFetch;
-  return (
-    <span className={cn("inline-block min-w-0 max-w-full", className)} data-feedback-entry-file={url}>
-      {isImageAttachment(url) ? (
-        <AuthedImage
-          src={url}
-          alt={labels.attachment}
-          fetcher={fetchFile}
-          link
-          stopPropagation
-          errorFallback={<FeedbackAttachmentDownload url={url} fetcher={fetchFile} />}
-          wrapperClassName="inline-block max-w-full"
-          className="max-h-40 max-w-full rounded border border-subtle"
-        />
-      ) : (
-        <FeedbackAttachmentDownload url={url} fetcher={fetchFile} />
-      )}
-    </span>
-  );
-}
-
-/* ── The composer's one file ──────────────────────────────────────────────── */
-
-/** `POST /feedback/attachments` — the file, answered with its URL. */
-export type FeedbackEntryUpload = (file: File) => Promise<string>;
-
-export interface FeedbackEntryUploadOptions {
-  /** The upload. Left out, the composer is text only. */
-  onUpload?: FeedbackEntryUpload;
-  /** The "Capture screenshot" button — the kit's `captureAppScreenshot` or the app's
-   *  own. A rejection toasts `feedbackToast.captureFailed` and adds nothing. */
-  onCaptureScreenshot?: () => Promise<File | null>;
-  /** Over the field's defaults: the contract's types and 10 MB (§3.5), the
-   *  `feedbackToast` refusals. The same object the rework section takes. */
-  attachment?: Partial<FeedbackNoteAttachment>;
-}
-
-export interface FeedbackEntryUploadState {
-  /** For {@link ChatComposer}'s `attachment`; `undefined` without `onUpload`. */
-  composerAttachment: FeedbackComposerAttachment | undefined;
-  /** Upload the picked file, if any: its URL, `undefined` for none. Rejects after a
-   *  toast (`feedbackAttachment.attachmentUploadFailed`) when the upload fails — the
-   *  send then stops and the composer keeps the draft and the file. */
-  upload: (file: File | null) => Promise<string | undefined>;
-  /** An upload is running — add it to the composer's `pending`. */
-  uploading: boolean;
-}
-
-/**
- * The rework note's file field for a reply or a comment composer (§12): one file, added,
- * captured or pasted from the clipboard into the box, the contract's types and 10 MB; and
- * the upload, awaited before the entry is sent.
- */
-export function useFeedbackEntryUpload({
-  onUpload,
-  onCaptureScreenshot,
-  attachment,
-}: FeedbackEntryUploadOptions): FeedbackEntryUploadState {
-  const toasts = useFeedbackToastLabels();
-  const fieldLabels = useKitLabels("feedbackAttachment", DEFAULT_FEEDBACK_ATTACHMENT_LABELS);
-  const [uploading, setUploading] = useState(false);
-
-  const capture = onCaptureScreenshot
-    ? async () => {
-        try {
-          return await onCaptureScreenshot();
-        } catch {
-          toast.error(toasts.captureFailed);
-          return null;
-        }
-      }
-    : undefined;
-
-  const composerAttachment: FeedbackComposerAttachment | undefined = onUpload
-    ? {
-        accept: FEEDBACK_ATTACHMENT_ACCEPT,
-        maxBytes: DEFAULT_MAX_ATTACHMENT_BYTES,
-        onError: (kind) => {
-          toast.error(kind === "type" ? toasts.attachmentUnsupported : toasts.attachmentTooLarge);
-        },
-        onCaptureScreenshot: capture,
-        buttonVariant: "ghost",
-        buttonSize: "sm",
-        ...attachment,
-      }
-    : undefined;
-
-  const upload = async (file: File | null) => {
-    if (!file || !onUpload) return undefined;
-    setUploading(true);
-    try {
-      return await onUpload(file);
-    } catch (error) {
-      const failed = fieldLabels.attachmentUploadFailed ?? DEFAULT_FEEDBACK_ATTACHMENT_LABELS.attachmentUploadFailed!;
-      toast.error(failed(file.name));
-      throw error;
-    } finally {
-      setUploading(false);
-    }
-  };
-
-  return { composerAttachment, upload, uploading };
-}