- 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.9 KiB
3.9 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wrap Destructured Props in Getters for watch and Composables | MEDIUM | Passing destructured prop values directly to watch or composables loses reactivity | gotcha |
|
Wrap Destructured Props in Getters for watch and Composables
Impact: MEDIUM - When you destructure props with defineProps, the destructured variables are reactive in templates but passing them directly to watch() or external composables will pass the current value, not a reactive source. The watcher or composable won't track future changes.
Vue 3.5+ automatically transforms destructured props for template reactivity, but external functions still need getter wrappers.
Task Checklist
- Wrap destructured props in arrow functions when passing to
watch() - Use getter functions when passing destructured props to composables
- Verify composables use
toValue()to normalize getter/ref inputs - Consider using
props.propertyNamedirectly if getter syntax feels awkward
Incorrect:
<script setup>
import { watch } from 'vue'
import { useDebounce } from './composables'
const { searchQuery, userId } = defineProps(['searchQuery', 'userId'])
// WRONG: Passing value, not reactive source
// This captures the initial value only - changes won't trigger the watcher
watch(searchQuery, (newValue) => {
console.log('Query changed:', newValue) // Never fires after initial!
})
// WRONG: Composable receives static value
const debouncedQuery = useDebounce(searchQuery, 300) // Won't update
</script>
Correct:
<script setup>
import { watch } from 'vue'
import { useDebounce } from './composables'
const { searchQuery, userId } = defineProps(['searchQuery', 'userId'])
// CORRECT: Wrap in getter function to maintain reactivity
watch(() => searchQuery, (newValue) => {
console.log('Query changed:', newValue) // Fires on every change
})
// CORRECT: Pass getter to composable
const debouncedQuery = useDebounce(() => searchQuery, 300)
</script>
Alternative: Use props Object Directly
<script setup>
import { watch } from 'vue'
const props = defineProps(['searchQuery', 'userId'])
// Also correct: Watch via props object (no getter needed)
watch(() => props.searchQuery, (newValue) => {
console.log('Query changed:', newValue)
})
// Watch multiple props
watch(
() => [props.searchQuery, props.userId],
([newQuery, newUserId]) => {
console.log('Props changed:', newQuery, newUserId)
}
)
</script>
Writing Composables That Accept Props
When creating composables that should work with destructured props:
// composables/useDebounce.js
import { ref, watch, toValue } from 'vue'
export function useDebounce(source, delay = 300) {
const debounced = ref(toValue(source)) // toValue handles both getter and ref
let timeout
watch(
// toValue normalizes getter functions and refs
() => toValue(source),
(newValue) => {
clearTimeout(timeout)
timeout = setTimeout(() => {
debounced.value = newValue
}, delay)
}
)
return debounced
}
<!-- Usage -->
<script setup>
const { query } = defineProps(['query'])
// Works with getter
const debouncedQuery = useDebounce(() => query, 300)
</script>
Vue 3.5+ Reactive Destructuring
Vue 3.5+ added reactive props destructuring. The compiler transforms:
const { foo } = defineProps(['foo'])
Into something like:
const __props = defineProps(['foo'])
// foo accesses __props.foo reactively in templates
However, external function calls still need getters because JavaScript itself passes values, not references.