@oneflowui/ui 0.8.5 → 0.8.6

package/README.en.md

@@ -154,7 +154,7 @@ When a single page needs two visual contexts at once, prefer the `ThemeScope` co
 
 ```vue
 <script setup lang="ts">
-import { ThemeScope } from '@oneflowui/ui'
+import { DataTable, ThemeScope } from '@oneflowui/ui'
 </script>
 
 <template>
@@ -174,33 +174,37 @@ Supported values currently match the global theme list:
 
 Direct `data-of-theme-scope` usage is still compatible for older code, but new consumers should use `ThemeScope`.
 
-### Component-Level Example
+### ThemeScope Scene Component
 
-A more realistic consumer pattern is to wrap an actual component subtree. The page keeps its global theme, while the local region switches to tokens that fit an ops or command-console context.
+If you want to reuse "local theme + title + description + meta/footer slots" together, use `ThemeScopeScene`. It is a lightweight scene shell component that fits enterprise back offices, ops consoles, and task centers.
 
 ```vue
 <script setup lang="ts">
-import { DataTable, StatisticCard, ThemeScope } from '@oneflowui/ui'
+import { DataTable, ThemeScopeScene } from '@oneflowui/ui'
 </script>
 
 <template>
-  <ThemeScope theme="ops-console" tag="section" class="task-surface">
-    <header class="task-surface__header">
-      <h3>Task Overview</h3>
-      <p>Only this region uses ops-console tokens.</p>
-    </header>
-
-    <div class="task-surface__metrics">
-      <StatisticCard icon="check-circle" :value="18" label="Done" />
-      <StatisticCard icon="clock" :value="6" label="In progress" />
-    </div>
+  <ThemeScopeScene
+    theme="ops-console"
+    tag="section"
+    eyebrow="Enterprise Scene"
+    title="Task Overview"
+    description="This region automatically receives ops-console tokens."
+  >
+    <template #meta>
+      <span class="scene-chip">ThemeScopeScene</span>
+    </template>
 
     <DataTable :rows="rows" :columns="columns" />
-  </ThemeScope>
+
+    <template #footer>
+      <small>footer / notes / actions</small>
+    </template>
+  </ThemeScopeScene>
 </template>
 ```
 
-This is non-breaking: no component API changes are required, and `ThemeScope` only adds a local token boundary on the wrapper.
+`ThemeScopeScene` still reuses `ThemeScope` under the hood, so this is non-breaking. It just packages the common business shell into a reusable component.
 
 ### Virtual List State Cache
 
@@ -224,14 +228,14 @@ const { visibleItems, totalHeight, offsetY } = useVirtualList({
 
 If you need to review the current traceable release materials, start with these docs:
 
-- Current evidence index: [`docs/plans/2026-03-22-release-0.8.5-evidence-index.md`](docs/plans/2026-03-22-release-0.8.5-evidence-index.md)
-- Release proof: [`docs/plans/2026-03-22-release-0.8.5-proof.md`](docs/plans/2026-03-22-release-0.8.5-proof.md)
-- Verification result: [`docs/plans/2026-03-22-release-0.8.5-verification.md`](docs/plans/2026-03-22-release-0.8.5-verification.md)
+- Current evidence index: [`docs/plans/2026-03-22-release-0.8.6-evidence-index.md`](docs/plans/2026-03-22-release-0.8.6-evidence-index.md)
+- Release proof: [`docs/plans/2026-03-22-release-0.8.6-proof.md`](docs/plans/2026-03-22-release-0.8.6-proof.md)
+- Verification result: [`docs/plans/2026-03-22-release-0.8.6-verification.md`](docs/plans/2026-03-22-release-0.8.6-verification.md)
 - Pre-release smoke: [`docs/plans/2026-03-22-oneui-theme-scope-middleware-composer-pre-release-verification.md`](docs/plans/2026-03-22-oneui-theme-scope-middleware-composer-pre-release-verification.md)
 - Package entrypoints verification: [`docs/plans/2026-03-22-oneui-package-entrypoints-verification.md`](docs/plans/2026-03-22-oneui-package-entrypoints-verification.md)
-- Changelog: [`docs/CHANGELOG-v0.8.5.md`](docs/CHANGELOG-v0.8.5.md)
+- Changelog: [`docs/CHANGELOG-v0.8.6.md`](docs/CHANGELOG-v0.8.6.md)
 
-The current public npm version will move to `0.8.5` after this release step, and publish, pack, dry-run, and dual-host smoke checks all have separate evidence.
+The current public npm version should be checked against the latest release proof, and publish, pack, dry-run, and dual-host smoke checks all have separate evidence.
 
 ---
 
@@ -316,6 +320,8 @@ You can compose reusable `DatabaseView` middleware presets for toast, analytics,
 import {
   composeDatabaseViewMiddlewares,
   createDatabaseViewAnalyticsMiddleware,
+  createDatabaseViewPresetBundle,
+  createDatabaseViewPresetMiddleware,
   createDatabaseViewOptimisticMiddleware,
   createDatabaseViewToastMiddleware,
   useDatabaseView,
@@ -344,9 +350,80 @@ const view = useDatabaseView({
 })
 ```
 
+If you prefer a single factory that returns a ready-to-use middleware, use the official preset bundle helper:
+
+```ts
+const presetBundle = createDatabaseViewPresetBundle({
+  toast: {
+    onSuccess: (message) => toast.success(message),
+    onError: (message) => toast.error(message),
+  },
+  analytics: {
+    onEvent: (event) => console.log('[db-view]', event.phase, event.action),
+  },
+  optimistic: {
+    apply: ({ payload }) => updateLocalRecord(payload),
+    revert: ({ payload }) => revertLocalRecord(payload),
+  },
+})
+
+const view = useDatabaseView({
+  tableId: 'tbl-1',
+  actions: {
+    middleware: presetBundle.middleware,
+    onCellEdit: saveCellEdit,
+  },
+})
+```
+
+`createDatabaseViewPresetMiddleware` is the one-liner version when you only need the final middleware object:
+
+```ts
+const middleware = createDatabaseViewPresetMiddleware({
+  toast: {
+    onSuccess: (message) => toast.success(message),
+    onError: (message) => toast.error(message),
+  },
+  analytics: {
+    onEvent: (event) => console.log('[db-view]', event.phase, event.action),
+  },
+  optimistic: {
+    apply: ({ payload }) => updateLocalRecord(payload),
+    revert: ({ payload }) => revertLocalRecord(payload),
+  },
+})
+```
+
+### ThemeScope Scene Template
+
+If you want to evolve `ThemeScope` from a local wrapper into a business scene template, use it as the page shell that organizes the region structure. This fits enterprise dashboards, ops consoles, and task boards: the outer shell fixes the visual context while the inner area hosts cards, tables, metrics, and side notes.
+
+```vue
+<script setup lang="ts">
+import { ThemeScope } from '@oneflowui/ui'
+</script>
+
+<template>
+  <ThemeScope theme="ops-console" tag="section" class="enterprise-scene">
+    <header class="enterprise-scene__header">
+      <h3>Enterprise Scene</h3>
+      <p>Theme, layout, and business content are reused together as one template.</p>
+    </header>
+
+    <div class="enterprise-scene__body">
+      <div class="enterprise-scene__summary">...</div>
+      <DataTable :rows="rows" :columns="columns" />
+    </div>
+  </ThemeScope>
+</template>
+```
+
+The repository's `src/dev/examples/database/DatabaseEnterpriseDemo.vue` is the dev/examples-level reference for this kind of scene template. It shows the "ThemeScopeScene + DatabaseView + middleware" composition pattern that you can copy into your own project and turn into a real enterprise page.
+
 ### Dev Examples / Enterprise Demo
 
-`DatabaseEnterpriseDemo` is a dev/examples-level consumption pattern used to show a more complete enterprise-style page composition. It is documentation and development sample material, not an npm-exported component, and it does not change the public export surface of `@oneflowui/ui`.
+`src/dev/examples/database/DatabaseEnterpriseDemo.vue` is a dev/examples-level consumption pattern used to show a more complete enterprise-style page composition. It is documentation and development sample material, not an npm-exported component, and it does not change the public export surface of `@oneflowui/ui`.
+The repository also ships `src/dev/examples/database/DatabasePresetDemo.vue` as a shorter official preset-bundle example, focused on direct `createDatabaseViewPresetBundle` / `actions.middleware` consumption.
 
 If your business app needs something similar, copy the composition idea from the example and wire it to your own data source and action contract instead of depending on a separate production export.
 

package/README.md

@@ -145,7 +145,7 @@ import '@oneflowui/ui/theme'
 
 ```vue
 <script setup lang="ts">
-import { ThemeScope } from '@oneflowui/ui'
+import { DataTable, ThemeScope } from '@oneflowui/ui'
 </script>
 
 <template>
@@ -165,33 +165,37 @@ import { ThemeScope } from '@oneflowui/ui'
 
 老代码里直接手写的 `data-of-theme-scope` 仍然兼容，但新代码优先使用组件入口。
 
-### 组件级示例
+### ThemeScope 场景组件
 
-更贴近业务消费的写法，是把一个组件子树直接包进 `ThemeScope`。外层页面继续沿用全局主题，局部区域则切到适合命令台或运营视角的 token。
+如果你想把“局部主题 + 标题 + 说明 + meta/footer 插槽”一起复用，直接用 `ThemeScopeScene`。它是一个轻量的场景壳层组件，适合企业后台、运营控制台、任务中心这类页面。
 
 ```vue
 <script setup lang="ts">
-import { DataTable, StatisticCard, ThemeScope } from '@oneflowui/ui'
+import { DataTable, ThemeScopeScene } from '@oneflowui/ui'
 </script>
 
 <template>
-  <ThemeScope theme="ops-console" tag="section" class="task-surface">
-    <header class="task-surface__header">
-      <h3>任务总览</h3>
-      <p>仅这块区域使用 ops-console token。</p>
-    </header>
-
-    <div class="task-surface__metrics">
-      <StatisticCard icon="check-circle" :value="18" label="已完成" />
-      <StatisticCard icon="clock" :value="6" label="进行中" />
-    </div>
+  <ThemeScopeScene
+    theme="ops-console"
+    tag="section"
+    eyebrow="Enterprise Scene"
+    title="任务总览"
+    description="这个区域会自动获得 ops-console token。"
+  >
+    <template #meta>
+      <span class="scene-chip">ThemeScopeScene</span>
+    </template>
 
     <DataTable :rows="rows" :columns="columns" />
-  </ThemeScope>
+
+    <template #footer>
+      <small>footer / notes / actions</small>
+    </template>
+  </ThemeScopeScene>
 </template>
 ```
 
-这是一种非 breaking 的增强：组件 API 不需要变，`ThemeScope` 只是在局部 wrapper 上增加一层 token 作用域。
+`ThemeScopeScene` 内部继续复用 `ThemeScope` 的 token 作用域，所以它仍然是 non-breaking 的增强，只是把常见业务壳层收成了一个可复用组件。
 
 ### 虚拟列表状态缓存
 
@@ -215,14 +219,14 @@ const { visibleItems, totalHeight, offsetY } = useVirtualList({
 
 如果你需要核对当前可追溯的发布材料，优先看这几份文档：
 
-- 当前版本证据索引：[`docs/plans/2026-03-22-release-0.8.5-evidence-index.md`](docs/plans/2026-03-22-release-0.8.5-evidence-index.md)
-- 发布 proof：[`docs/plans/2026-03-22-release-0.8.5-proof.md`](docs/plans/2026-03-22-release-0.8.5-proof.md)
-- 验收结果：[`docs/plans/2026-03-22-release-0.8.5-verification.md`](docs/plans/2026-03-22-release-0.8.5-verification.md)
+- 当前版本证据索引：[`docs/plans/2026-03-22-release-0.8.6-evidence-index.md`](docs/plans/2026-03-22-release-0.8.6-evidence-index.md)
+- 发布 proof：[`docs/plans/2026-03-22-release-0.8.6-proof.md`](docs/plans/2026-03-22-release-0.8.6-proof.md)
+- 验收结果：[`docs/plans/2026-03-22-release-0.8.6-verification.md`](docs/plans/2026-03-22-release-0.8.6-verification.md)
 - 预发布验证：[`docs/plans/2026-03-22-oneui-theme-scope-middleware-composer-pre-release-verification.md`](docs/plans/2026-03-22-oneui-theme-scope-middleware-composer-pre-release-verification.md)
 - 子路径入口治理：[`docs/plans/2026-03-22-oneui-package-entrypoints-verification.md`](docs/plans/2026-03-22-oneui-package-entrypoints-verification.md)
-- 版本日志：[`docs/CHANGELOG-v0.8.5.md`](docs/CHANGELOG-v0.8.5.md)
+- 版本日志：[`docs/CHANGELOG-v0.8.6.md`](docs/CHANGELOG-v0.8.6.md)
 
-当前 npm 公开版本会在本轮发版完成后更新到 `0.8.5`，对应的发布、pack、dry-run 和双宿主 smoke 都有独立留痕。
+当前 npm 公开版本以最新 release proof 为准，对应的发布、pack、dry-run 和双宿主 smoke 都有独立留痕。
 
 ---
 
@@ -287,6 +291,8 @@ type DatabaseViewActions = {
 import {
   composeDatabaseViewMiddlewares,
   createDatabaseViewAnalyticsMiddleware,
+  createDatabaseViewPresetBundle,
+  createDatabaseViewPresetMiddleware,
   createDatabaseViewOptimisticMiddleware,
   createDatabaseViewToastMiddleware,
   useDatabaseView,
@@ -315,9 +321,80 @@ const view = useDatabaseView({
 })
 ```
 
+如果你更想要一个“一键拿到可直接消费的 middleware”的入口，可以优先用官方 preset 工厂：
+
+```ts
+const presetBundle = createDatabaseViewPresetBundle({
+  toast: {
+    onSuccess: (message) => toast.success(message),
+    onError: (message) => toast.error(message),
+  },
+  analytics: {
+    onEvent: (event) => console.log('[db-view]', event.phase, event.action),
+  },
+  optimistic: {
+    apply: ({ payload }) => updateLocalRecord(payload),
+    revert: ({ payload }) => revertLocalRecord(payload),
+  },
+})
+
+const view = useDatabaseView({
+  tableId: 'tbl-1',
+  actions: {
+    middleware: presetBundle.middleware,
+    onCellEdit: saveCellEdit,
+  },
+})
+```
+
+`createDatabaseViewPresetBundle` 会把常用 preset 先组装好，再暴露给业务方按需复用；`createDatabaseViewPresetMiddleware` 则适合直接塞进 `actions.middleware`，用于最小接入，例如：
+
+```ts
+const middleware = createDatabaseViewPresetMiddleware({
+  toast: {
+    onSuccess: (message) => toast.success(message),
+    onError: (message) => toast.error(message),
+  },
+  analytics: {
+    onEvent: (event) => console.log('[db-view]', event.phase, event.action),
+  },
+  optimistic: {
+    apply: ({ payload }) => updateLocalRecord(payload),
+    revert: ({ payload }) => revertLocalRecord(payload),
+  },
+})
+```
+
+### ThemeScope 场景模板
+
+如果你想把 `ThemeScope` 从“局部 wrapper”升级成“业务场景模板”，可以直接把它当成页面壳层来组织区域结构。这个模板适合企业后台、运营控制台、任务看板这类页面：外层固定视觉语境，内层再放业务卡片、数据表、统计块和侧边说明。
+
+```vue
+<script setup lang="ts">
+import { ThemeScope } from '@oneflowui/ui'
+</script>
+
+<template>
+  <ThemeScope theme="ops-console" tag="section" class="enterprise-scene">
+    <header class="enterprise-scene__header">
+      <h3>Enterprise Scene</h3>
+      <p>主题、布局和业务内容一起作为模板复用。</p>
+    </header>
+
+    <div class="enterprise-scene__body">
+      <div class="enterprise-scene__summary">...</div>
+      <DataTable :rows="rows" :columns="columns" />
+    </div>
+  </ThemeScope>
+</template>
+```
+
+仓库里的 `src/dev/examples/database/DatabaseEnterpriseDemo.vue` 就是这一类场景组件的 dev/examples 级参考实现。它展示的是“ThemeScopeScene + DatabaseView + middleware”的组合方式，便于复制到自家项目里改造成真正的企业页。
+
 ### Dev Examples / Enterprise Demo
 
-`DatabaseEnterpriseDemo` 是 dev/examples 级的消费范式，用来展示更完整的企业版页面组合方式。它属于开发示例和文档参考，不是 npm 包对外导出的组件，不会改变 `@oneflowui/ui` 的公开导出面。
+`src/dev/examples/database/DatabaseEnterpriseDemo.vue` 是 dev/examples 级的消费范式，用来展示更完整的企业版页面组合方式。它属于开发示例和文档参考，不是 npm 包对外导出的组件，不会改变 `@oneflowui/ui` 的公开导出面。
+仓库同时提供 `src/dev/examples/database/DatabasePresetDemo.vue` 作为更短的 preset bundle 官方示例，重点展示 `createDatabaseViewPresetBundle` / `actions.middleware` 的直接消费方式。
 
 如果你在业务工程里需要类似的页面，建议直接复制示例里的组合思路，再按自己的数据源和动作契约接入，而不是依赖一个额外的生产级导出入口。
 

package/dist/components/common/ThemeScopeScene.vue.d.ts

@@ -0,0 +1,31 @@
+type ThemeScopeTheme = "neutral" | "ops-console";
+type __VLS_Props = {
+    theme: ThemeScopeTheme;
+    title: string;
+    description?: string;
+    eyebrow?: string;
+    tag?: string;
+};
+declare function __VLS_template(): {
+    attrs: Partial<{}>;
+    slots: {
+        meta?(_: {}): any;
+        default?(_: {}): any;
+        footer?(_: {}): any;
+    };
+    refs: {};
+    rootEl: any;
+};
+type __VLS_TemplateResult = ReturnType<typeof __VLS_template>;
+declare const __VLS_component: import('vue').DefineComponent<__VLS_Props, {}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {}, string, import('vue').PublicProps, Readonly<__VLS_Props> & Readonly<{}>, {
+    description: string;
+    tag: string;
+    eyebrow: string;
+}, {}, {}, {}, string, import('vue').ComponentProvideOptions, false, {}, any>;
+declare const _default: __VLS_WithTemplateSlots<typeof __VLS_component, __VLS_TemplateResult["slots"]>;
+export default _default;
+type __VLS_WithTemplateSlots<T, S> = T & {
+    new (): {
+        $slots: S;
+    };
+};

package/dist/components/common/ThemeScopeScene.vue.js

@@ -0,0 +1,7 @@
+import o from "./ThemeScopeScene.vue2.js";
+/* empty css                     */
+import e from "../../_virtual/_plugin-vue_export-helper.js";
+const m = /* @__PURE__ */ e(o, [["__scopeId", "data-v-60160caa"]]);
+export {
+  m as default
+};

package/dist/components/common/ThemeScopeScene.vue2.js

@@ -0,0 +1,56 @@
+import { defineComponent as i, openBlock as o, createBlock as d, withCtx as m, createElementVNode as s, createElementBlock as c, toDisplayString as r, createCommentVNode as n, renderSlot as a } from "vue";
+import l from "./ThemeScope.vue.js";
+const h = { class: "of-theme-scope-scene__header" }, p = { class: "of-theme-scope-scene__heading" }, f = {
+  key: 0,
+  class: "of-theme-scope-scene__eyebrow"
+}, u = { class: "of-theme-scope-scene__title" }, y = {
+  key: 1,
+  class: "of-theme-scope-scene__description"
+}, k = {
+  key: 0,
+  class: "of-theme-scope-scene__meta"
+}, g = { class: "of-theme-scope-scene__body" }, v = {
+  key: 0,
+  class: "of-theme-scope-scene__footer"
+}, w = /* @__PURE__ */ i({
+  name: "ThemeScopeScene",
+  __name: "ThemeScopeScene",
+  props: {
+    theme: {},
+    title: {},
+    description: { default: "" },
+    eyebrow: { default: "" },
+    tag: { default: "section" }
+  },
+  setup(_) {
+    const e = _;
+    return (t, S) => (o(), d(l, {
+      theme: e.theme,
+      tag: e.tag,
+      class: "of-theme-scope-scene"
+    }, {
+      default: m(() => [
+        s("header", h, [
+          s("div", p, [
+            e.eyebrow ? (o(), c("p", f, r(e.eyebrow), 1)) : n("", !0),
+            s("h3", u, r(e.title), 1),
+            e.description ? (o(), c("p", y, r(e.description), 1)) : n("", !0)
+          ]),
+          t.$slots.meta ? (o(), c("div", k, [
+            a(t.$slots, "meta", {}, void 0, !0)
+          ])) : n("", !0)
+        ]),
+        s("div", g, [
+          a(t.$slots, "default", {}, void 0, !0)
+        ]),
+        t.$slots.footer ? (o(), c("footer", v, [
+          a(t.$slots, "footer", {}, void 0, !0)
+        ])) : n("", !0)
+      ]),
+      _: 3
+    }, 8, ["theme", "tag"]));
+  }
+});
+export {
+  w as default
+};

package/dist/components/common/index.d.ts

@@ -1 +1,2 @@
 export { default as ThemeScope } from './ThemeScope.vue';
+export { default as ThemeScopeScene } from './ThemeScopeScene.vue';

package/dist/composables/index.d.ts

@@ -45,9 +45,9 @@ export type { SupabaseQueryBuilder, SupabaseFilterBuilder, UseSupabaseProviderOp
 export { useViewPersistence, createLocalStorageBackend, createSupabaseBackend, } from './useViewPersistence';
 export type { ViewStorageBackend, SupabaseViewBackendOptions, UseViewPersistenceOptions, } from './useViewPersistence';
 export { useDatabaseView } from './useDatabaseView';
-export { composeDatabaseViewMiddlewares, createDatabaseViewAnalyticsMiddleware, createDatabaseViewToastMiddleware, createDatabaseViewOptimisticMiddleware, } from './useDatabaseViewMiddleware';
+export { composeDatabaseViewMiddlewares, createDatabaseViewAnalyticsMiddleware, createDatabaseViewPresetInputs, createDatabaseViewPresetBundle, createDatabaseViewPresetMiddleware, createDatabaseViewToastMiddleware, createDatabaseViewOptimisticMiddleware, } from './useDatabaseViewMiddleware';
 export type { DatabaseViewActionContext, DatabaseViewActionErrorContext, DatabaseViewActionMiddleware, DatabaseViewActionMiddlewareList, DatabaseViewMode, DatabaseViewFetchParams, DatabaseViewFetchResult, DatabaseViewProvider, DatabaseSchemaEvent, DatabaseViewActions, DatabaseViewDetailOptions, DatabaseViewNavigationOptions, UseDatabaseViewOptions, UseDatabaseViewResult, } from './useDatabaseView';
-export type { DatabaseViewAnalyticsEvent, DatabaseViewAnalyticsMiddlewareOptions, DatabaseViewMiddlewareInput, DatabaseViewOptimisticMiddlewareOptions, DatabaseViewToastMiddlewareOptions, } from './useDatabaseViewMiddleware';
+export type { DatabaseViewAnalyticsEvent, DatabaseViewAnalyticsMiddlewareOptions, DatabaseViewPresetMiddlewareOptions, DatabaseViewPresetBundle, DatabaseViewPresetBundleOptions, DatabaseViewMiddlewareInput, DatabaseViewOptimisticMiddlewareOptions, DatabaseViewToastMiddlewareOptions, } from './useDatabaseViewMiddleware';
 export { useDatabaseViewport, useDatabaseWorkspaceState } from './useDatabaseWorkspace';
 export { useSearch } from './useSearch';
 export type { UseSearchOptions, SearchHighlight } from './useSearch';

package/dist/composables/useDatabaseViewMiddleware.d.ts

@@ -26,8 +26,31 @@ export interface DatabaseViewOptimisticMiddlewareOptions<T extends DataRecord =
     revert: (context: DatabaseViewActionErrorContext<T>) => void | Promise<void>;
     shouldApply?: (context: DatabaseViewActionContext<T>) => boolean;
 }
+export interface DatabaseViewPresetMiddlewareOptions<T extends DataRecord = DataRecord> {
+    toast?: DatabaseViewToastMiddlewareOptions<T> | false;
+    analytics?: DatabaseViewAnalyticsMiddlewareOptions<T> | false;
+    optimistic?: DatabaseViewOptimisticMiddlewareOptions<T> | false;
+    extra?: readonly DatabaseViewMiddlewareInput<T>[];
+}
+export interface DatabaseViewPresetBundleOptions<T extends DataRecord = DataRecord> {
+    middlewares?: DatabaseViewMiddlewareInput<T>[];
+    toast?: DatabaseViewToastMiddlewareOptions<T>;
+    analytics?: DatabaseViewAnalyticsMiddlewareOptions<T>;
+    optimistic?: DatabaseViewOptimisticMiddlewareOptions<T>;
+}
+export interface DatabaseViewPresetBundle<T extends DataRecord = DataRecord> {
+    middleware: DatabaseViewActionMiddleware<T>;
+    presets: {
+        toast?: DatabaseViewActionMiddleware<T>;
+        analytics?: DatabaseViewActionMiddleware<T>;
+        optimistic?: DatabaseViewActionMiddleware<T>;
+    };
+}
 export type DatabaseViewMiddlewareInput<T extends DataRecord = DataRecord> = DatabaseViewActionMiddleware<T> | readonly DatabaseViewMiddlewareInput<T>[] | null | undefined;
 export declare function createDatabaseViewToastMiddleware<T extends DataRecord = DataRecord>(options?: DatabaseViewToastMiddlewareOptions<T>): DatabaseViewActionMiddleware<T>;
 export declare function createDatabaseViewAnalyticsMiddleware<T extends DataRecord = DataRecord>(options: DatabaseViewAnalyticsMiddlewareOptions<T>): DatabaseViewActionMiddleware<T>;
 export declare function createDatabaseViewOptimisticMiddleware<T extends DataRecord = DataRecord>(options: DatabaseViewOptimisticMiddlewareOptions<T>): DatabaseViewActionMiddleware<T>;
+export declare function createDatabaseViewPresetBundle<T extends DataRecord = DataRecord>(options?: DatabaseViewPresetBundleOptions<T>): DatabaseViewPresetBundle<T>;
 export declare function composeDatabaseViewMiddlewares<T extends DataRecord = DataRecord>(...inputs: DatabaseViewMiddlewareInput<T>[]): DatabaseViewActionMiddleware<T>;
+export declare function createDatabaseViewPresetInputs<T extends DataRecord = DataRecord>(options: DatabaseViewPresetMiddlewareOptions<T>): DatabaseViewMiddlewareInput<T>[];
+export declare function createDatabaseViewPresetMiddleware<T extends DataRecord = DataRecord>(options?: DatabaseViewPresetBundleOptions<T>): DatabaseViewActionMiddleware<T>;