canopycms 0.0.67-int.90 → 0.0.67

package/dist/editor/fields/DateTimeField.js

@@ -2,10 +2,10 @@ import { jsx as _jsx } from "react/jsx-runtime";
 import { useId } from 'react';
 import { Input } from '@mantine/core';
 /**
- * Convert a stored value (ISO 8601 UTC, e.g. "2024-03-15T14:30:00.000Z")
- * into the "local wall-clock" string a `datetime-local` input expects
- * (`YYYY-MM-DDTHH:mm:ss`, no timezone). Returns '' for '' or an unparsable
- * value.
+ * Converts a stored value (ISO 8601 UTC, e.g. `YYYY-MM-DDTHH:mm:ss.sssZ`)
+ * into the local wall-clock string a `datetime-local` input expects
+ * (`YYYY-MM-DDTHH:mm:ss`, no timezone). Returns '' for '' or an unparsable value.
+ * @internal Exported for tests.
  */
 export function isoToDatetimeLocalValue(iso) {
     if (!iso)
@@ -16,15 +16,14 @@ export function isoToDatetimeLocalValue(iso) {
     const pad = (n) => String(n).padStart(2, '0');
     const base = `${date.getFullYear()}-${pad(date.getMonth() + 1)}-${pad(date.getDate())}` +
         `T${pad(date.getHours())}:${pad(date.getMinutes())}`;
-    // Match the platform's own canonical `datetime-local` serialization: the
-    // seconds component is included only when non-zero (a real browser's
-    // input.value getter does the same), so the value we set and what the
-    // control reports back agree exactly.
+    // Seconds are included only when non-zero, matching a real browser's own
+    // `datetime-local` serialization, so the value we set agrees with what the control reports back.
     return date.getSeconds() === 0 ? base : `${base}:${pad(date.getSeconds())}`;
 }
 /**
  * Convert a `datetime-local` input's local wall-clock string back into the
  * ISO 8601 UTC storage format. Returns '' for '' or an unparsable value.
+ * @internal Exported for tests.
  */
 export function datetimeLocalValueToIso(local) {
     if (!local)
@@ -37,29 +36,21 @@ export function datetimeLocalValueToIso(local) {
 /**
  * Editor for `type: 'datetime'` fields.
  *
- * Storage format: ISO 8601 UTC string (e.g. "2024-03-15T14:30:00.000Z") —
- * what `Date.prototype.toISOString()` produces and what
- * `validation/entry-validator.ts`'s datetime check (`Date.parse`) accepts.
- * Empty string means "not set" (matches entry-validator's empty-string
- * check for required fields).
+ * Storage format: ISO 8601 UTC string (e.g. `YYYY-MM-DDTHH:mm:ss.sssZ`) — what
+ * `Date.prototype.toISOString()` produces and `validation/entry-validator.ts`'s
+ * datetime check (`Date.parse`) accepts. Empty string means "not set".
  *
- * `@mantine/dates` is not a dependency of this package, so per house rules
- * we don't add one just for this field: a native `<input
- * type="datetime-local">` wrapped in Mantine's `Input`/`Input.Wrapper`
- * gives a real date+time picker with zero new dependencies.
+ * Uses a native `datetime-local` input in Mantine's `Input.Wrapper` rather than
+ * `@mantine/dates` (not a dependency here) — a real picker with zero new deps.
  *
- * `datetime-local` has no timezone concept — it shows/accepts local
- * "wall-clock" time. We convert UTC ISO -> local for display and local ->
- * UTC ISO on change, so loading a value and saving it unedited round-trips
- * to the exact same stored string instead of drifting by the browser's UTC
- * offset. `step={1}` keeps seconds in that round trip; sub-second
- * precision in the source data is not preserved (`datetime-local` has no
- * milliseconds field), so a stored value with non-zero milliseconds will
- * have them zeroed out once resaved.
+ * `datetime-local` has no timezone: converts UTC ISO -> local for display and
+ * back on change, so an unedited load-then-save round-trips exactly instead of
+ * drifting by the browser's offset. `step={1}` preserves seconds in that
+ * round-trip; sub-second precision is not preserved (no milliseconds field),
+ * so a value with non-zero milliseconds is zeroed out once resaved.
  */
 export const DateTimeField = ({ id, label, value, onChange, dataCanopyField, }) => {
     const generatedId = useId();
     const inputId = id ?? generatedId;
     return (_jsx(Input.Wrapper, { id: inputId, label: label, size: "sm", children: _jsx(Input, { type: "datetime-local", step: 1, size: "sm", value: isoToDatetimeLocalValue(value), onChange: (e) => onChange(datetimeLocalValueToIso(e.currentTarget.value)), "data-canopy-field": dataCanopyField }) }));
 };
-export default DateTimeField;

package/dist/editor/fields/ImageField.d.ts

@@ -1,6 +1,6 @@
 import React from 'react';
 import type { ImageFieldValue } from '../../config/index.js';
-export interface ImageFieldErrors {
+interface ImageFieldErrors {
     src?: string;
     alt?: string;
     crop?: string;
@@ -18,4 +18,4 @@ export interface ImageFieldProps {
     errors?: ImageFieldErrors;
 }
 export declare const ImageField: React.FC<ImageFieldProps>;
-export default ImageField;
+export {};

package/dist/editor/fields/ImageField.js

@@ -20,8 +20,7 @@ export const ImageField = ({ id, label, value, onChange, aspect, altOptional, da
     const [pickerOpen, setPickerOpen] = useState(false);
     const [cropRequest, setCropRequest] = useState(null);
     // Dropzone-level rejections (wrong type/too large) never reach useAssetUpload
-    // (Dropzone filters them out before onDrop fires), so they need their own
-    // error slot rather than piggybacking on upload.error.
+    // (filtered before onDrop fires), so they need their own error slot.
     const [dropError, setDropError] = useState(null);
     const altInputRef = useRef(null);
     const justCommittedRef = useRef(false);
@@ -30,20 +29,17 @@ export const ImageField = ({ id, label, value, onChange, aspect, altOptional, da
     const previewSrc = value
         ? assetUrl({ src: value.src }, { width: PREVIEW_WIDTH, crop: value.crop, baseUrl })
         : undefined;
-    // Broken-preview fallback, consistent with AssetCard's thumbnail fallback
-    // (same icon/copy, same "adjust state during render" reset pattern rather
-    // than a useEffect - see AssetCard.tsx for the rationale). This covers
-    // both an asset that was broken at upload time (pre-existing content) and
-    // a transform that fails for some other reason at render time.
+    // Broken-preview fallback, mirroring AssetCard.tsx's thumbnail fallback (same
+    // icon/copy, same reset-during-render pattern). Covers both an asset broken
+    // at upload time and a transform failing at render time.
     const [previewFailed, setPreviewFailed] = useState(false);
     const [prevPreviewSrc, setPrevPreviewSrc] = useState(previewSrc);
     if (previewSrc !== prevPreviewSrc) {
         setPrevPreviewSrc(previewSrc);
         setPreviewFailed(false);
     }
-    // Focus the alt input right after a new image commits (pick or upload),
-    // so the editor's next keystroke goes straight into the field most likely
-    // to need attention.
+    // Focuses the alt input right after a new image commits (pick or upload),
+    // so the next keystroke lands in the field most likely to need attention.
     useEffect(() => {
         if (justCommittedRef.current) {
             justCommittedRef.current = false;
@@ -54,9 +50,8 @@ export const ImageField = ({ id, label, value, onChange, aspect, altOptional, da
         justCommittedRef.current = true;
         onChange({
             src: asset.src,
-            // Preserve the current alt text on replace - it often still describes
-            // the new image (e.g. "hero photo"), and the editor can always edit it.
-            // Selecting into an empty field has no prior alt, so it stays ''.
+            // Preserves the current alt text on replace (it often still fits); an
+            // empty field has no prior alt, so it stays ''.
             alt: value?.alt ?? '',
             ...(asset.width !== undefined ? { width: asset.width } : {}),
             ...(asset.height !== undefined ? { height: asset.height } : {}),
@@ -123,4 +118,3 @@ export const ImageField = ({ id, label, value, onChange, aspect, altOptional, da
                             display: 'block',
                         }, onError: () => setPreviewFailed(true) })), errors?.src && (_jsx(Text, { size: "xs", c: "red", children: errors.src })), _jsx(TextInput, { id: inputId, ref: altInputRef, label: "Alt text", required: !altOptional, value: value.alt, onChange: (event) => handleAltChange(event.currentTarget.value), error: errors?.alt, size: "sm", "data-testid": `image-field-alt-${dataCanopyField}` }), _jsxs(Group, { gap: "xs", children: [_jsx(Button, { variant: "light", size: "xs", onClick: () => setPickerOpen(true), "data-testid": `image-field-replace-${dataCanopyField}`, children: "Replace" }), aspectRatio !== undefined && (_jsx(Button, { variant: "light", size: "xs", onClick: () => setCropRequest({ kind: 'existing' }), "data-testid": `image-field-crop-${dataCanopyField}`, children: "Crop" })), _jsx(Button, { variant: "subtle", color: "red", size: "xs", onClick: handleRemove, "data-testid": `image-field-remove-${dataCanopyField}`, children: "Remove" })] }), errors?.crop && (_jsx(Text, { size: "xs", c: "red", children: errors.crop }))] })), _jsx(MediaLibrary, { opened: pickerOpen, onClose: () => setPickerOpen(false), mode: "picker", onSelect: handleAssetReady }), aspectRatio !== undefined && (_jsx(CropStep, { opened: cropRequest !== null, onClose: () => setCropRequest(null), imageSrc: cropImageSrc, aspect: aspectRatio, initialCrop: cropInitial, onConfirm: handleCropConfirm }))] }));
 };
-export default ImageField;

package/dist/editor/fields/InlineGroupField.d.ts

@@ -13,4 +13,3 @@ export interface InlineGroupFieldProps {
     path: Array<string | number>;
 }
 export declare const InlineGroupField: React.FC<InlineGroupFieldProps>;
-export default InlineGroupField;

package/dist/editor/fields/InlineGroupField.js

@@ -12,4 +12,3 @@ export const InlineGroupField = ({ label, description, fields, value, onChange,
                         return (_jsx("div", { children: renderField(field, value[field.name], (next) => onChange({ ...value, [field.name]: next }), fieldPath) }, formatCanopyPath(fieldPath)));
                     }) })] }) }));
 };
-export default InlineGroupField;

package/dist/editor/fields/MarkdownField.d.ts

@@ -7,4 +7,3 @@ export interface MarkdownFieldProps {
     dataCanopyField?: string;
 }
 export declare const MarkdownField: React.FC<MarkdownFieldProps>;
-export default MarkdownField;

package/dist/editor/fields/MarkdownField.js

@@ -8,15 +8,14 @@ import { useApiClient } from '../context/index.js';
 import { uploadAsset } from '../media/upload-asset.js';
 const MDXEditorLazy = React.lazy(async () => {
     const [{ MDXEditor }, { headingsPlugin, listsPlugin, quotePlugin, thematicBreakPlugin, markdownShortcutPlugin, linkPlugin, linkDialogPlugin, imagePlugin, tablePlugin, toolbarPlugin, codeBlockPlugin, codeMirrorPlugin, BoldItalicUnderlineToggles, BlockTypeSelect, ListsToggle, CreateLink, InsertImage, InsertTable, InsertThematicBreak, CodeToggle, InsertCodeBlock, UndoRedo, Separator, insertMarkdown$, usePublisher, useCellValues, saveImage$, closeImageDialog$, imageDialogState$, },] = await Promise.all([import('@mdxeditor/editor'), import('@mdxeditor/editor')]);
-    /** Toolbar wrapper that provides insertMarkdown to InsertEntryLink */
     const EntryLinkToolbarButton = () => {
         const insertMarkdown = usePublisher(insertMarkdown$);
         return _jsx(InsertEntryLink, { onInsert: insertMarkdown });
     };
     /**
-     * Bridges mdxeditor's realm cells (only reachable once this lazy chunk has
+     * Bridges mdxeditor's realm cells (reachable only once this lazy chunk has
      * loaded) into MdxImageDialog's plain-props interface, so that component
-     * itself never imports `@mdxeditor/editor` at runtime. Same pattern as
+     * never imports `@mdxeditor/editor` at runtime — same pattern as
      * `EntryLinkToolbarButton` above.
      */
     const MdxImageDialogBridge = () => {
@@ -60,7 +59,6 @@ const MDXEditorLazy = React.lazy(async () => {
     };
     return { default: WrappedEditor };
 });
-/** Style the editor wrapper with a white background and border so it's visually distinct from the form background. */
 const editorWrapperStyle = {
     background: '#fff',
     border: '1px solid var(--mantine-color-gray-4, #ced4da)',
@@ -102,12 +100,10 @@ export const MarkdownField = ({ id, label, value, onChange, dataCanopyField, })
     const editorRef = useRef(null);
     const lastExternalValue = useRef(value);
     const apiClient = useApiClient();
-    // Drives both MDXEditor's own drag/drop/paste upload flow and the Upload
-    // tab in our custom image dialog (MdxImageDialog) via the SAME presign/
-    // finalize-or-proxied pipeline used everywhere else in the editor (see
-    // media/upload-asset.ts). Stable across renders (memoized on the API
-    // client, which ApiClientProvider itself memoizes) so MDXEditor's plugin
-    // list doesn't churn on every keystroke.
+    // Drives both MDXEditor's drag/drop/paste upload and the custom image
+    // dialog's Upload tab via the same presign/finalize-or-proxied pipeline
+    // (media/upload-asset.ts). Memoized on the API client (itself memoized by
+    // ApiClientProvider) so MDXEditor's plugin list doesn't churn per keystroke.
     const imageUploadHandler = useCallback(async (file) => {
         const asset = await uploadAsset(apiClient, file);
         return asset.src;
@@ -125,4 +121,3 @@ export const MarkdownField = ({ id, label, value, onChange, dataCanopyField, })
     }, [onChange]);
     return (_jsxs("div", { id: inputId, "data-canopy-field": dataCanopyField, className: "canopy-markdown-field", children: [label && (_jsx(Text, { size: "sm", fw: 500, mb: 4, children: label })), _jsx(EditorContentStyles, {}), _jsx("div", { style: editorWrapperStyle, children: _jsx(Suspense, { fallback: _jsx(FallbackTextarea, { value: value, onChange: onChange }), children: _jsx(MDXEditorLazy, { markdown: value, onChange: handleChange, editorRef: editorRef, imageUploadHandler: imageUploadHandler }) }) })] }));
 };
-export default MarkdownField;

package/dist/editor/fields/MdxImageDialog.d.ts

@@ -1,5 +1,6 @@
 import React from 'react';
 import type { EditingImageDialogState, InactiveImageDialogState, NewImageDialogState, SaveImageParameters } from '@mdxeditor/editor';
+/** @internal Exported for tests. */
 export type MdxImageDialogState = InactiveImageDialogState | NewImageDialogState | EditingImageDialogState;
 export interface MdxImageDialogProps {
     state: MdxImageDialogState;
@@ -12,4 +13,3 @@ export interface MdxImageDialogProps {
  * in MarkdownField.tsx.
  */
 export declare const MdxImageDialog: React.FC<MdxImageDialogProps>;
-export default MdxImageDialog;

package/dist/editor/fields/MdxImageDialog.js

@@ -69,4 +69,3 @@ export const MdxImageDialog = ({ state, onSave, onClose }) => {
                     }, children: [_jsxs(Tabs.List, { children: [_jsx(Tabs.Tab, { value: "upload", "data-testid": "mdx-image-dialog-tab-upload", children: "Upload" }), _jsx(Tabs.Tab, { value: "library", "data-testid": "mdx-image-dialog-tab-library", children: "From library" }), _jsx(Tabs.Tab, { value: "url", "data-testid": "mdx-image-dialog-tab-url", children: "By URL" })] }), _jsx(Tabs.Panel, { value: "upload", pt: "sm", children: _jsxs(Stack, { gap: "xs", children: [_jsx(Dropzone, { onDrop: (files) => void handleDrop(files), onReject: handleReject, maxSize: MAX_UPLOAD_BYTES, accept: ACCEPTED_IMAGE_MIME_TYPES, loading: upload.uploading, multiple: false, "data-testid": "mdx-image-dialog-dropzone", children: _jsxs(Group, { justify: "center", gap: "xs", py: "sm", style: { pointerEvents: 'none' }, children: [_jsx(IconUpload, { size: 20 }), _jsx(Text, { size: "sm", children: "Drop an image here, or click to browse" })] }) }), upload.uploading &&
                                         (upload.progress !== null ? (_jsx(Progress, { value: upload.progress * 100, size: "sm" })) : (_jsx(Progress, { value: 100, size: "sm", animated: true }))), (upload.error || dropError) && (_jsx(Alert, { icon: _jsx(IconAlertCircle, { size: 16 }), color: "red", children: upload.error || dropError }))] }) }), _jsx(Tabs.Panel, { value: "library", pt: "sm", children: _jsx("div", { style: { height: LIBRARY_PANEL_HEIGHT }, children: _jsx(MediaLibraryBody, { opened: tab === 'library', mode: "picker", onSelect: handlePickFromLibrary }) }) }), _jsx(Tabs.Panel, { value: "url", pt: "sm", children: _jsxs(Stack, { gap: "xs", children: [_jsx(TextInput, { label: "Image URL", placeholder: "https://example.com/image.png", value: urlValue, onChange: (event) => setUrlValue(event.currentTarget.value), "data-testid": "mdx-image-dialog-url" }), _jsx(Group, { justify: "flex-end", children: _jsx(Button, { onClick: handleUrlSubmit, disabled: !urlValue.trim(), "data-testid": "mdx-image-dialog-url-submit", children: "Insert" }) })] }) })] }), _jsx(Group, { justify: "flex-end", children: _jsx(Button, { variant: "default", onClick: onClose, children: "Cancel" }) })] }) }));
 };
-export default MdxImageDialog;

package/dist/editor/fields/NumberField.d.ts

@@ -9,25 +9,15 @@ export interface NumberFieldProps {
 /**
  * Editor for `type: 'number'` fields.
  *
- * `undefined` means "not filled in" and is distinct from `0`: an empty
- * input must not silently become `0` (that would make a required numeric
- * field with value `0` look correct while an actually-empty field also
- * looks fine), and `0` must not be mistaken for "absent". Mantine's
- * `NumberInput` reports an empty input as `''`; we translate that to
- * `undefined` so `validation/entry-validator.ts`'s required check (which
- * treats only `undefined`/`null` as empty for numbers) agrees with what the
- * form displays.
+ * `undefined` (not `0`) means "not filled in": Mantine's `NumberInput` reports
+ * an empty input as `''`, which this field translates to `undefined` so
+ * `validation/entry-validator.ts`'s required check agrees with the form.
  *
- * IN-PROGRESS TEXT IS MIRRORED BACK, NOT THE PARSED NUMBER, and that is
- * load-bearing rather than stylistic. Mantine reports an entry as a STRING
- * exactly when the text and its numeric value disagree (`'-0'`, `'0.'`,
- * `'-0.0'`, leading zeros) and as a number otherwise. Handing the PARSED
- * number back as the controlled value re-renders the input from
- * `String(number)` — and `String(-0)` is `'0'`, so typing `-0.5` lost its
- * minus after the second keystroke and the `.5` appended to a POSITIVE
- * zero: the user typed `-0.5` and `0.5` was stored, silently. Keeping the
- * text Mantine itself reported keeps the sign on screen until the entry is
- * a complete number. See NumberField.test.tsx's keystroke matrix.
+ * The in-progress TEXT is mirrored back, not the parsed number. Mantine
+ * reports the entry as a string exactly when text and numeric value disagree
+ * (`'-0'`, `'0.'`, leading zeros); re-rendering from `String(parsedNumber)`
+ * instead loses that distinction — `String(-0)` is `'0'`, so typing `-0.5`
+ * would silently store `0.5` after the second keystroke. See
+ * NumberField.test.tsx's keystroke matrix.
  */
 export declare const NumberField: React.FC<NumberFieldProps>;
-export default NumberField;

package/dist/editor/fields/NumberField.js

@@ -16,37 +16,26 @@ const toNumericValue = (raw) => {
 /**
  * Editor for `type: 'number'` fields.
  *
- * `undefined` means "not filled in" and is distinct from `0`: an empty
- * input must not silently become `0` (that would make a required numeric
- * field with value `0` look correct while an actually-empty field also
- * looks fine), and `0` must not be mistaken for "absent". Mantine's
- * `NumberInput` reports an empty input as `''`; we translate that to
- * `undefined` so `validation/entry-validator.ts`'s required check (which
- * treats only `undefined`/`null` as empty for numbers) agrees with what the
- * form displays.
+ * `undefined` (not `0`) means "not filled in": Mantine's `NumberInput` reports
+ * an empty input as `''`, which this field translates to `undefined` so
+ * `validation/entry-validator.ts`'s required check agrees with the form.
  *
- * IN-PROGRESS TEXT IS MIRRORED BACK, NOT THE PARSED NUMBER, and that is
- * load-bearing rather than stylistic. Mantine reports an entry as a STRING
- * exactly when the text and its numeric value disagree (`'-0'`, `'0.'`,
- * `'-0.0'`, leading zeros) and as a number otherwise. Handing the PARSED
- * number back as the controlled value re-renders the input from
- * `String(number)` — and `String(-0)` is `'0'`, so typing `-0.5` lost its
- * minus after the second keystroke and the `.5` appended to a POSITIVE
- * zero: the user typed `-0.5` and `0.5` was stored, silently. Keeping the
- * text Mantine itself reported keeps the sign on screen until the entry is
- * a complete number. See NumberField.test.tsx's keystroke matrix.
+ * The in-progress TEXT is mirrored back, not the parsed number. Mantine
+ * reports the entry as a string exactly when text and numeric value disagree
+ * (`'-0'`, `'0.'`, leading zeros); re-rendering from `String(parsedNumber)`
+ * instead loses that distinction — `String(-0)` is `'0'`, so typing `-0.5`
+ * would silently store `0.5` after the second keystroke. See
+ * NumberField.test.tsx's keystroke matrix.
  */
 export const NumberField = ({ id, label, value, onChange, dataCanopyField, }) => {
     const generatedId = useId();
     const inputId = id ?? generatedId;
     const [inputValue, setInputValue] = useState(value ?? '');
-    // Show the in-progress text only while it still means what the parent
-    // holds. Once the parent's value diverges (entry loaded, draft discarded,
-    // "Reload File"), that value wins and the stale text is dropped.
+    // Shows the in-progress text only while it still matches the parent's
+    // value; once the parent's value diverges (load, discard, reload), that value wins.
     const displayValue = toNumericValue(inputValue) === value ? inputValue : (value ?? '');
     return (_jsx(NumberInput, { id: inputId, label: label, value: displayValue, size: "sm", onChange: (next) => {
             setInputValue(next);
             onChange(toNumericValue(next));
         }, "data-canopy-field": dataCanopyField }));
 };
-export default NumberField;

package/dist/editor/fields/NumberListField.d.ts

@@ -9,16 +9,13 @@ export interface NumberListFieldProps {
 /**
  * Editor for `type: 'number', list: true` fields.
  *
- * Mirrors `StringListField`'s approach (Mantine's `TagsInput`: type + Enter
- * adds an item, Backspace on an empty input removes the last one) since
- * there is no numeric equivalent in Mantine. Tags are parsed to numbers on
- * change; a tag that doesn't parse to a finite number is not stored (it
- * would be `NaN`, or a spurious `0` for a blank one).
+ * Mirrors `StringListField`'s `TagsInput` approach (type + Enter adds an
+ * item, Backspace on empty removes the last) since Mantine has no numeric
+ * equivalent. A tag that doesn't parse to a finite number is dropped rather
+ * than stored as `NaN`.
  *
- * A rejected tag is REPORTED, not silently swallowed. Dropping it quietly
- * looked identical to accepting it - the tag vanished on Enter with no
- * error, no value, and nothing distinguishing "typo" from "the field
- * doesn't work" - so the rejected text is named in the field's error slot.
+ * A dropped tag is reported, not silently swallowed — otherwise it vanished
+ * on Enter indistinguishably from being accepted, with nothing to tell a
+ * typo from a broken field — so rejected text is named in the error slot.
  */
 export declare const NumberListField: React.FC<NumberListFieldProps>;
-export default NumberListField;

package/dist/editor/fields/NumberListField.js

@@ -18,16 +18,14 @@ const parseTag = (tag) => {
 /**
  * Editor for `type: 'number', list: true` fields.
  *
- * Mirrors `StringListField`'s approach (Mantine's `TagsInput`: type + Enter
- * adds an item, Backspace on an empty input removes the last one) since
- * there is no numeric equivalent in Mantine. Tags are parsed to numbers on
- * change; a tag that doesn't parse to a finite number is not stored (it
- * would be `NaN`, or a spurious `0` for a blank one).
+ * Mirrors `StringListField`'s `TagsInput` approach (type + Enter adds an
+ * item, Backspace on empty removes the last) since Mantine has no numeric
+ * equivalent. A tag that doesn't parse to a finite number is dropped rather
+ * than stored as `NaN`.
  *
- * A rejected tag is REPORTED, not silently swallowed. Dropping it quietly
- * looked identical to accepting it - the tag vanished on Enter with no
- * error, no value, and nothing distinguishing "typo" from "the field
- * doesn't work" - so the rejected text is named in the field's error slot.
+ * A dropped tag is reported, not silently swallowed — otherwise it vanished
+ * on Enter indistinguishably from being accepted, with nothing to tell a
+ * typo from a broken field — so rejected text is named in the error slot.
  */
 export const NumberListField = ({ id, label, value, onChange, dataCanopyField, }) => {
     const generatedId = useId();
@@ -49,4 +47,3 @@ export const NumberListField = ({ id, label, value, onChange, dataCanopyField, }
             onChange(parsed);
         }, splitChars: [], allowDuplicates: true, "data-canopy-field": dataCanopyField }));
 };
-export default NumberListField;

package/dist/editor/fields/ObjectField.d.ts

@@ -10,15 +10,12 @@ export interface ObjectFieldProps {
     path: Array<string | number>;
     dataCanopyField?: string;
     /**
-     * When provided, renders a "Clear" affordance next to the label that
-     * resets this object field back to its unset (`undefined`) state.
-     * Used by FormRenderer's non-list 'object' case so a non-list object with
-     * a required child can't get stuck present-but-invalid with no way back
-     * to "not filled in" (see FormRenderer.tsx's `case 'object'`). Omitted
-     * for object-list items, which are removed via the list's own per-item
-     * Remove button instead.
+     * When set, shows a "Clear" affordance that resets this field to unset
+     * (`undefined`) — used by `FormRenderer.tsx`'s non-list `case 'object'` so
+     * a required child can't strand the field present-but-invalid with no way
+     * back to "not filled in". Omitted for object-list items, which remove via
+     * the list's own per-item button.
      */
     onRemove?: () => void;
 }
 export declare const ObjectField: React.FC<ObjectFieldProps>;
-export default ObjectField;

package/dist/editor/fields/ObjectField.js

@@ -8,4 +8,3 @@ export const ObjectField = ({ label, fields, value, onChange, renderField, path,
                         return (_jsx("div", { children: renderField(field, current[field.name], (next) => onChange({ ...current, [field.name]: next }), fieldPath) }, formatCanopyPath(fieldPath)));
                     }) })] }) }));
 };
-export default ObjectField;

package/dist/editor/fields/ReferenceField.d.ts

@@ -1,4 +1,5 @@
 import React from 'react';
+/** @internal Exported for tests. */
 export interface ReferenceOption {
     value: string;
     label: string;
@@ -17,4 +18,3 @@ export interface ReferenceFieldProps {
     dataCanopyField?: string;
 }
 export declare const ReferenceField: React.FC<ReferenceFieldProps>;
-export default ReferenceField;

package/dist/editor/fields/ReferenceField.js

@@ -7,10 +7,10 @@ import { createApiClient } from '../../api/client.js';
 import { useOptionalApiClient } from '../context/index.js';
 import { getErrorMessage } from '../../utils/error.js';
 export const ReferenceField = ({ id, label, options: staticOptions, collections, entryTypes, displayField = 'title', branch = 'main', value, onChange, multiple, dataCanopyField, }) => {
-    // Context-provided client (configured with the deployment's basePath) when rendered inside an
-    // ApiClientProvider -- which it always is in the real Editor tree. `null` outside one (e.g.
-    // FormRenderer.stories.tsx has no provider), in which case the fetch effect below falls back
-    // to a default-configured client.
+    // Configured with the deployment's basePath when rendered inside an
+    // ApiClientProvider (always true in the real Editor tree); `null` outside one
+    // (e.g. FormRenderer.stories.tsx), so the fetch effect falls back to a
+    // default-configured client.
     const contextApiClient = useOptionalApiClient();
     const hasCollections = !!collections && collections.length > 0;
     const hasEntryTypes = !!entryTypes && entryTypes.length > 0;
@@ -19,7 +19,6 @@ export const ReferenceField = ({ id, label, options: staticOptions, collections,
     const [loading, setLoading] = useState(needsFetch);
     const [error, setError] = useState(null);
     const [retryCount, setRetryCount] = useState(0);
-    // Extract ID from value - handle both string IDs and resolved objects
     const extractId = (val) => {
         if (typeof val === 'string')
             return val;
@@ -46,17 +45,14 @@ export const ReferenceField = ({ id, label, options: staticOptions, collections,
             setError(null);
         }
     }
-    // Load options from API if collections or entryTypes are provided and no static options.
+    // Keyed on the derived `fetchKey`, not the raw `collections`/`entryTypes`
+    // arrays: the parent rebuilds those on every render (including every
+    // `refreshEntries()` after a save), so depending on them directly fired
+    // this fetch far more often than the inputs actually changed.
     //
-    // Keyed on the derived `fetchKey` (not the raw `collections`/`entryTypes`
-    // arrays): the parent rebuilds those arrays on every render -- including
-    // every `refreshEntries()` after a save -- so depending on them directly
-    // fired this fetch far more often than the inputs actually changed.
-    //
-    // `active` guards against a stale response: if the key changes again (or
-    // the field unmounts) before this request settles, the loser's `.then`/
-    // `.catch`/`.finally` must not overwrite state a newer request already
-    // owns.
+    // `active` guards against a stale response: if the key changes again or the
+    // field unmounts before this request settles, the loser's `.then`/`.catch`/
+    // `.finally` must not overwrite state a newer request already owns.
     useEffect(() => {
         if (!needsFetch)
             return;
@@ -112,4 +108,3 @@ export const ReferenceField = ({ id, label, options: staticOptions, collections,
     }
     return (_jsx(Stack, { gap: 4, "data-canopy-field": dataCanopyField, "data-testid": `reference-field-${dataCanopyField}`, children: multiple ? (_jsx(MultiSelect, { id: inputId, label: label, data: options, value: normalizedValue, onChange: (next) => onChange(next), searchable: true, placeholder: "Select reference\u2026", size: "sm" })) : (_jsx(Select, { id: inputId, label: label, data: options, value: normalizedValue, onChange: (next) => onChange(next ?? ''), searchable: true, clearable: true, placeholder: "Select reference\u2026", size: "sm" })) }));
 };
-export default ReferenceField;

package/dist/editor/fields/SelectField.d.ts

@@ -1,5 +1,5 @@
 import React from 'react';
-export interface SelectOption {
+interface SelectOption {
     label: string;
     value: string;
 }
@@ -14,4 +14,4 @@ export interface SelectFieldProps {
     dataCanopyField?: string;
 }
 export declare const SelectField: React.FC<SelectFieldProps>;
-export default SelectField;
+export {};

package/dist/editor/fields/SelectField.js

@@ -13,4 +13,3 @@ export const SelectField = ({ id, label, options, value, onChange, multiple, pla
     const inputId = id ?? generatedId;
     return (_jsxs(Stack, { gap: 4, "data-canopy-field": dataCanopyField, children: [multiple ? (_jsx(MultiSelect, { id: inputId, label: label, data: options, value: normalizedValue, onChange: (next) => onChange(next), searchable: true, placeholder: placeholder, size: "sm" })) : (_jsx(Select, { id: inputId, label: label, data: options, value: normalizedValue, onChange: (next) => onChange(next ?? ''), searchable: true, clearable: true, placeholder: placeholder, size: "sm" })), multiple && (_jsx(Text, { size: "xs", c: "dimmed", children: "Searchable multi-select; start typing to filter." }))] }));
 };
-export default SelectField;

package/dist/editor/fields/StringListField.d.ts

@@ -11,9 +11,5 @@ export interface StringListFieldProps {
  *
  * Uses Mantine's TagsInput: type + Enter adds an item, each item renders as a
  * removable pill, and Backspace on an empty input removes the last item.
- * (Before this component existed, string-list fields fell through to the
- * single-value TextField, which coerced the array to a comma-joined string —
- * effectively unsupported.)
  */
 export declare const StringListField: React.FC<StringListFieldProps>;
-export default StringListField;

package/dist/editor/fields/StringListField.js

@@ -6,19 +6,14 @@ import { TagsInput } from '@mantine/core';
  *
  * Uses Mantine's TagsInput: type + Enter adds an item, each item renders as a
  * removable pill, and Backspace on an empty input removes the last item.
- * (Before this component existed, string-list fields fell through to the
- * single-value TextField, which coerced the array to a comma-joined string —
- * effectively unsupported.)
  */
 export const StringListField = ({ id, label, value, onChange, dataCanopyField, }) => {
     const generatedId = useId();
     const inputId = id ?? generatedId;
     return (_jsx(TagsInput, { id: inputId, label: label, value: value, size: "sm", onChange: onChange, 
-        // Faithful generic-list semantics, not tag ergonomics: no comma
-        // splitting ("New York, NY" stays one item — TagsInput's default
-        // splitChars would break it in two) and duplicates are legitimate
-        // list data (the default silently drops them, so existing file data
-        // couldn't round-trip).
+        // Faithful generic-list semantics, not tag ergonomics: no comma-splitting
+        // ("New York, NY" stays one item) and duplicates are legitimate list
+        // data — TagsInput's defaults would break both, so existing file data
+        // couldn't round-trip.
         splitChars: [], allowDuplicates: true, "data-canopy-field": dataCanopyField }));
 };
-export default StringListField;

package/dist/editor/fields/TextField.d.ts

@@ -7,4 +7,3 @@ export interface TextFieldProps {
     dataCanopyField?: string;
 }
 export declare const TextField: React.FC<TextFieldProps>;
-export default TextField;

package/dist/editor/fields/TextField.js

@@ -6,4 +6,3 @@ export const TextField = ({ id, label, value, onChange, dataCanopyField, }) => {
     const inputId = id ?? generatedId;
     return (_jsx(TextInput, { id: inputId, label: label, value: value, size: "sm", onChange: (e) => onChange(e.currentTarget.value), "data-canopy-field": dataCanopyField }));
 };
-export default TextField;

package/dist/editor/fields/ToggleField.d.ts

@@ -8,4 +8,3 @@ export interface ToggleFieldProps {
     testId?: string;
 }
 export declare const ToggleField: React.FC<ToggleFieldProps>;
-export default ToggleField;

package/dist/editor/fields/ToggleField.js

@@ -6,4 +6,3 @@ export const ToggleField = ({ id, label, value, onChange, dataCanopyField, testI
     const inputId = id ?? generatedId;
     return (_jsx(Switch, { id: inputId, label: label, checked: value, onChange: (e) => onChange(e.currentTarget.checked), size: "md", "data-canopy-field": dataCanopyField, wrapperProps: testId ? { 'data-testid': testId } : undefined }));
 };
-export default ToggleField;

package/dist/editor/fields/entry-link/EntryLinkContext.js

@@ -1,9 +1,7 @@
 'use client';
 /**
- * React context for providing entry data to the InsertEntryLink toolbar button.
- *
- * The MarkdownField is lazy-loaded and its toolbar components don't have direct
- * access to the editor's entry list. This context bridges that gap.
+ * Bridges entry data to MarkdownField's lazy-loaded toolbar components (e.g.
+ * InsertEntryLink), which have no direct access to the editor's entry list.
  */
 import { createContext, useContext } from 'react';
 export const EntryLinkContext = createContext({ entries: [] });

package/dist/editor/fields/entry-link/InsertEntryLink.d.ts

@@ -1,9 +1,6 @@
 /**
  * MDXEditor toolbar button for inserting entry links.
  *
- * Opens a modal with a searchable list of entries. When the user selects
- * an entry, inserts [Entry Title](entry:CONTENT_ID) into the editor.
- *
  * Must be rendered inside an MDXEditor toolbar (uses usePublisher from gurx).
  */
 import React from 'react';

package/dist/editor/fields/entry-link/InsertEntryLink.js

@@ -3,9 +3,6 @@ import { jsx as _jsx, jsxs as _jsxs, Fragment as _Fragment } from "react/jsx-run
 /**
  * MDXEditor toolbar button for inserting entry links.
  *
- * Opens a modal with a searchable list of entries. When the user selects
- * an entry, inserts [Entry Title](entry:CONTENT_ID) into the editor.
- *
  * Must be rendered inside an MDXEditor toolbar (uses usePublisher from gurx).
  */
 import { useState, useMemo } from 'react';
@@ -27,7 +24,6 @@ export const InsertEntryLink = ({ onInsert }) => {
             e.slug?.toLowerCase().includes(lower) ||
             e.collectionName?.toLowerCase().includes(lower));
     }, [entries, search]);
-    // Group entries by collection
     const grouped = useMemo(() => {
         const groups = new Map();
         for (const entry of filtered) {