12451 b553c4e519 feat: API 统一 + 设备详情补全 + H5 导航优化

- 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: 下拉刷新 / 上拉加载
- 产品首页: 添加业务联系
- 文档: 清理过时文件，补充缺失规范章节

2026-07-04 04:03:02 +08:00

2.5 KiB

Raw Blame History

Suspense is Experimental and API May Change

Rule

<Suspense> is an experimental feature in Vue 3. The API is not guaranteed to reach stable status and may change before it does. Plan for potential breaking changes when using Suspense in production applications.

Why This Matters

Relying heavily on experimental features in production code creates maintenance risk. If the API changes, refactoring could be substantial. The Suspense API has been experimental since Vue 3's initial release (over 4 years) and developers have reported frustrations with bugs and restrictions.

Bad Code

<script setup>
// Building critical application infrastructure on experimental API
// without fallback strategy
</script>

<template>
  <!-- Core navigation depends entirely on Suspense -->
  <Suspense>
    <RouterView />
    <template #fallback>
      <GlobalLoadingScreen />
    </template>
  </Suspense>
</template>

Good Code

<script setup>
import { ref } from 'vue'

// Prepare fallback loading strategy
const isLoading = ref(false)

// Can toggle between Suspense and manual loading if needed
const useSuspense = true
</script>

<template>
  <!-- Document that this uses experimental API -->
  <!-- Consider: Suspense is experimental - monitor Vue releases -->
  <Suspense v-if="useSuspense">
    <RouterView />
    <template #fallback>
      <GlobalLoadingScreen />
    </template>
  </Suspense>

  <!-- Alternative loading strategy available -->
  <template v-else>
    <GlobalLoadingScreen v-if="isLoading" />
    <RouterView v-else />
  </template>
</template>

Mitigation Strategies

Isolate Suspense usage - Don't spread Suspense throughout the codebase; centralize it
Document usage - Comment where Suspense is used for easy refactoring
Test thoroughly - Suspense edge cases may behave differently across Vue versions
Follow Vue releases - Monitor changelogs for Suspense-related changes
Have a fallback plan - Be ready to implement manual loading states if needed

Key Points

Suspense has been experimental for 4+ years with no stable release date announced
Some developers find it "too buggy or too restrictive" for certain use cases
Consider Vue 2-style loading patterns as a reliable alternative for critical paths
Keep Suspense boundaries minimal and centralized for easier migration

2.5 KiB Raw Blame History