@omnitend/dashboard-for-laravel 0.38.0 → 0.40.0

package/docs/public/api-reference.json

@@ -1,8 +1,8 @@
 {
-  "generated": "2026-07-23T18:28:14.921Z",
+  "generated": "2026-08-25T19:01:45.537Z",
   "package": {
     "name": "@omnitend/dashboard-for-laravel",
-    "version": "0.38.0"
+    "version": "0.40.0"
   },
   "components": {
     "base": [
@@ -1478,7 +1478,7 @@
         "name": "DXCurrencyInput",
         "category": "extended",
         "filePath": "resources/js/components/extended/DXCurrencyInput.vue",
-        "description": "DXCurrencyInput — the money input leaf (#152). A currency-symbol-prefixed numeric input with the display/model split from #69: the MODEL is always a plain number (or null), while the displayed text is padded to the minor-unit precision on blur/seed (`3.8` -> `3.80`) and never reformatted mid-edit. Clearing the input emits `null` — never `NaN`, never `\"\"` — so \"no value\" is one predictable shape (#152). `minorUnits` (#116) edits an integer-minor-unit model (pence) as major units (pounds): display = model / 10^decimals, emit = round(input * 10^decimals). `min`/`max`/`step` and the displayed text are always in MAJOR units — only the model is scaled. DXField's `currency` field type renders this leaf; it exists standalone so a money input outside a form (an inline table correction, a quick filter) doesn't re-inline the `£`-prefix + toFixed + parse foot-guns.",
+        "description": "DXCurrencyInput — the money input leaf (#152). A currency-symbol-prefixed numeric input with the display/model split from #69: the MODEL is always a plain number (or null), while the displayed text is padded to the minor-unit precision on blur/seed (`3.8` -> `3.80`) and never reformatted mid-edit. Clearing the input emits `null` — never `NaN`, never `\"\"` — so \"no value\" is one predictable shape (#152). `minorUnits` (#116) edits an integer-minor-unit model (pence) as major units (pounds): display = model / 10^decimals, emit = round(input * 10^decimals). `min`/`max`/`step` and the displayed text are always in MAJOR units — only the model is scaled. `append` puts a trailing affix after the input — the unit the price is per (\"Pint\", \"per case\", \"each\"). Without it a consumer needing a unit beside the amount has to hand-roll a `DInputGroup` + bare number input, which puts every foot-gun above straight back. A plain string covers most cases; the `#append` slot takes arbitrary content (a unit picker, a button) and wins over the prop, the same prop-with-slot-fallback shape `DXFieldShell` uses for `hint`. DXField's `currency` field type renders this leaf; it exists standalone so a money input outside a form (an inline table correction, a quick filter) doesn't re-inline the `£`-prefix + toFixed + parse foot-guns. On a DXField, reach the affix through the field's `inputProps` (`{ append: 'per case' }`) — it binds to this prop like any other.",
         "props": [
           {
             "name": "modelValue",
@@ -1514,6 +1514,13 @@
             "required": false,
             "default": "undefined",
             "description": "Input step in MAJOR units (default: one minor unit, e.g. 0.01)."
+          },
+          {
+            "name": "append",
+            "type": "string",
+            "required": false,
+            "default": "undefined",
+            "description": "Trailing affix shown after the input — the unit the amount is per\n (\"Pint\", \"per case\", \"each\"). Omit for no trailing cell. The `#append`\n slot overrides it when the affix needs to be more than a string."
           }
         ],
         "events": [
@@ -1523,7 +1530,13 @@
             "properties": []
           }
         ],
-        "slots": [],
+        "slots": [
+          {
+            "name": "append",
+            "description": "Trailing content after the input — arbitrary markup, overriding the `append` prop.",
+            "bindings": []
+          }
+        ],
         "methods": []
       },
       {
@@ -3097,7 +3110,7 @@
             "name": "size",
             "type": "\"sm\"",
             "required": false,
-            "description": "`\"sm\"` renders a compact box (~31px vs the default ~35px input height) for\ndense rows that repeat the switch per item (a per-line visibility toggle in\na modal). Omit for the standard size, which matches the `.form-control`\nheight so a switch lines up with inputs beside it."
+            "description": "`\"sm\"` renders a compact box (a few px shorter than the default, which\nmatches the input height) for dense rows that repeat the switch per item (a\nper-line visibility toggle in a modal). Omit for the standard size, which\nlines the switch up with the `.form-control`\nheight so a switch lines up with inputs beside it."
           }
         ],
         "events": [
@@ -3414,7 +3427,13 @@
             "name": "deleteGuard",
             "type": "TSFunctionType",
             "required": false,
-            "description": "Guard run when Delete is clicked, before the confirm dialog and request.\nReturn a message for a non-deletable item to show it immediately (as a\ntoast) and skip both the confirm and the delete request; return\n`null`/`undefined` to proceed with the normal confirm + delete. Lets you\nshort-circuit a doomed delete (e.g. a record with dependents that the\nserver would reject) with an immediate, specific reason."
+            "description": "Guard run when Delete is clicked, before the confirm dialog and request.\nReturn a message for a non-deletable item to show it immediately (as a\ntoast) and skip both the confirm and the delete request; return\n`null`/`undefined` to proceed with the normal confirm + delete. Lets you\nshort-circuit a doomed delete (e.g. a record with dependents that the\nserver would reject) with an immediate, specific reason.\n\nAWAITED, so it may return a promise — the same shape as `saveGuard`, so\nan `async` guard behaves the way its author expects. A guard that throws\nalso aborts, surfacing its message."
+          },
+          {
+            "name": "saveGuard",
+            "type": "TSFunctionType",
+            "required": false,
+            "description": "Guard run when the modal's Save/Create is clicked, before the request.\nReturn a message to abort the save — it is shown immediately (as a toast)\nand no request is made; return `null`/`undefined` to proceed. Covers both\nthe `editUrl` and `createUrl` paths.\n\nAWAITED (as `deleteGuard` is), so it may return a promise: the case it\nexists for is an async control in an `edit-value` slot — an image\nupload — that has not finished when Save is clicked. Without the guard the\nform submits the previous media map, the save SUCCEEDS, the toast says\nsaved and the modal closes: the image is lost with no error anywhere,\nbecause every individual step worked. Await the upload here and the save\nsimply waits for it.\n\n`item` is the row being edited, `null` in create mode (as in the\n`edit-value` slot's binding); `data` is the live form data. Aborting\nleaves the modal open with the user's edits intact. A guard that throws\nalso aborts, surfacing its message."
           },
           {
             "name": "createUrl",

package/docs/public/docs-map.md

@@ -1,7 +1,7 @@
 # Documentation Map
 
 > Auto-generated hierarchical overview of all documentation
-> Last updated: 2026-07-23T18:28:14.969Z
+> Last updated: 2026-08-25T19:01:45.587Z
 
 This file provides a complete map of all available documentation for AI agents and developers.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omnitend/dashboard-for-laravel",
-  "version": "0.38.0",
+  "version": "0.40.0",
   "description": "Vue 3 dashboard components for Laravel with Bootstrap Vue Next",
   "type": "module",
   "main": "./dist/dashboard-for-laravel.umd.cjs",

package/resources/css/theme.scss

@@ -48,7 +48,11 @@ $color-contrast-light: #fff; // Light text color (for dark backgrounds)
 // ----------------------------------------------------------------------------
 
 $font-family-base: "Poppins", sans-serif;
-$font-size-base: 0.875rem; // 14px
+$font-size-base: 1rem; // 16px — the default tier. Legacy omnitend rendered body
+// and table text at 16px; the earlier 0.875rem (14px) shrank every ported page's
+// text ~12% while rem-fixed chrome stayed put, so controls read oversized and
+// text miniaturised (PO20). The small tier is Bootstrap's `.875em` (14px) via
+// `.small`/`<small>`; the extra-small tier is `.75em` (12px, badges/fine print).
 $font-weight-base: 400;
 $line-height-base: 1.5;
 

package/resources/js/components/extended/DXCurrencyInput.vue

@@ -12,9 +12,18 @@
   `min`/`max`/`step` and the displayed text are always in MAJOR units — only
   the model is scaled.
 
+  `append` puts a trailing affix after the input — the unit the price is per
+  ("Pint", "per case", "each"). Without it a consumer needing a unit beside the
+  amount has to hand-roll a `DInputGroup` + bare number input, which puts every
+  foot-gun above straight back. A plain string covers most cases; the `#append`
+  slot takes arbitrary content (a unit picker, a button) and wins over the prop,
+  the same prop-with-slot-fallback shape `DXFieldShell` uses for `hint`.
+
   DXField's `currency` field type renders this leaf; it exists standalone so a
   money input outside a form (an inline table correction, a quick filter)
-  doesn't re-inline the `£`-prefix + toFixed + parse foot-guns.
+  doesn't re-inline the `£`-prefix + toFixed + parse foot-guns. On a DXField,
+  reach the affix through the field's `inputProps` (`{ append: 'per case' }`) —
+  it binds to this prop like any other.
 -->
 <template>
     <DInputGroup>
@@ -30,6 +39,14 @@
             @focus="handleFocus"
             @blur="handleBlur"
         />
+        <!-- Trailing affix. Conditional so an input with no unit renders the
+             exact same markup as before (one prepend, no trailing cell). -->
+        <template v-if="append || $slots.append" #append>
+            <!-- @slot Trailing content after the input — arbitrary markup, overriding the `append` prop. -->
+            <slot name="append">
+                <span class="input-group-text">{{ append }}</span>
+            </slot>
+        </template>
     </DInputGroup>
 </template>
 
@@ -54,6 +71,10 @@ interface Props {
     minorUnits?: boolean;
     /** Input step in MAJOR units (default: one minor unit, e.g. 0.01). */
     step?: string | number;
+    /** Trailing affix shown after the input — the unit the amount is per
+     *  ("Pint", "per case", "each"). Omit for no trailing cell. The `#append`
+     *  slot overrides it when the affix needs to be more than a string. */
+    append?: string;
 }
 
 const props = withDefaults(defineProps<Props>(), {
@@ -62,6 +83,7 @@ const props = withDefaults(defineProps<Props>(), {
     decimals: 2,
     minorUnits: false,
     step: undefined,
+    append: undefined,
 });
 
 const emit = defineEmits<{

package/resources/js/components/extended/DXSwitch.vue

@@ -64,9 +64,10 @@ interface Props {
    */
   onVariant?: "success" | "neutral";
   /**
-   * `"sm"` renders a compact box (~31px vs the default ~35px input height) for
-   * dense rows that repeat the switch per item (a per-line visibility toggle in
-   * a modal). Omit for the standard size, which matches the `.form-control`
+   * `"sm"` renders a compact box (a few px shorter than the default, which
+   * matches the input height) for dense rows that repeat the switch per item (a
+   * per-line visibility toggle in a modal). Omit for the standard size, which
+   * lines the switch up with the `.form-control`
    * height so a switch lines up with inputs beside it.
    */
   size?: "sm";
@@ -140,7 +141,8 @@ defineOptions({
 
 /* Compact size (#… size="sm"): a shorter box for dense rows that repeat the
    switch per item. `min-height: auto` drops the input-height floor so the box
-   shrinks to its padded content (~31px vs ~35px); the smaller font pulls the
+   shrinks to its padded content, a few px under the input-height default;
+   the smaller font pulls the
    label in to match. The fixed-rem toggle itself is unchanged — only the box
    chrome tightens. */
 .dx-switch--sm :deep(.form-check) {

package/resources/js/components/extended/DXTable.vue

@@ -725,8 +725,38 @@ export interface Props<TItem = any> {
      * `null`/`undefined` to proceed with the normal confirm + delete. Lets you
      * short-circuit a doomed delete (e.g. a record with dependents that the
      * server would reject) with an immediate, specific reason.
+     *
+     * AWAITED, so it may return a promise — the same shape as `saveGuard`, so
+     * an `async` guard behaves the way its author expects. A guard that throws
+     * also aborts, surfacing its message.
+     */
+    deleteGuard?: (
+        item: TItem,
+    ) => string | null | undefined | Promise<string | null | undefined>;
+
+    /**
+     * Guard run when the modal's Save/Create is clicked, before the request.
+     * Return a message to abort the save — it is shown immediately (as a toast)
+     * and no request is made; return `null`/`undefined` to proceed. Covers both
+     * the `editUrl` and `createUrl` paths.
+     *
+     * AWAITED (as `deleteGuard` is), so it may return a promise: the case it
+     * exists for is an async control in an `edit-value` slot — an image
+     * upload — that has not finished when Save is clicked. Without the guard the
+     * form submits the previous media map, the save SUCCEEDS, the toast says
+     * saved and the modal closes: the image is lost with no error anywhere,
+     * because every individual step worked. Await the upload here and the save
+     * simply waits for it.
+     *
+     * `item` is the row being edited, `null` in create mode (as in the
+     * `edit-value` slot's binding); `data` is the live form data. Aborting
+     * leaves the modal open with the user's edits intact. A guard that throws
+     * also aborts, surfacing its message.
      */
-    deleteGuard?: (item: TItem) => string | null | undefined;
+    saveGuard?: (
+        item: TItem | null,
+        data: Record<string, any>,
+    ) => string | null | undefined | Promise<string | null | undefined>;
 
     /** API endpoint for creating new items (e.g., "/api/products") — enables "New" button */
     createUrl?: string;
@@ -2182,10 +2212,20 @@ const handleFilterChange = (fieldKey: string, value: string | string[]) => {
             );
         }
 
-        // For API mode, provider will be called automatically by BTable
-        // when we trigger a refresh
+        // API mode: a changed filter is a fresh result set — go back to page 1,
+        // exactly as the Inertia branch above does. Without this, typing a
+        // filter while on page 3 of the unfiltered set requests page 3 of the
+        // NARROWED set, which is usually past its end: the server returns an
+        // empty page and the table shows "no rows match your filters" over a
+        // non-zero total. Same exactly-one-fetch dance as the apiUrl/provider
+        // swap watchers: a page change re-invokes the provider on its own;
+        // only when already on page 1 does refresh() need to force it.
         if (isProviderMode.value && tableRef.value) {
-            refresh();
+            const wasOnFirstPage = apiCurrentPage.value === 1;
+            apiCurrentPage.value = 1;
+            if (wasOnFirstPage) {
+                refresh();
+            }
         }
 
         // Emit filterChange event for backward compatibility

package/resources/js/composables/useResourceEditor.ts

@@ -30,8 +30,15 @@ export interface ResourceEditorProps<T = any> {
     deleteUrl?: string;
     /** `POST` endpoint for creating new items, e.g. `/api/products`. */
     createUrl?: string;
-    /** Guard run before delete — a message short-circuits with a toast. */
-    deleteGuard?: (item: T) => string | null | undefined;
+    /** Guard run before delete — a message short-circuits with a toast. Awaited. */
+    deleteGuard?: (
+        item: T,
+    ) => string | null | undefined | Promise<string | null | undefined>;
+    /** Guard run before save — a message aborts with a toast. Awaited. */
+    saveGuard?: (
+        item: T | null,
+        data: Record<string, any>,
+    ) => string | null | undefined | Promise<string | null | undefined>;
 }
 
 /**
@@ -299,18 +306,96 @@ export function useResourceEditor<T = any>(
         showEditModal.value = true;
     };
 
-    // Save from the edit modal
+    // Save from the edit modal (create or edit).
     const save = async () => {
         if (!editForm.value) return;
 
+        // Don't save — or evaluate the guard — until the full record has loaded
+        // (showUrl). The thin list row is missing fields the form and the guard
+        // may both depend on, so a guard keyed on one of them would see
+        // `undefined` and wave the save through, which is the silent success the
+        // guard exists to prevent. Same rule as `remove`.
+        if (editLoading.value) return;
+
+        // Not re-entrant. The footer button disables itself while
+        // `pendingAction` is set, but DXForm's own submit (Enter in a field)
+        // reaches here directly — and with an AWAITED save guard there is now a
+        // real window in which a second Save would fire a second request.
+        if (pendingAction.value) return;
+
         pendingAction.value = 'save';
         try {
+            if (!(await passesSaveGuard())) return;
             await performSave();
         } finally {
             pendingAction.value = null;
         }
     };
 
+    /*
+     * BOTH guards run through here, which is the point of it: they must not
+     * diverge. Each is AWAITED. The case `saveGuard` exists for is a control
+     * that has not finished yet — an image upload still in flight when Save is
+     * clicked. The form would submit the previous media map, the request would
+     * SUCCEED, the toast would say saved and the modal would close: the image
+     * lost with no error anywhere, because every individual step worked.
+     * `deleteGuard` is awaited on the same path so an `async` guard does what
+     * its author expects — unawaited, its promise is merely truthy, which would
+     * block every delete with an unreadable message.
+     *
+     * Returns true to proceed. Aborting leaves the modal open and the form
+     * untouched — the user's edits are the thing being protected, so nothing is
+     * closed or reset on the way out. A guard that THROWS also aborts: a guard
+     * that could not decide is not permission to proceed.
+     */
+    const passesGuard = async (
+        run: () => string | null | undefined | Promise<string | null | undefined>,
+        title: string,
+        fallbackMessage: string,
+    ): Promise<boolean> => {
+        let message: string | null | undefined;
+        try {
+            message = await run();
+        } catch (error: any) {
+            message = error?.message ?? fallbackMessage;
+        }
+        if (!message) return true;
+
+        createToast?.({
+            title,
+            body: message,
+            variant: 'danger',
+            modelValue: 5000,
+        });
+        return false;
+    };
+
+    const passesSaveGuard = (): Promise<boolean> => {
+        const guard = props.saveGuard;
+        if (!guard) return Promise.resolve(true);
+
+        return passesGuard(
+            () =>
+                guard(
+                    isCreateMode.value ? null : (selectedItem.value as T | null),
+                    editForm.value.data,
+                ),
+            'Cannot save',
+            'Could not save. Please try again.',
+        );
+    };
+
+    const passesDeleteGuard = (): Promise<boolean> => {
+        const guard = props.deleteGuard;
+        if (!guard) return Promise.resolve(true);
+
+        return passesGuard(
+            () => guard(selectedItem.value as T),
+            'Cannot delete',
+            'Could not delete. Please try again.',
+        );
+    };
+
     const performSave = async () => {
         // Create mode: POST to createUrl
         if (isCreateMode.value && props.createUrl) {
@@ -441,27 +526,23 @@ export function useResourceEditor<T = any>(
         // may depend on fields the thin list row doesn't carry.
         if (editLoading.value) return;
 
-        // Delete guard: a non-null message means this item can't be deleted — show
-        // it immediately and skip the confirm and the request entirely.
-        const guardMessage = props.deleteGuard?.(selectedItem.value as T);
-        if (guardMessage) {
-            createToast?.({
-                title: 'Cannot delete',
-                body: guardMessage,
-                variant: 'danger',
-                modelValue: 5000,
-            });
-            return;
-        }
-
-        // Confirm deletion
-        const itemName = (selectedItem.value as any).name || (selectedItem.value as any).title || singularItemName.value;
-        const confirmed = window.confirm(`Are you sure you want to delete "${itemName}"? This action cannot be undone.`);
-
-        if (!confirmed) return;
+        // Not re-entrant, for the same reason as `save`: the guard is awaited,
+        // so a second Delete arriving by a path that doesn't disable the button
+        // would run the guard — and the confirm — a second time.
+        if (pendingAction.value) return;
 
         pendingAction.value = 'delete';
         try {
+            // Delete guard: a non-null message means this item can't be deleted —
+            // show it immediately and skip the confirm and the request entirely.
+            if (!(await passesDeleteGuard())) return;
+
+            // Confirm deletion
+            const itemName = (selectedItem.value as any).name || (selectedItem.value as any).title || singularItemName.value;
+            const confirmed = window.confirm(`Are you sure you want to delete "${itemName}"? This action cannot be undone.`);
+
+            if (!confirmed) return;
+
             const itemId = (selectedItem.value as any).id;
             const url = props.deleteUrl.replace(':id', itemId);
 

package/dist/charts.d.ts

@@ -1,19 +0,0 @@
-/**
- * Chart entry point — `@omnitend/dashboard-for-laravel/charts` (#142).
- *
- * The chart components are the ONLY ones that need `chart.js` / `vue-chartjs`,
- * so they live behind this separate subpath entry. The main entry
- * (`@omnitend/dashboard-for-laravel`) never references the chart libraries, so
- * they are genuinely OPTIONAL peers: a consumer that renders no charts installs
- * neither and their build no longer fails resolving them.
- *
- *   import { DXBarChart } from '@omnitend/dashboard-for-laravel/charts';
- *
- * Chart containers are styled by `.dx-chart` in the main stylesheet
- * (`@omnitend/dashboard-for-laravel/style.css`), which chart consumers already
- * import for the theme and the `--dx-chart-*` palette variables — so this entry
- * ships no CSS of its own.
- */
-export { default as DXBarChart } from "./components/charts/DXBarChart.vue";
-export { default as DXLineChart } from "./components/charts/DXLineChart.vue";
-export { default as DXDoughnutChart } from "./components/charts/DXDoughnutChart.vue";

package/dist/components/base/DAccordion.vue.d.ts

@@ -1,12 +0,0 @@
-declare var __VLS_7: string | number, __VLS_8: any;
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<{}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<{}> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, true, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DAccordionItem.vue.d.ts

@@ -1,12 +0,0 @@
-declare var __VLS_7: string | number, __VLS_8: any;
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<{}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<{}> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, true, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DAlert.vue.d.ts

@@ -1,17 +0,0 @@
-type __VLS_Props = {
-    modelValue?: boolean | number;
-};
-declare var __VLS_7: string | number, __VLS_8: {};
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<__VLS_Props, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<__VLS_Props> & Readonly<{}>, {
-    modelValue: boolean | number;
-}, {}, {}, {}, string, import("vue").ComponentProvideOptions, false, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DAspect.vue.d.ts

@@ -1,12 +0,0 @@
-declare var __VLS_7: string | number, __VLS_8: any;
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<{}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<{}> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, true, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DAutocomplete.vue.d.ts

@@ -1,32 +0,0 @@
-import type { SelectOption } from "bootstrap-vue-next";
-type AutocompleteOptions = readonly (object | string | number | boolean)[];
-type FilterFunction = (options: SelectOption[], search: string) => SelectOption[];
-interface Props {
-    /** Options passed straight through to BAutocomplete (see its `options` prop). */
-    options?: AutocompleteOptions;
-    /**
-     * A custom filter. Composed with `null-option` rather than replaced: when a
-     * null option is present it stays pinned and this runs on the rest.
-     */
-    filterFunction?: FilterFunction;
-    /**
-     * Prepend a pinned, never-filtered, selectable "no selection" row whose value
-     * is `null` (#138). `true` → default label "None"; a string → that label.
-     * Selecting it sets the model to `null` (bvn reads that as no selection, so
-     * the ✕ hides and the placeholder shows). Off by default — unchanged
-     * behaviour. DXTable does NOT use this; it builds its own "All" option.
-     */
-    nullOption?: boolean | string;
-}
-declare var __VLS_6: string | number, __VLS_7: any;
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_6>]?: (props: typeof __VLS_7) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<Props, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<Props> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, false, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DAvatar.vue.d.ts

@@ -1,12 +0,0 @@
-declare var __VLS_7: string | number, __VLS_8: any;
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<{}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<{}> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, true, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DBadge.vue.d.ts

@@ -1,12 +0,0 @@
-declare var __VLS_7: string | number, __VLS_8: {};
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<{}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<{}> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, true, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};

package/dist/components/base/DBreadcrumb.vue.d.ts

@@ -1,12 +0,0 @@
-declare var __VLS_7: string | number, __VLS_8: any;
-type __VLS_Slots = {} & {
-    [K in NonNullable<typeof __VLS_7>]?: (props: typeof __VLS_8) => any;
-};
-declare const __VLS_component: import("vue").DefineComponent<{}, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<{}> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, true, {}, any>;
-declare const _default: __VLS_WithSlots<typeof __VLS_component, __VLS_Slots>;
-export default _default;
-type __VLS_WithSlots<T, S> = T & {
-    new (): {
-        $slots: S;
-    };
-};