- 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.3 KiB
4.3 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | ||||
|---|---|---|---|---|---|---|---|---|
| Do Not Rely on Internal VNode Properties | MEDIUM | Using undocumented vnode properties causes code to break on Vue updates | gotcha |
|
Do Not Rely on Internal VNode Properties
Impact: MEDIUM - The VNode interface contains many internal properties used by Vue's rendering system. Relying on any properties other than the documented public ones will cause your code to break when Vue's internal implementation changes.
Only use the documented vnode properties: type, props, children, and key. All other properties are internal implementation details that may change without notice between Vue versions.
Task Checklist
- Only access documented vnode properties:
type,props,children,key - Never access properties like
el,component,shapeFlag,patchFlag, etc. - If you need DOM element access, use template refs instead
- Treat vnodes as opaque data structures for rendering, not inspection
Incorrect:
import { h } from 'vue'
export default {
setup(props, { slots }) {
return () => {
const slotContent = slots.default?.()
// WRONG: Accessing internal properties
if (slotContent?.[0]?.el) {
// el is an internal property
console.log(slotContent[0].el.tagName)
}
// WRONG: Using shapeFlag internal property
if (slotContent?.[0]?.shapeFlag & 1) {
// This is internal implementation
}
return h('div', slotContent)
}
}
}
// WRONG: Inspecting component instance via vnode
const vnode = h(MyComponent)
console.log(vnode.component) // Internal property
console.log(vnode.appContext) // Internal property
Correct:
import { h } from 'vue'
export default {
setup(props, { slots }) {
return () => {
const slotContent = slots.default?.()
// CORRECT: Only use documented properties
if (slotContent?.[0]) {
const vnode = slotContent[0]
console.log(vnode.type) // Safe: element type or component
console.log(vnode.props) // Safe: props object
console.log(vnode.children) // Safe: children
console.log(vnode.key) // Safe: key prop
}
return h('div', slotContent)
}
}
}
import { h, ref, onMounted } from 'vue'
export default {
setup() {
// CORRECT: Use template refs for DOM access
const divRef = ref(null)
onMounted(() => {
// Safe way to access DOM element
console.log(divRef.value.tagName)
})
return () => h('div', { ref: divRef }, 'Content')
}
}
Documented VNode Properties
| Property | Type | Description |
|---|---|---|
type |
string | Component |
Element tag name or component definition |
props |
object | null |
Props passed to the vnode |
children |
any |
Child vnodes, text, or slots |
key |
string | number | null |
Key for list rendering |
Safe VNode Inspection Patterns
import { h, isVNode } from 'vue'
export default {
setup(props, { slots }) {
return () => {
const children = slots.default?.() || []
// Safe: Check if something is a vnode
children.forEach(child => {
if (isVNode(child)) {
// Safe: Check vnode type
if (typeof child.type === 'string') {
console.log('Element:', child.type)
} else if (typeof child.type === 'object') {
console.log('Component:', child.type.name)
}
// Safe: Read props
if (child.props?.class) {
console.log('Has class:', child.props.class)
}
}
})
return h('div', children)
}
}
}
Why This Matters
Vue's internal vnode structure may change for:
- Performance optimizations
- New feature implementations
- Bug fixes
- Tree-shaking improvements
Code relying on internal properties will break silently or throw errors when upgrading Vue versions. The documented properties are part of Vue's public API and are guaranteed to remain stable.