rhjy-ui 0.2.6 → 0.2.8

package/README.md

@@ -1,261 +1,321 @@
-# rhjy-ui
-
-`rhjy-ui` is a Vue 3 and Element Plus business UI component library. The first release contains a configurable data-center suite for displaying asynchronous import, export, generation and other background tasks.
-
-## Install
-
-```bash
-pnpm add rhjy-ui vue element-plus @element-plus/icons-vue
-```
-
-Import the package stylesheet once in the application entrypoint:
-
-```ts
-import 'rhjy-ui/style.css'
-```
-
-## Responsive Info Grid
-
-Responsive Info Grid arranges title-content pairs in a configurable grid and switches column counts at the 1200px and 768px breakpoints.
-
-```vue
-<script setup lang="ts">
-import {
-  RhResponsiveInfoGrid,
-  RhResponsiveInfoGridItem,
-} from 'rhjy-ui'
-</script>
-
-<template>
-  <RhResponsiveInfoGrid>
-    <RhResponsiveInfoGridItem title="Project: " content="Smart Campus" />
-    <RhResponsiveInfoGridItem title="Owner: " content="Operations Team" />
-    <RhResponsiveInfoGridItem title="Devices: " :content="128" />
-    <RhResponsiveInfoGridItem title="Summary: " content="All systems operational" :span="2" />
-  </RhResponsiveInfoGrid>
-</template>
-```
-
-See the [Responsive Info Grid component README](https://unpkg.com/rhjy-ui@0.2.2/src/responsive-info-grid/README.md) for subpath imports, the complete props and slots reference, responsive behavior, and more examples.
-
-## Data center panel
-
-`rhjy-ui` never receives an API URL. Each application supplies a `loadTasks` function and converts its own response into the standard task model.
-
-```vue
-<script setup lang="ts">
-import { RhDataCenter } from 'rhjy-ui'
-import type {
-  RhDataCenterCategory,
-  RhDataCenterLoadTasks,
-} from 'rhjy-ui/data-center'
-
-const categories: RhDataCenterCategory[] = [
-  { key: 'all', label: '全部任务' },
-  { key: 'generate', label: '数据生成' },
-  { key: 'import', label: '数据导入' },
-  { key: 'export', label: '数据导出' },
-]
-
-const loadTasks: RhDataCenterLoadTasks = async ({ category }) => {
-  const response = await requestTaskList({
-    taskType: category.key === 'all' ? undefined : category.key,
-  })
-
-  return {
-    items: response.list,
-    total: response.total,
-  }
-}
+# rhjy-ui
+
+`rhjy-ui` is a Vue 3 and Element Plus business UI component library. The first release contains a configurable data-center suite for displaying asynchronous import, export, generation and other background tasks.
+
+## Install
+
+```bash
+pnpm add rhjy-ui vue element-plus @element-plus/icons-vue
+```
+
+Import the package stylesheet once in the application entrypoint:
+
+```ts
+import 'rhjy-ui/style.css'
+```
+
+## Responsive Info Grid
+
+Responsive Info Grid arranges title-content pairs in a configurable grid and switches column counts at the 1200px and 768px breakpoints.
+
+```vue
+<script setup lang="ts">
+import {
+  RhResponsiveInfoGrid,
+  RhResponsiveInfoGridItem,
+} from 'rhjy-ui'
+</script>
+
+<template>
+  <RhResponsiveInfoGrid>
+    <RhResponsiveInfoGridItem title="Project: " content="Smart Campus" />
+    <RhResponsiveInfoGridItem title="Owner: " content="Operations Team" />
+    <RhResponsiveInfoGridItem title="Devices: " :content="128" />
+    <RhResponsiveInfoGridItem title="Summary: " content="All systems operational" :span="2" />
+  </RhResponsiveInfoGrid>
+</template>
+```
+
+See the [Responsive Info Grid component README](https://unpkg.com/rhjy-ui@0.2.2/src/responsive-info-grid/README.md) for subpath imports, the complete props and slots reference, responsive behavior, and more examples.
+
+## Data center panel
+
+`rhjy-ui` never receives an API URL. Each application supplies a `loadTasks` function and converts its own response into the standard task model.
+
+```vue
+<script setup lang="ts">
+import { RhDataCenter } from 'rhjy-ui'
+import type {
+  RhDataCenterCategory,
+  RhDataCenterLoadTasks,
+} from 'rhjy-ui/data-center'
+
+const categories: RhDataCenterCategory[] = [
+  { key: 'all', label: '全部任务' },
+  { key: 'generate', label: '数据生成' },
+  { key: 'import', label: '数据导入' },
+  { key: 'export', label: '数据导出' },
+]
+
+const loadTasks: RhDataCenterLoadTasks = async ({ category }) => {
+  const response = await requestTaskList({
+    taskType: category.key === 'all' ? undefined : category.key,
+  })
+
+  return {
+    items: response.list,
+    total: response.total,
+  }
+}
+
+const handleTaskAction = ({ action, task }) => {
+  if (action === 'download') {
+    window.open(task.raw.fileUrl)
+  }
+}
+</script>
+
+<template>
+  <RhDataCenter
+    :categories="categories"
+    :load-tasks="loadTasks"
+    sidebar-width="160px"
+    @task-action="handleTaskAction"
+  />
+</template>
+```
+
+The “全部任务” rule is application-owned. It may omit `taskType`, pass a fixed value, or combine multiple requests without changing the component.
+
+### Reuse the business adapter
+
+When multiple applications use the same data-center protocol, use `createRhDataCenterAdapter` to share response conversion, status messages, sorting, counts, and default download actions. The application still injects its own API functions; the package never receives an API URL.
+
+```ts
+import {
+  createRhDataCenterAdapter,
+  type RhDataCenterCategory,
+} from 'rhjy-ui/data-center'
+import { clickDownloadBtByTaskId, getMyTaskList } from '@/services/dataCenter'
+
+const categories: RhDataCenterCategory[] = [
+  { key: 'all', label: '全部任务', query: { taskType: 0 } },
+  { key: 2, label: '数据导入', query: { taskType: 2 } },
+  { key: 3, label: '数据导出', query: { taskType: 3 } },
+]
+
+const { loadTasks, handleTaskAction } = createRhDataCenterAdapter({
+  api: {
+    getTaskList: getMyTaskList,
+    downloadTask: ({ taskId }) => clickDownloadBtByTaskId({ taskId }),
+  },
+  categories,
+  taskKind: { import: [2], export: [3] },
+  completedDownloadKinds: ['other'],
+})
+```
+
+The adapter provides default task actions for completed exports, import failure records, and failed tasks. Use `completedDownloadKinds` when another task kind should show a file download action after completion and its raw task contains `fileUrl`. Use `parseResponse` when the application response wrapper or success rule differs. Use `mapTask` or `resolveActions` for an application-specific field or operation without changing the shared adapter. `RhDataCenter` remains responsible for polling; the adapter handles one query and one task action at a time.
+
+Use `sidebar-width` with a number or CSS size string to adjust the data type panel width. Its default value is `124px`.
+
+Category counts are optional and application-owned. Set `show-category-count` to `false` to hide every category count, or pass `category-counts` to display values before individual categories are loaded:
+
+```vue
+<RhDataCenter
+  :categories="categories"
+  :load-tasks="loadTasks"
+  :show-category-count="true"
+  :category-counts="{ all: 20, generate: 8, import: 4, export: 8 }"
+/>
+```
+
+When counts are enabled, the component uses `categoryCounts`, then a loaded result's `counts`, and finally the category result's `total`.
+
+When the backend provides a separate count endpoint, configure it on the shared adapter. The count request runs in parallel with each task-list refresh, so the sidebar stays synchronized with polling without moving API details into `RhDataCenter`:
+
+```ts
+const { loadTasks, handleTaskAction } = createRhDataCenterAdapter<
+  RawTask,
+  TaskQuery,
+  TaskListResponse,
+  TaskCountResponse
+>({
+  api: {
+    getTaskList: requestTaskList,
+    getTaskCounts: () => requestTaskCounts({ taskType: 0 }),
+  },
+  categories,
+  parseResponse: (response) => response.data.list,
+  parseCounts: (response) => ({
+    all: response.data.totalTaskCount,
+    import: response.data.taskCountList.find((item) => item.taskType === 2)?.taskCount ?? 0,
+  }),
+})
+```
+
+`parseCounts` converts the shared backend response into category keys. If the count request or parser fails, the adapter keeps the task list available and falls back to `resolveCounts` or the loaded result totals.
+
+Task tags read `raw.taskTypeName` by default. When an API uses another field name, pass `task-tag-field` without changing the task adapter:
+
+```vue
+<RhDataCenter
+  :categories="categories"
+  :load-tasks="loadTasks"
+  task-tag-field="taskTypeName"
+/>
+```
+
+## Task tip flow
+
+Use `useRhDataCenter` after a page successfully creates a background task:
+
+```vue
+<script setup lang="ts">
+import { RhDataCenterTip, useRhDataCenter } from 'rhjy-ui'
+
+const { tipVisible, tipConfig, showTip } = useRhDataCenter()
+
+const startExport = async () => {
+  const result = await createExportTask()
+  showTip({
+    type: 'export',
+    minutes: Number(result.minutes),
+    title: '导出文件生成中，大概需要',
+    content: '现在你可关闭弹框，去做其他事情了。',
+  })
+}
+</script>
+
+<template>
+  <RhDataCenterTip v-model="tipVisible" v-bind="tipConfig" />
+</template>
+```
+
+`RhDataCenterTip` 默认使用简化引导动画；需要使用带数据处理中心图片、手势和方向切换的引导时，可传入 `guideVariant="normal"` 或 `guideVariant="super"`。
+
+## Standard task model
+
+The adapter returns `id`, `categoryKey`, `title`, `createdAt`, `progress`, and one of `waiting`, `processing`, `success`, or `failed`. Optional `tag`, `message`, `actions`, and `raw` provide display and application action context.
+
+For completed tasks with rejected records, pass the normalized `failCount` field. The task item keeps the completed progress bar, shows `失败记录（xx条）` in red, and hides the normal completion message when the count is zero. The application still supplies the failure-record action and handles its download event.
+
+For processing tasks, pass `taskSeconds` to show `总时长约X分XX秒` instead of the default processing message. If `taskSeconds` is omitted, the provided `message` is displayed.
+
+## Styling
 
-const handleTaskAction = ({ action, task }) => {
-  if (action === 'download') {
-    window.open(task.raw.fileUrl)
-  }
+Override CSS variables at the application root when needed:
+
+```css
+:root {
+  --rh-ui-data-center-primary: #00828a;
+  --rh-ui-data-center-panel-width: 606px;
+  --rh-ui-data-center-panel-height: 500px;
 }
-</script>
-
-<template>
-  <RhDataCenter
-    :categories="categories"
-    :load-tasks="loadTasks"
-    sidebar-width="160px"
-    @task-action="handleTaskAction"
-  />
-</template>
-```
-
-The “全部任务” rule is application-owned. It may omit `taskType`, pass a fixed value, or combine multiple requests without changing the component.
-
-### Reuse the business adapter
-
-When multiple applications use the same data-center protocol, use `createRhDataCenterAdapter` to share response conversion, status messages, sorting, counts, and default download actions. The application still injects its own API functions; the package never receives an API URL.
-
-```ts
-import {
-  createRhDataCenterAdapter,
-  type RhDataCenterCategory,
-} from 'rhjy-ui/data-center'
-import { clickDownloadBtByTaskId, getMyTaskList } from '@/services/dataCenter'
-
-const categories: RhDataCenterCategory[] = [
-  { key: 'all', label: '全部任务', query: { taskType: 0 } },
-  { key: 2, label: '数据导入', query: { taskType: 2 } },
-  { key: 3, label: '数据导出', query: { taskType: 3 } },
-]
-
-const { loadTasks, handleTaskAction } = createRhDataCenterAdapter({
-  api: {
-    getTaskList: getMyTaskList,
-    downloadTask: ({ taskId }) => clickDownloadBtByTaskId({ taskId }),
-  },
-  categories,
-  taskKind: { import: [2], export: [3] },
-})
 ```
 
-Use `parseResponse` when the application response wrapper or success rule differs. Use `mapTask` or `resolveActions` for an application-specific field or operation without changing the shared adapter. `RhDataCenter` remains responsible for polling; the adapter handles one query and one task action at a time.
-
-Use `sidebar-width` with a number or CSS size string to adjust the data type panel width. Its default value is `124px`.
-
-Category counts are optional and application-owned. Set `show-category-count` to `false` to hide every category count, or pass `category-counts` to display values before individual categories are loaded:
+For business-specific styles, pass `custom-class`. The class is applied to both the trigger and the Teleport panel container, so it can scope overrides for the panel rendered under `body`:
 
 ```vue
 <RhDataCenter
+  class="after-school-data-center"
+  custom-class="restaurant-data-center"
   :categories="categories"
   :load-tasks="loadTasks"
   :show-category-count="true"
-  :category-counts="{ all: 20, generate: 8, import: 4, export: 8 }"
+  :category-counts="categoryCounts"
 />
 ```
 
-When counts are enabled, the component uses `categoryCounts`, then a loaded result's `counts`, and finally the category result's `total`.
-
-When the backend provides a separate count endpoint, configure it on the shared adapter. The count request runs in parallel with each task-list refresh, so the sidebar stays synchronized with polling without moving API details into `RhDataCenter`:
+```scss
+.restaurant-data-center {
+  .rh-data-center-panel__category.is-active {
+    color: #409eff;
+  }
 
-```ts
-const { loadTasks, handleTaskAction } = createRhDataCenterAdapter<
-  RawTask,
-  TaskQuery,
-  TaskListResponse,
-  TaskCountResponse
->({
-  api: {
-    getTaskList: requestTaskList,
-    getTaskCounts: () => requestTaskCounts({ taskType: 0 }),
-  },
-  categories,
-  parseResponse: (response) => response.data.list,
-  parseCounts: (response) => ({
-    all: response.data.totalTaskCount,
-    import: response.data.taskCountList.find((item) => item.taskType === 2)?.taskCount ?? 0,
-  }),
-})
+  .rh-data-center-panel__progressBar {
+    background: #409eff;
+  }
+}
 ```
 
-`parseCounts` converts the shared backend response into category keys. If the count request or parser fails, the adapter keeps the task list available and falls back to `resolveCounts` or the loaded result totals.
-
-Task tags read `raw.taskTypeName` by default. When an API uses another field name, pass `task-tag-field` without changing the task adapter:
+The existing `class` prop remains supported. If the consuming component uses `<style scoped>`, use `:deep()` for selectors inside the Teleport panel:
 
-```vue
-<RhDataCenter
-  :categories="categories"
-  :load-tasks="loadTasks"
-  task-tag-field="taskTypeName"
-/>
+```scss
+.restaurant-data-center {
+  :deep(.rh-data-center-panel__category.is-active) {
+    color: #409eff;
+  }
+}
 ```
 
-## Task tip flow
-
-Use `useRhDataCenter` after a page successfully creates a background task:
+The task status icons use the built-in images by default. Use `status-icons` when a business needs different images; omitted statuses continue to use the defaults:
 
 ```vue
 <script setup lang="ts">
-import { RhDataCenterTip, useRhDataCenter } from 'rhjy-ui'
-
-const { tipVisible, tipConfig, showTip } = useRhDataCenter()
+import successIcon from './images/data-center-success.png'
+import failedIcon from './images/data-center-failed.png'
 
-const startExport = async () => {
-  const result = await createExportTask()
-  showTip({
-    type: 'export',
-    minutes: Number(result.minutes),
-    title: '导出文件生成中，大概需要',
-    content: '现在你可关闭弹框，去做其他事情了。',
-  })
+const statusIcons = {
+  success: successIcon,
+  failed: failedIcon,
 }
 </script>
 
 <template>
-  <RhDataCenterTip v-model="tipVisible" v-bind="tipConfig" />
+  <RhDataCenter
+    :categories="categories"
+    :load-tasks="loadTasks"
+    :status-icons="statusIcons"
+  />
 </template>
 ```
 
-`RhDataCenterTip` 默认使用简化引导动画；需要使用带数据处理中心图片、手势和方向切换的引导时，可传入 `guideVariant="normal"` 或 `guideVariant="super"`。
-
-## Standard task model
-
-The adapter returns `id`, `categoryKey`, `title`, `createdAt`, `progress`, and one of `waiting`, `processing`, `success`, or `failed`. Optional `tag`, `message`, `actions`, and `raw` provide display and application action context.
-
-For completed tasks with rejected records, pass the normalized `failCount` field. The task item keeps the completed progress bar, shows `失败记录（xx条）` in red, and hides the normal completion message when the count is zero. The application still supplies the failure-record action and handles its download event.
-
-For processing tasks, pass `taskSeconds` to show `总时长约X分XX秒` instead of the default processing message. If `taskSeconds` is omitted, the provided `message` is displayed.
-
-## Styling
-
-Override CSS variables at the application root when needed:
-
-```css
-:root {
-  --rh-ui-data-center-primary: #00828a;
-  --rh-ui-data-center-panel-width: 606px;
-  --rh-ui-data-center-panel-height: 500px;
-}
-```
+The available keys are `waiting`, `processing`, `success`, and `failed`. The current default waiting, success, and failed icons keep their existing class name `rh-data-center-panel__progressStatusIcon`, so size and layout can also be overridden through `custom-class`.
 
 ## Build and publish
-
-After changing the source code or component assets, run the package script in the `rh-ui` directory to regenerate `dist`:
-
-```bash
-cd D:\workfile\sass-workspace\packages\rh-ui
-npm run package
-```
-
-The workspace equivalent is:
-
-```bash
-pnpm --filter rhjy-ui package
-```
-
-Before publishing, increment the package version without creating a Git tag:
-
-```bash
-npm run version:patch
-```
-
-Use `npm run version:minor` only for a backward-compatible feature release. You can inspect the files that will be published with:
-
-```bash
-npm pack --dry-run
-```
-
-After confirming the tarball contents, publish the public package:
-
-```bash
-npm login --registry=https://registry.npmjs.org --auth-type=web
-npm publish --access public --registry=https://registry.npmjs.org
-```
-
-If the account uses two-factor authentication, npm opens the browser authentication flow. After publishing, synchronize the school admin project from this package directory:
-
-```bash
-cd D:\workfile\sass-workspace\packages\rh-ui
-npm run sync:wise-school-admin
-```
-
-The script installs the latest public `rhjy-ui` release with an exact version and synchronizes `D:\workfile\wise-school-admin\package.json` and `package-lock.json`. It is intended for the fixed local workspace path; add another explicit `sync:<project>` script when a new application needs this workflow.
-
-## Releases
-
-The package is published with compiled `dist` output. Consumers should use an explicit version such as `rhjy-ui@0.2.2`; application-specific API adapters remain in the consuming project.
+
+After changing the source code or component assets, run the package script in the `rh-ui` directory to regenerate `dist`:
+
+```bash
+cd D:\workfile\sass-workspace\packages\rh-ui
+npm run package
+```
+
+The workspace equivalent is:
+
+```bash
+pnpm --filter rhjy-ui package
+```
+
+Before publishing, increment the package version without creating a Git tag:
+
+```bash
+npm run version:patch
+```
+
+Use `npm run version:minor` only for a backward-compatible feature release. You can inspect the files that will be published with:
+
+```bash
+npm pack --dry-run
+```
+
+After confirming the tarball contents, publish the public package:
+
+```bash
+npm login --registry=https://registry.npmjs.org --auth-type=web
+npm publish --access public --registry=https://registry.npmjs.org
+```
+
+If the account uses two-factor authentication, npm opens the browser authentication flow. After publishing, synchronize the school admin project from this package directory:
+
+```bash
+cd D:\workfile\sass-workspace\packages\rh-ui
+npm run sync:wise-school-admin
+```
+
+The script installs the latest public `rhjy-ui` release with an exact version and synchronizes `D:\workfile\wise-school-admin\package.json` and `package-lock.json`. It is intended for the fixed local workspace path; add another explicit `sync:<project>` script when a new application needs this workflow.
+
+## Releases
+
+The package is published with compiled `dist` output. Consumers should use an explicit version such as `rhjy-ui@0.2.2`; application-specific API adapters remain in the consuming project.

package/dist/data-center/RhDataCenter.vue.d.ts

@@ -1,4 +1,4 @@
-import { RhDataCenterCategory, RhDataCenterLoadTasks, RhDataCenterTaskActionPayload } from './types';
+import { RhDataCenterCategory, RhDataCenterLoadTasks, RhDataCenterStatusIcons, RhDataCenterTaskActionPayload } from './types';
 
 declare function __VLS_template(): {
     trigger?(_: {
@@ -36,6 +36,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     panelHeight?: string | number;
     sidebarWidth?: string | number;
     taskTagField?: string;
+    statusIcons?: RhDataCenterStatusIcons;
     panelRight?: string | number;
     pollInterval?: number;
     refreshOnOpen?: boolean;
@@ -44,6 +45,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     categoryCounts?: Record<string, number>;
     icon?: string;
     activeIcon?: string;
+    customClass?: string;
 }>, {
     modelValue: any;
     label: string;
@@ -58,6 +60,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     showCategoryCount: boolean;
     icon: string;
     activeIcon: string;
+    customClass: string;
 }>>, {}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {
     "update:modelValue": (value: boolean) => void;
     open: () => void;
@@ -74,6 +77,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     panelHeight?: string | number;
     sidebarWidth?: string | number;
     taskTagField?: string;
+    statusIcons?: RhDataCenterStatusIcons;
     panelRight?: string | number;
     pollInterval?: number;
     refreshOnOpen?: boolean;
@@ -82,6 +86,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     categoryCounts?: Record<string, number>;
     icon?: string;
     activeIcon?: string;
+    customClass?: string;
 }>, {
     modelValue: any;
     label: string;
@@ -96,6 +101,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     showCategoryCount: boolean;
     icon: string;
     activeIcon: string;
+    customClass: string;
 }>>> & Readonly<{
     onClose?: () => any;
     onRefresh?: (category: RhDataCenterCategory) => any;
@@ -117,6 +123,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     closeOnClickOutside: boolean;
     icon: string;
     activeIcon: string;
+    customClass: string;
 }, {}, {}, {}, string, import('vue').ComponentProvideOptions, true, {}, any>;
 declare const _default: __VLS_WithTemplateSlots<typeof __VLS_component, ReturnType<typeof __VLS_template>>;
 export default _default;

package/dist/data-center/RhDataCenterPanel.vue.d.ts

@@ -1,4 +1,4 @@
-import { RhDataCenterCategory, RhDataCenterLoadTasks, RhDataCenterTask, RhDataCenterTaskActionPayload, RhDataCenterTaskResult } from './types';
+import { RhDataCenterCategory, RhDataCenterLoadTasks, RhDataCenterStatusIcons, RhDataCenterTask, RhDataCenterTaskActionPayload, RhDataCenterTaskResult } from './types';
 
 declare function __VLS_template(): {
     header?(_: {
@@ -27,6 +27,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     activeCategoryKey?: string | number;
     sidebarWidth?: string | number;
     taskTagField?: string;
+    statusIcons?: RhDataCenterStatusIcons;
     closeable?: boolean;
     showTotal?: boolean;
     showCategoryCount?: boolean;
@@ -53,6 +54,7 @@ declare const __VLS_component: import('vue').DefineComponent<import('vue').Extra
     activeCategoryKey?: string | number;
     sidebarWidth?: string | number;
     taskTagField?: string;
+    statusIcons?: RhDataCenterStatusIcons;
     closeable?: boolean;
     showTotal?: boolean;
     showCategoryCount?: boolean;

package/dist/data-center/components/RhDataCenterTaskItem.vue.d.ts

@@ -1,11 +1,13 @@
-import { RhDataCenterTask } from '../types';
+import { RhDataCenterStatusIcons, RhDataCenterTask } from '../types';
 
 declare const _default: import('vue').DefineComponent<import('vue').ExtractPropTypes<__VLS_TypePropsToRuntimeProps<{
     task: RhDataCenterTask;
+    statusIcons?: RhDataCenterStatusIcons;
 }>>, {}, {}, {}, {}, import('vue').ComponentOptionsMixin, import('vue').ComponentOptionsMixin, {
     action: (action: string) => void;
 }, string, import('vue').PublicProps, Readonly<import('vue').ExtractPropTypes<__VLS_TypePropsToRuntimeProps<{
     task: RhDataCenterTask;
+    statusIcons?: RhDataCenterStatusIcons;
 }>>> & Readonly<{
     onAction?: (action: string) => any;
 }>, {}, {}, {}, {}, string, import('vue').ComponentProvideOptions, true, {}, any>;