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: 下拉刷新 / 上拉加载 - 产品首页: 添加业务联系 - 文档: 清理过时文件，补充缺失规范章节
2.9 KiB
2.9 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | |||||
|---|---|---|---|---|---|---|---|---|---|
| Use Explicit Default Template When Mixing Named and Scoped Slots | HIGH | Mixing v-slot on component with named slots inside causes ambiguous scope and compilation errors | gotcha |
|
Use Explicit Default Template When Mixing Named and Scoped Slots
Impact: HIGH - When a component uses both the default scoped slot and named slots, you must use an explicit <template #default> for the default slot. Using v-slot directly on the component while having nested named slot templates causes scope ambiguity and compilation errors.
Task Checklist
- When using named slots alongside a default slot with props, always use explicit
<template #default> - Never mix
v-sloton the component element with<template #name>inside - Keep slot scope clear and unambiguous
Incorrect:
<script setup>
import MyComponent from './MyComponent.vue'
</script>
<template>
<!-- BAD: v-slot on component + named template inside causes ambiguity -->
<MyComponent v-slot="{ message }">
<p>{{ message }}</p>
<template #footer>
<!-- Ambiguous: Is 'message' available here? Vue can't determine -->
<p>Footer: {{ message }}</p>
</template>
</MyComponent>
</template>
This causes a compilation error because Vue cannot determine:
- Whether
messagefrom the default slot should be available in the footer slot - Which scope applies to the non-template content
Correct:
<script setup>
import MyComponent from './MyComponent.vue'
</script>
<template>
<!-- GOOD: Explicit template for each slot with clear scope -->
<MyComponent>
<template #default="{ message }">
<p>{{ message }}</p>
</template>
<template #footer>
<!-- Clear: footer slot has its own scope, no access to default's 'message' -->
<p>Footer content here</p>
</template>
</MyComponent>
</template>
Correct - When Footer Also Has Props:
<script setup>
import MyComponent from './MyComponent.vue'
</script>
<template>
<MyComponent>
<template #default="{ message }">
<p>{{ message }}</p>
</template>
<template #footer="{ year }">
<!-- Each slot receives its own props -->
<p>Copyright {{ year }}</p>
</template>
</MyComponent>
</template>
The Rule
When you have any named slots (<template #name>), always use explicit templates for all slots, including the default slot. This makes scope boundaries clear and prevents compilation errors.
| Pattern | Valid? | Notes |
|---|---|---|
v-slot on component only |
Yes | Single default scoped slot |
| Named templates only | Yes | Multiple named slots |
v-slot on component + named templates |
No | Ambiguous scope |
| All explicit templates | Yes | Clear scope for each slot |