- API 路由统一: 移除 /api/h5/,统一 /api/pms/ 入口 - 二进制改名: api-server -> pms-api(与服务名一致) - nginx: 合并 /api/ + /pms/api/ 为 /api/pms/ - 新增 docs/API.md 接口文档 - 后端: CabinetDetail 增加 rssi/pow_fail/address/soc 等字段 - Redis 管道批量读取仓体实时数据(SOC/电压/电流/功率) - DB: 所有 TIMESTAMP 列改为 DATETIME(修复类型不匹配) - 用户管理: 新增创建时间/修改时间列,状态改用 Switch - 角色管理/用户管理: 操作按钮改为图标 - PC 设备详情: 基本信息补全 RSSI/ICCID/电源/地址 - PC 卡片: 通道统计改用 Lucide 图标,颜色统一 - PC 二维码: canvas 渲染,含编号文字,支持右键下载 - H5: 按 uni-app 规范修正导航(navigateTo 替代 reLaunch) - H5: 详情页加返回导航条 - H5: 扫码支持摄像头(jsQR)+ ?id= 参数 - H5: 底部 tabBar 在所有页面常显 - H5: 首页统计改为 6 项(设备/通道/空闲/充电/充满/故障) - H5: 下拉刷新 / 上拉加载 - 产品首页: 添加业务联系 - 文档: 清理过时文件,补充缺失规范章节
4.1 KiB
4.1 KiB
Use Suspense Events for Loading State Tracking
Rule
<Suspense> emits three events: pending, resolve, and fallback. Use these events to track loading states, implement analytics, coordinate UI updates, or trigger side effects at appropriate times.
Why This Matters
Relying solely on the fallback slot for loading indication limits your options. The events provide programmatic access to Suspense state changes, enabling:
- Loading progress tracking
- Analytics for perceived performance
- Coordinated animations
- Custom loading indicators outside the Suspense boundary
- Debugging async component behavior
Basic Usage
<script setup>
import { ref } from 'vue'
const loadingState = ref('idle')
const loadStartTime = ref(null)
const onPending = () => {
loadingState.value = 'pending'
loadStartTime.value = Date.now()
console.log('Suspense entered pending state')
}
const onResolve = () => {
loadingState.value = 'resolved'
const loadTime = Date.now() - loadStartTime.value
console.log(`Content resolved in ${loadTime}ms`)
// Track performance
analytics.track('page_load_time', { duration: loadTime })
}
const onFallback = () => {
loadingState.value = 'fallback'
console.log('Fallback content is now visible')
}
</script>
<template>
<Suspense
@pending="onPending"
@resolve="onResolve"
@fallback="onFallback"
>
<AsyncPage />
<template #fallback>
<LoadingSkeleton />
</template>
</Suspense>
</template>
Advanced: Global Loading Indicator
<!-- App.vue -->
<script setup>
import { ref, provide } from 'vue'
const globalLoading = ref(false)
const pendingCount = ref(0)
provide('globalLoading', globalLoading)
const onSuspensePending = () => {
pendingCount.value++
globalLoading.value = true
}
const onSuspenseResolve = () => {
pendingCount.value--
if (pendingCount.value === 0) {
globalLoading.value = false
}
}
</script>
<template>
<!-- Global loading bar -->
<Transition name="fade">
<LoadingBar v-if="globalLoading" />
</Transition>
<RouterView v-slot="{ Component }">
<Suspense
@pending="onSuspensePending"
@resolve="onSuspenseResolve"
>
<component :is="Component" />
<template #fallback>
<PageSkeleton />
</template>
</Suspense>
</RouterView>
</template>
Event Sequence
Initial Load:
1. @pending - Suspense enters pending state
2. @fallback - Fallback content is displayed (may not fire if resolved quickly)
3. @resolve - Async content is ready
On Content Change (with timeout):
1. @pending - New async dependency detected
2. (Previous content still visible during timeout period)
3. @fallback - Timeout exceeded, fallback shown
4. @resolve - New content ready
On Content Change (fast):
1. @pending - New async dependency detected
2. @resolve - Resolved before timeout, fallback never shown
Coordinating with Transitions
<script setup>
import { ref } from 'vue'
const isTransitioning = ref(false)
const onPending = () => {
isTransitioning.value = true
}
const onResolve = () => {
// Delay to allow enter transition to complete
setTimeout(() => {
isTransitioning.value = false
}, 300)
}
</script>
<template>
<div :class="{ 'is-loading': isTransitioning }">
<Transition mode="out-in" @after-leave="onAfterLeave">
<Suspense @pending="onPending" @resolve="onResolve">
<component :is="currentView" :key="viewKey" />
<template #fallback>
<LoadingView />
</template>
</Suspense>
</Transition>
</div>
</template>
Key Points
@pendingfires when Suspense starts waiting for async dependencies@fallbackfires when fallback content becomes visible (respects timeout)@resolvefires when default slot content is ready to display- Use events for analytics, debugging, and coordinating UI outside Suspense
- Events enable global loading indicators across multiple Suspense boundaries
@fallbackmay not fire if content resolves before the timeout