Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions ui/src/conversation-panel/components/message-list/index.vue
Original file line number Diff line number Diff line change
Expand Up @@ -86,5 +86,3 @@ const showUserAvatar = computed(() => appInfo.value?.show_user_avatar)
</ReverseInfiniteScroll>
<ShareFooter v-if="isShared" />
</template>

<style scoped lang="scss"></style>
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,10 @@ defineExpose({ scrollToBottom, followBottom })
</script>

<template>
<div v-loading="initialLoading" class="min-h-0 flex-1 overflow-hidden">
<div class="min-h-0 flex-1 overflow-hidden">
<el-scrollbar ref="scrollbarRef" wrap-class="[overflow-anchor:none]" view-class="min-h-full flex-column" @scroll="onScroll">
<div class="min-h-full flex-1 flex-column" :class="contentClass">
<el-skeleton v-if="initialLoading" animated />
<!-- 固定预留状态行,加载提示切换时不改变消息位置。 -->
<div v-if="loadingMore" class="flex-center py-4 shrink-0">
<span class="mk-conversation-loading" />
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ export function createConversationListStore(deps: ConversationListDeps) {

// 历史会话分页
const conversations = ref<Conversation[]>([])
const initialLoading = ref(true)
const pageSize = 50
const currentPage = ref(1)
const hasMore = ref(true)
Expand All @@ -45,6 +46,8 @@ export function createConversationListStore(deps: ConversationListDeps) {
hasMore.value = records.length >= pageSize
} catch {
// 部分模式可能不提供历史接口,加载失败时保留现有列表和分页状态。
} finally {
initialLoading.value = false
}
}

Expand Down Expand Up @@ -110,6 +113,7 @@ export function createConversationListStore(deps: ConversationListDeps) {
switchShared,
bindLeftSideMode,
conversations,
initialLoading,
currentChatId,
currentConversation,
appInfo,
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ const shareLink = useShareLinkStoreOptional()
const showShare = useShowShare()
const canShare = computed(() => msgs.messages.value.length > 0 && !msgs.streamLoading.value && !msgs.loading.value)

const { appInfo, conversations, currentChatId, selectConversation, newConversation, deleteChat, toggleLeftSide, hasMore, loadMore } =
const { appInfo, conversations, initialLoading, currentChatId, selectConversation, newConversation, deleteChat, toggleLeftSide, hasMore, loadMore } =
useConversationListStore()

// 非当前会话先激活并加载消息,避免分享到其他会话。
Expand Down Expand Up @@ -99,7 +99,8 @@ function handleClearConversations() {

<!-- 历史列表独立滚动,应用信息和新建入口保持固定。 -->
<el-scrollbar class="min-h-0 flex-1 mt-1 -mr-4" view-class="pr-4">
<div v-if="conversations.length === 0" class="text-N600 text-center mt-4">暂无历史记录</div>
<el-skeleton v-if="initialLoading" animated />
<div v-else-if="conversations.length === 0" class="text-N600 text-center mt-4">暂无历史记录</div>
<div v-else class="space-y-1">
<template v-for="conversation in conversations" :key="conversation.id">
<MkListItem :active="currentChatId === conversation.id" @click="selectConversation(conversation.id)">
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,10 +25,17 @@ const selectedApplicationId = ref(props.applicationId)
const keyword = ref('')
const conversations = ref<PortalConversationSummary[]>([])
const scrollRef = ref<{ reset: () => Promise<void> }>()
const initialLoading = ref(true)
let requestVersion = 0

// 搜索与切换智能体从第一页重新加载,分页由共享滚动组件维护。
const loadConversations = ({ currentPage, pageSize }: { currentPage: number; pageSize: number }) =>
ConversationApi.getPortalConversationPage(selectedApplicationId.value, currentPage, pageSize, keyword.value.trim())
const loadConversations = ({ currentPage, pageSize }: { currentPage: number; pageSize: number }) => {
const currentRequestVersion = ++requestVersion
initialLoading.value = currentPage === 1
return ConversationApi.getPortalConversationPage(selectedApplicationId.value, currentPage, pageSize, keyword.value.trim()).finally(() => {
if (currentRequestVersion === requestVersion) initialLoading.value = false
})
}
const handleSearch = () => scrollRef.value?.reset()
const handleApplicationChange = () => {
keyword.value = ''
Expand Down Expand Up @@ -76,7 +83,9 @@ const handleDeleteConversation = (conversation: PortalConversationSummary) => {
<!-- 按历史对话摘要搜索 -->
<MkSearchInput v-model="keyword" class="min-w-0 flex-1" placeholder="搜索" @change="handleSearch" />
</div>
<MkInfiniteScroll ref="scrollRef" v-model="conversations" :load="loadConversations">
<el-skeleton v-if="initialLoading" animated />
<!-- 保持滚动组件挂载,由它发起首屏和重置请求。 -->
<MkInfiniteScroll v-show="!initialLoading" ref="scrollRef" v-model="conversations" :load="loadConversations">
<div class="space-y-1">
<!-- 打开历史对话 -->
<MkListItem
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ export function createPortalConversationListStore(deps: PortalConversationListDe

// 历史对话分组
const applicationGroups = ref<PortalApplicationGroup[]>([])
const initialLoading = ref(true)
const isApplicationGroupsLoaded = ref(false)

// 总数不超过 20 条时,补齐分组接口可能只返回的最近 5 条会话。
Expand All @@ -60,14 +61,18 @@ export function createPortalConversationListStore(deps: PortalConversationListDe
}

const loadApplicationGroups = () =>
pageApplicationConversations(1, APPLICATION_PAGE_SIZE).then((response) => {
applicationGroups.value = (response.records ?? []).map((application) => ({
...application,
expanded: application.conversations.length > 0 || application.id === currentApplicationId.value,
}))
isApplicationGroupsLoaded.value = true
return completeGroupConversations()
})
pageApplicationConversations(1, APPLICATION_PAGE_SIZE)
.then((response) => {
applicationGroups.value = (response.records ?? []).map((application) => ({
...application,
expanded: application.conversations.length > 0 || application.id === currentApplicationId.value,
}))
isApplicationGroupsLoaded.value = true
return completeGroupConversations()
})
.finally(() => {
initialLoading.value = false
})

// 展开其他智能体时查询其最近会话;当前智能体以会话列表 Store 为准,无需查询
const loadGroupConversations = (group: PortalApplicationGroup) =>
Expand Down Expand Up @@ -153,6 +158,7 @@ export function createPortalConversationListStore(deps: PortalConversationListDe

return {
applicationGroups,
initialLoading,
isApplicationGroupsLoaded,
loadApplicationGroups,
toggleGroup,

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The diff looks mostly fine, but here are the irregularities and suggestions:

Potential issues

  1. initialLoading never resets / no retry handling.
    initialLoading.value = false is set in .finally(), which runs on both success and failure — that part is correct. However, if loadApplicationGroups() can be called again (e.g., a refresh or retry), initialLoading is left false. That's probably intended for a "first load only" flag; if it's meant as a general loading indicator, it should be set to true at the start of each call.

  2. completeGroupConversations() rejection is silent to the caller.
    Because .finally() is chained after .then(), the returned promise still rejects if either the page request or completeGroupConversations() fails. Callers must handle this. Pairing .finally() with an unhandled rejection could produce console errors if callers don't .catch(). Consider returning a handled promise or documenting the rejection contract.

  3. Error state not tracked.
    There's no error ref. If loading fails, initialLoading becomes false but consumers can't distinguish "loaded empty" from "failed." Consider adding loadError.

  4. Race conditions on repeated calls.
    If loadApplicationGroups() is invoked twice concurrently, the later .finally() may clear initialLoading before the first completes. A request-token / sequence guard would make this robust.

Optimization / style

  1. Indentation-only reformatting inflates the diff. Keeping the original .then(...) single-expression form and just appending .finally(() => { initialLoading.value = false }) would reduce review noise.

  2. Consider extracting the mapping logic (records -> expanded groups) into a helper; the arrow-chain is getting long.

  3. Naming: initialLoading is fine, but if it only tracks the very first fetch, a name like isInitialLoadDone/hasLoadedOnce (inverted) or a comment clarifies semantics.

Verdict: No functional bugs introduced; main concerns are the missing error state and concurrent-call guarding.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ const portalLogo = computed(() => authStore.authProfile?.logo)
const msgs = useMessageListStore()
const canShare = computed(() => msgs.messages.value.length > 0 && !msgs.streamLoading.value && !msgs.loading.value)
const portalList = usePortalConversationListStore()
const { applicationGroups, currentApplicationId, isApplicationListActive, toggleGroup } = portalList
const { applicationGroups, initialLoading, currentApplicationId, isApplicationListActive, toggleGroup } = portalList
const { conversations, currentChatId, selectConversation, deleteChat, newConversation, switchShared, toggleLeftSide } = useConversationListStore()

const historyApplicationId = ref('')
Expand Down Expand Up @@ -135,8 +135,9 @@ const handleClearConversations = () => {
</div>

<!-- 历史列表独立滚动,门户入口和新建入口保持固定。 -->
<el-scrollbar :inert="clearing" class="min-h-0 flex-1 mt-1 -mr-4" view-class="pr-4">
<div v-if="historyApplicationGroups.length === 0" class="text-N600 text-center mt-4">暂无历史记录</div>
<el-scrollbar class="min-h-0 flex-1 mt-1 -mr-4" view-class="pr-4">
<el-skeleton v-if="initialLoading" animated />
<div v-else-if="historyApplicationGroups.length === 0" class="text-N600 text-center mt-4">暂无历史记录</div>
<div v-else class="space-y-1">
<template v-for="group in historyApplicationGroups" :key="group.id">
<MkCollapse
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,10 @@ onMounted(() => {
<MkSearchInput v-model="applicationKeyword" class="w-full! md:w-50!" placeholder="搜索" @change="loadApplications" />
</header>

<el-scrollbar v-loading="isApplicationsLoading" class="min-h-0 flex-1 p-4 pt-0!">
<el-scrollbar class="min-h-0 flex-1 p-4 pt-0!">
<el-skeleton v-if="isApplicationsLoading" animated />
<MkEmpty
v-if="!isApplicationsLoading && applications.length === 0"
v-else-if="applications.length === 0"
:type="applicationKeyword ? 'search' : 'default'"
:description="applicationKeyword ? '没有匹配的智能体' : '暂无可用智能体'"
class="mt-20"
Expand Down
6 changes: 6 additions & 0 deletions ui/src/styles/element-plus.scss
Original file line number Diff line number Diff line change
Expand Up @@ -979,6 +979,12 @@
}
}

/* skeleton */
.el-skeleton {
--el-skeleton-color: rgba(239, 240, 241, 0.6);
--el-skeleton-to-color: rgba(239, 240, 241, 1);
}

/* slider */
.el-slider {
--el-slider-button-wrapper-size: 16px;
Expand Down
4 changes: 4 additions & 0 deletions ui/src/views/VIEW_README.md
Original file line number Diff line number Diff line change
Expand Up @@ -515,6 +515,10 @@ System 资源管理的修正内容与添加知识库选项仅包含当前智能

### 正式对话与门户

Chat/Portal 的历史侧栏首次查询使用列表骨架;`ReverseInfiniteScroll` 在正在加载且没有消息时
统一展示默认文本骨架,适用于对话、分享记录及日志详情。新建对话、流式生成与向上加载历史
不使用骨架;骨架不参与消息计数和历史分页。

`conversation-panel/components/message-input/url-upload/` 维护 URL 附件浮层:开启 URL 上传时,附件按钮打开浮层,按启用的文件类型选择分类、逐行输入 HTTP/HTTPS 地址。通过当前入口的文件 API 获取远程内容,校验响应状态、MIME 类型和大小,并补齐无扩展名的文件名;图片、视频保留原地址,文档、音频和其他文件转换为 File 后复用附件上传流程。URL 与本地文件共用附件总数限制,远程读取及转上传完成前禁止发送。本地上传开启时,允许输入区拖拽、文件粘贴上传,并通过浮层底部按钮选择文件;关闭本地上传时禁用这些入口。仅本地上传模式沿用原有直接选择入口。

- Chat/Portal 页面以 auth token 为面板 key,token 变化重建并加载用户档案;路由认证见路由文档。
Expand Down
48 changes: 25 additions & 23 deletions ui/src/views/home/components/HomeResourceOverview.vue
Original file line number Diff line number Diff line change
Expand Up @@ -118,15 +118,15 @@ function loadResources() {
})
}
function handleNavigate(card: HomeResourceCard) {
if (card.disabled) return
if (loading.value || card.disabled) return
router.push({ name: card.route, params: { workspaceId: props.workspaceId } })
}
onMounted(loadResources)
defineExpose({ refresh: loadResources })
</script>
<template>
<section>
<div v-loading="loading" class="grid grid-cols-1 gap-4 sm:grid-cols-2 xl:grid-cols-4">
<div class="grid grid-cols-1 gap-4 sm:grid-cols-2 xl:grid-cols-4">
<template v-for="card in resourceGroups" :key="card.route">
<!-- 进入未禁用资源的列表 -->
<el-card
Expand All @@ -135,29 +135,31 @@ defineExpose({ refresh: loadResources })
:style="{ color: card.color, backgroundImage: `linear-gradient(to bottom, ${card.color}0A 0%, #FFFFFF 40%, #FFFFFF 100%)` }"
@click="handleNavigate(card)"
>
<div class="flex-between text-N900">
<div>
<p class="text-N600 mb-1">{{ card.label }}</p>
<p class="text-3xl leading-9.5 font-semibold tabular-nums">{{ toThousands(card.total) }}</p>
</div>
<el-skeleton :loading="loading" animated>
<div class="flex-between text-N900">
<div>
<p class="text-N600 mb-1">{{ card.label }}</p>
<p class="text-3xl leading-9.5 font-semibold tabular-nums">{{ toThousands(card.total) }}</p>
</div>

<el-avatar
shape="square"
:size="44"
:style="{ color: card.color, backgroundColor: `${card.color}14`, '--el-avatar-border-radius': '12px' }"
>
<MkIcon :name="card.icon" :size="26" />
</el-avatar>
</div>
<el-avatar
shape="square"
:size="44"
:style="{ color: card.color, backgroundColor: `${card.color}14`, '--el-avatar-border-radius': '12px' }"
>
<MkIcon :name="card.icon" :size="26" />
</el-avatar>
</div>

<div class="flex mt-4 gap-4">
<template v-for="[label, value] in card.details" :key="String(label)">
<div class="min-w-0 flex-1">
<p class="text-N600">{{ label }}</p>
<h2 class="mt-1 text-N900">{{ toThousands(value) }}</h2>
</div>
</template>
</div>
<div class="flex mt-4 gap-4">
<template v-for="[label, value] in card.details" :key="String(label)">
<div class="min-w-0 flex-1">
<p class="text-N600">{{ label }}</p>
<h2 class="mt-1 text-N900">{{ toThousands(value) }}</h2>
</div>
</template>
</div>
</el-skeleton>
</el-card>
</template>
</div>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The diff is generally reasonable, but there are a few potential issues and improvements:

  1. Skeleton may never show if resourceGroups is empty during loading

    • The skeleton is inside v-for="card in resourceGroups".
    • If resourceGroups starts as [] and is populated only after loading, no cards render, so no skeleton renders.
    • Since v-loading was removed from the grid, the user may see a blank area while loading.
    • Fix: render placeholder skeleton cards when loading && resourceGroups.length === 0, or keep a parent-level loading state.
  2. Ensure loading is reset in finally

    • handleNavigate now blocks navigation when loading.value is true.
    • If loadResources throws before resetting loading, navigation will be blocked indefinitely and the skeleton will remain.
    • Use try/finally:
    async function loadResources() {
      loading.value = true
      try {
        // load data
      } finally {
        loading.value = false
      }
    }
  3. Blocking navigation during all loading may be too aggressive

    • If loading is also used for background refreshes, users cannot navigate during a refresh.
    • Consider separating initialLoading from refreshing, or only block navigation when the card data is not ready.
    • If you keep the guard, also make the card visually disabled during loading, e.g. cursor-not-allowed or pointer-events-none, so the UI does not appear clickable but do nothing.
  4. The default el-skeleton does not match the card layout

    • The default skeleton renders generic text rows, not the label/total/avatar/details structure.
    • This causes visual mismatch and possible layout shift when the real content appears.
    • Use a custom #template with el-skeleton-item matching the card structure, and set a stable min-height.
  5. Check CSS that depends on direct children

    • Wrapping the card content in <el-skeleton> adds an extra wrapper element inside el-card__body.
    • If existing CSS uses direct-child selectors such as .el-card__body > .flex-between, it may break.
    • Verify the card body layout still works after the wrapper is added.
  6. Minor accessibility / UX notes

    • The card still looks clickable during loading even though navigation is blocked.
    • Consider adding aria-busy to the loading container and aria-disabled to blocked cards.
    • The clickable el-card is not keyboard accessible by default. Consider using router-link/button or adding keyboard handlers if this is important.

Overall, no syntax error is visible, but the main risk is the empty-resourceGroups case and ensuring loading is always reset.

Expand Down
46 changes: 25 additions & 21 deletions ui/src/views/home/components/HomeStatistics.vue
Original file line number Diff line number Diff line change
Expand Up @@ -81,39 +81,43 @@ watch(() => [props.workspaceId, props.applicationId], loadMonitoring, { immediat
<slot name="application" :loading="loading" />
</div>
</div>
<div v-loading="loading" class="min-h-40">
<div class="min-h-40">
<div class="mb-4 grid grid-cols-1 gap-4 sm:grid-cols-2 xl:grid-cols-4">
<template v-for="metric in metrics" :key="metric.id">
<el-card shadow="never">
<p class="text-N600">{{ metric.title }}</p>
<div class="mt-1 flex-align-center gap-4 tabular-nums">
<template v-if="metric.id === 'feedback'">
<template v-for="(series, index) in metric.series" :key="series.name">
<div class="flex-align-center gap-2" :title="series.name">
<MkIcon
:name="index === 0 ? 'icon_thumbsup_filled' : 'icon_thumbdown_filled'"
class="shrink-0"
:class="index === 0 ? 'text-[#FFC60A]!' : 'text-danger!'"
/>
<h2>{{ numberFormat(series.total) }}</h2>
</div>
<el-skeleton :loading="loading" :rows="1" animated>
<p class="text-N600">{{ metric.title }}</p>
<div class="mt-1 flex-align-center gap-4 tabular-nums">
<template v-if="metric.id === 'feedback'">
<template v-for="(series, index) in metric.series" :key="series.name">
<div class="flex-align-center gap-2" :title="series.name">
<MkIcon
:name="index === 0 ? 'icon_thumbsup_filled' : 'icon_thumbdown_filled'"
class="shrink-0"
:class="index === 0 ? 'text-[#FFC60A]!' : 'text-danger!'"
/>
<h2>{{ numberFormat(series.total) }}</h2>
</div>
</template>
</template>
</template>
<template v-else>
<h2>
{{ metric.id === 'tokens' ? formatTokenNumber(metric.series[0]?.total) : numberFormat(metric.series[0]?.total) }}
</h2>
<h6 v-if="metric.id === 'activeUsers'" class="-ml-1 text-danger" title="新增用户">+{{ numberFormat(metric.series[1]?.total) }}</h6>
</template>
</div>
<template v-else>
<h2>
{{ metric.id === 'tokens' ? formatTokenNumber(metric.series[0]?.total) : numberFormat(metric.series[0]?.total) }}
</h2>
<h6 v-if="metric.id === 'activeUsers'" class="-ml-1 text-danger" title="新增用户">+{{ numberFormat(metric.series[1]?.total) }}</h6>
</template>
</div>
</el-skeleton>
</el-card>
</template>
</div>
<div class="grid grid-cols-1 gap-4 xl:grid-cols-2">
<template v-for="metric in metrics" :key="metric.id">
<el-card shadow="never">
<h4>{{ metric.title }}</h4>
<el-skeleton v-if="loading" animated class="h-89 mt-4" :rows="8" />
<MkLineChart
v-else
:value-formatter="metric.id === 'tokens' ? formatTokenNumber : numberFormat"
class="-mt-6"
:option="{ xData: days, yData: metric.series }"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change is reasonable, but there are a few issues worth addressing:

  1. Skeleton depends on metrics being populated

    • Both skeleton blocks are inside v-for="metric in metrics".
    • If metrics is empty during the initial load, no skeletons will render at all.
    • Since you removed the parent v-loading, the page may show no loading indicator until metrics is populated.
    • Fix: either render fixed placeholder cards while loading && !metrics.length, keep a container-level loading indicator, or initialize metrics with placeholder entries.
  2. Chart skeleton and chart have mismatched spacing/height

    • The skeleton uses class="h-89 mt-4", while the chart uses class="-mt-6".
    • This can cause a visible layout jump when loading finishes.
    • Also verify h-89 exists in your Tailwind config. It is not part of Tailwind’s default spacing scale.
    • Better: wrap the chart area in a fixed-height container and apply the same height/positioning to both skeleton and chart.
  3. Chart skeleton shape is not chart-like

    • <el-skeleton :rows="8" /> renders several text-like skeleton rows, not a rectangular chart placeholder.
    • Prefer a single rectangular skeleton item:
    <el-skeleton v-if="loading" animated>
      <template #template>
        <el-skeleton-item variant="rect" class="h-89 w-full" />
      </template>
    </el-skeleton>

    or use a custom skeleton matching the actual chart height.

  4. Top-card skeleton may not match real card height

    • :rows="1" may be shorter than the actual card content, especially for the feedback card with two values.
    • This can cause card height/layout shift after loading.
    • Consider a custom skeleton or a min-height matching the real content.
  5. Inconsistent loading presentation

    • Top card titles are hidden by the skeleton.
    • Bottom chart titles remain visible while only the chart area is skeletonized.
    • If consistency matters, keep the title visible in both cases and skeletonize only the value/chart area.
  6. Chart is unmounted/remounted on every loading toggle

    • <MkLineChart v-else ... /> means the chart is destroyed while loading and recreated afterward.
    • If loading is also used for refreshes, this can cause unnecessary re-initialization and flicker.
    • Consider distinguishing initial loading from refreshing, or use v-show / an overlay if the chart can remain mounted with empty data.
  7. Minor accessibility/UX note

    • Consider adding aria-busy or a loading label if this is a user-facing dashboard and accessibility is important.

The v-if / v-else adjacency itself is valid. The main concerns are the empty-metrics loading case and the layout shift between skeleton and chart.

Expand Down
2 changes: 1 addition & 1 deletion ui/src/views/home/components/ranking/HomeRankings.vue
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ onMounted(loadRankings)
<h4>排行榜 TOP5</h4>
<MkDateRange @change="handleRangeChange" />
</div>
<div v-loading="loading" class="grid grid-cols-1 gap-4 xl:grid-cols-3">
<div class="grid grid-cols-1 gap-4 xl:grid-cols-3">
<RankingCard
title="Tokens 消耗 · Top 智能体"
:records="rankings.tokens"
Expand Down
3 changes: 2 additions & 1 deletion ui/src/views/home/components/ranking/RankingCard.vue
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,8 @@ function getRecordPercentage(record: HomeRankingRecord) {
<MkIcon name="icon_right_outlined" />
</el-button>
</div>
<MkEmpty v-if="!loading && !records?.length" :image-size="80" />
<el-skeleton v-if="loading" :rows="7" animated />
<MkEmpty v-else-if="!records?.length" :image-size="80" />
<div v-else class="space-y-6">
<template v-for="(record, index) in records" :key="index">
<div class="flex-between gap-3">
Expand Down
Loading