- 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.8 KiB
3.8 KiB
Fallthrough Attributes Overwrite Explicit Attributes in Vue 3
Rule
In Vue 3, fallthrough attributes overwrite explicitly set attributes on the root element (except class and style which are merged). This is a breaking change from Vue 2. To preserve explicit attribute values, use inheritAttrs: false and manually bind $attrs before the explicit attribute.
Why This Matters
- Silent behavior change from Vue 2 to Vue 3
- Can cause unexpected attribute values in migrated codebases
- Only
classandstylemerge intelligently; other attributes are overwritten - Affects component composition patterns and wrapper components
Bad Code
<!-- Parent.vue -->
<template>
<Child msg="Passed from Parent" />
</template>
<!-- Child.vue - UNEXPECTED BEHAVIOR -->
<template>
<GrandChild msg="Set in Child" />
</template>
<!--
Vue 3 Result: GrandChild receives msg="Passed from Parent"
The fallthrough attribute OVERWRITES the explicit one!
Vue 2 Result: GrandChild receives msg="Set in Child"
The explicit attribute took precedence
-->
Another common case with data attributes
<!-- Parent.vue -->
<template>
<Button data-testid="parent-button" />
</template>
<!-- Button.vue - WRONG: explicit data-testid is overwritten -->
<template>
<button data-testid="submit-btn">Submit</button>
</template>
<!-- Result: <button data-testid="parent-button">Submit</button> -->
<!-- The component's intended test ID is lost! -->
Good Code
Option 1: Control attribute order with inheritAttrs: false
<!-- Child.vue - CORRECT: Control attribute precedence -->
<script setup>
defineOptions({
inheritAttrs: false
})
</script>
<template>
<!-- v-bind="$attrs" FIRST, then explicit attribute -->
<GrandChild v-bind="$attrs" msg="Set in Child" />
</template>
<!--
Result: GrandChild receives msg="Set in Child"
Explicit attribute overrides fallthrough because it comes last
-->
Option 2: Exclude specific attrs from fallthrough
<script setup>
import { computed, useAttrs } from 'vue'
defineOptions({
inheritAttrs: false
})
const attrs = useAttrs()
// Filter out attributes you want to control explicitly
const filteredAttrs = computed(() => {
const { msg, ...rest } = attrs
return rest
})
</script>
<template>
<GrandChild v-bind="filteredAttrs" msg="Set in Child" />
</template>
Option 3: For wrapper components, declare as prop
<!-- Button.vue - BEST: Declare attributes you need to control -->
<script setup>
const props = defineProps({
dataTestid: {
type: String,
default: 'submit-btn'
}
})
defineOptions({
inheritAttrs: false
})
</script>
<template>
<button :data-testid="dataTestid" v-bind="$attrs">
<slot />
</button>
</template>
Class and Style Are Special
Unlike other attributes, class and style merge rather than overwrite:
<!-- Parent.vue -->
<template>
<Button class="large" style="color: red" />
</template>
<!-- Button.vue -->
<template>
<button class="btn" style="padding: 10px">Submit</button>
</template>
<!--
Result: <button class="btn large" style="padding: 10px; color: red">
Both classes and styles are MERGED, not overwritten
-->
Vue 2 to Vue 3 Migration Checklist
When migrating components that rely on attribute precedence:
- Identify components that set explicit attributes on root elements
- Check if parent components pass the same attributes
- If explicit values should take precedence:
- Add
inheritAttrs: false - Use
v-bind="$attrs"before explicit attributes
- Add