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.7 KiB

Raw Blame History

title, impact, impactDescription, type, tags

title

impact

impactDescription

type

Prefer ref() Over reactive() for Consistency

Impact: MEDIUM - The Vue documentation recommends using ref() as the primary API for declaring reactive state. This avoids several reactive() gotchas and provides a consistent pattern across your codebase.

While both ref() and reactive() create reactive state, reactive() has several limitations: it only works with objects (not primitives), cannot be reassigned, and loses reactivity when destructured. Using ref() consistently means one pattern to remember.

Task Checklist

Use ref() as the default for all reactive state
Only use reactive() when you have a specific reason (e.g., group of related state)
Be consistent within a codebase - pick one approach and stick with it
Remember: .value is the price for avoiding reactive() gotchas

Incorrect:

import { reactive } from 'vue'

// reactive() has multiple gotchas:

// 1. Cannot use with primitives
const count = reactive(0)  // Won't work - not reactive

// 2. Cannot reassign the entire object
let state = reactive({ items: [] })
state = reactive({ items: [1, 2, 3] })  // Loses reactivity!

// 3. Destructuring breaks reactivity
const { items } = state  // items is not reactive

// 4. Passing to functions can lose reactivity
someFunction(state.items)  // May lose reactivity depending on usage

Correct:

import { ref } from 'vue'

// ref() works universally:

// 1. Works with primitives
const count = ref(0)
count.value++  // Works!

// 2. Can reassign the entire object
const state = ref({ items: [] })
state.value = { items: [1, 2, 3] }  // Reactivity preserved!

// 3. No destructuring issues (you work with .value)
const items = state.value.items  // If you need just the value

// 4. Passing refs is explicit
someFunction(state)        // Pass the ref
someFunction(state.value)  // Or pass the value explicitly

// When reactive() makes sense: grouping related state
import { reactive, toRefs } from 'vue'

// Acceptable use case: form state with many related fields
const form = reactive({
  username: '',
  email: '',
  password: '',
  confirmPassword: ''
})

// But always use toRefs() if you need to destructure
const { username, email } = toRefs(form)

2.7 KiB Raw Blame History

Prefer ref() Over reactive() for Consistency

Task Checklist

Reference

2.7 KiB

Raw Blame History