b553c4e519
- 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: 下拉刷新 / 上拉加载 - 产品首页: 添加业务联系 - 文档: 清理过时文件，补充缺失规范章节
3.1 KiB
3.1 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | |||||
|---|---|---|---|---|---|---|---|---|---|
| Template Ref Unwrapping Only Works for Top-Level Properties | MEDIUM | Nested refs in template expressions render as [object Object] instead of their values | capability |
|
Template Ref Unwrapping Only Works for Top-Level Properties
Impact: MEDIUM - Vue only auto-unwraps refs that are top-level properties in the template render context. Nested refs (refs inside objects) are NOT unwrapped in expressions, causing [object Object] rendering or calculation errors.
This caveat trips up developers when they store refs inside reactive objects or plain objects and try to use them in template expressions like {{ object.count + 1 }}.
Task Checklist
- Keep refs at the top level of your setup return or script setup
- Destructure nested refs to top-level variables before using in expressions
- Be aware that text interpolation
{{ object.ref }}DOES unwrap, but expressions{{ object.ref + 1 }}do NOT - Consider restructuring data to avoid nested refs in templates
Incorrect:
<script setup>
import { ref } from 'vue'
const count = ref(0)
const object = { id: ref(1) }
</script>
<template>
<!-- WRONG: Nested ref in expression - does NOT unwrap -->
<p>ID + 1 = {{ object.id + 1 }}</p>
<!-- Renders: "ID + 1 = [object Object]1" -->
<!-- Surprisingly, plain interpolation DOES work -->
<p>ID = {{ object.id }}</p>
<!-- Renders: "ID = 1" (unwrapped because it's the final expression) -->
</template>
Correct:
<script setup>
import { ref } from 'vue'
const count = ref(0)
const object = { id: ref(1) }
// SOLUTION 1: Destructure to top-level
const { id } = object
</script>
<template>
<!-- CORRECT: Top-level ref unwraps in all expressions -->
<p>Count + 1 = {{ count + 1 }}</p>
<!-- Renders: "Count + 1 = 1" -->
<!-- CORRECT: Destructured ref is now top-level -->
<p>ID + 1 = {{ id + 1 }}</p>
<!-- Renders: "ID + 1 = 2" -->
</template>
<script setup>
import { ref, computed } from 'vue'
const object = { id: ref(1) }
// SOLUTION 2: Use computed for derived values
const idPlusOne = computed(() => object.id.value + 1)
</script>
<template>
<!-- CORRECT: Computed handles the .value access -->
<p>ID + 1 = {{ idPlusOne }}</p>
</template>
<script setup>
import { reactive } from 'vue'
// SOLUTION 3: Use reactive object instead (refs inside reactive auto-unwrap)
const object = reactive({ id: 1 })
</script>
<template>
<!-- CORRECT: Plain reactive property works in expressions -->
<p>ID + 1 = {{ object.id + 1 }}</p>
</template>
// WHY this happens:
// - Template compilation only adds .value to top-level identifiers
// - {{ count + 1 }} compiles to: count.value + 1
// - {{ object.id + 1 }} compiles to: object.id + 1 (no .value added!)
// - Plain {{ object.id }} has special handling for display purposes