12451 b553c4e519 feat: API 统一 + 设备详情补全 + H5 导航优化
- 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: 下拉刷新 / 上拉加载
- 产品首页: 添加业务联系
- 文档: 清理过时文件,补充缺失规范章节
2026-07-04 04:03:02 +08:00

3.6 KiB

title, impact, impactDescription, type, tags
title impact impactDescription type tags
Slot Content Only Has Access to Parent Component Scope HIGH Attempting to access child component data in slot content results in undefined values or errors gotcha
vue3
slots
scope
reactivity
common-mistake

Slot Content Only Has Access to Parent Component Scope

Impact: HIGH - Slot content is compiled in the parent component's scope and cannot access data defined in the child component. This follows JavaScript's lexical scoping rules and is a common source of confusion.

When you provide content for a slot, that content is defined in your parent template and can only access data available in the parent component. The child component's internal state is not accessible unless explicitly passed via scoped slots.

Task Checklist

  • Remember that slot content is compiled in parent scope
  • Never try to access child component data directly in slot content
  • Use scoped slots when child data needs to be exposed to parent
  • Check that all template expressions reference data available in the current component

Incorrect:

<!-- Parent.vue -->
<script setup>
import SubmitButton from './SubmitButton.vue'
</script>

<template>
  <!-- BAD: Trying to access child's buttonText - this will be undefined -->
  <SubmitButton>{{ buttonText }}</SubmitButton>

  <!-- BAD: Trying to access child's isLoading state -->
  <SubmitButton>
    <span v-if="isLoading">Loading...</span>
    <span v-else>Submit</span>
  </SubmitButton>
</template>
<!-- SubmitButton.vue (Child) -->
<script setup>
import { ref } from 'vue'

const buttonText = ref('Click me')  // Not accessible in parent's slot content
const isLoading = ref(false)        // Not accessible in parent's slot content
</script>

<template>
  <button>
    <slot></slot>
  </button>
</template>

Correct - Use Scoped Slots:

<!-- SubmitButton.vue (Child) - Expose data via slot props -->
<script setup>
import { ref } from 'vue'

const buttonText = ref('Click me')
const isLoading = ref(false)
</script>

<template>
  <button>
    <!-- Pass child data as slot props -->
    <slot :text="buttonText" :loading="isLoading"></slot>
  </button>
</template>
<!-- Parent.vue -->
<script setup>
import SubmitButton from './SubmitButton.vue'
</script>

<template>
  <!-- GOOD: Receive child data via scoped slot -->
  <SubmitButton v-slot="{ text, loading }">
    <span v-if="loading">Loading...</span>
    <span v-else>{{ text }}</span>
  </SubmitButton>
</template>

Correct - Use Parent Data:

<!-- Parent.vue -->
<script setup>
import { ref } from 'vue'
import SubmitButton from './SubmitButton.vue'

// Define data in parent where slot content is compiled
const message = ref('Submit Form')
const isSubmitting = ref(false)
</script>

<template>
  <!-- GOOD: Using parent's own data in slot content -->
  <SubmitButton>
    <span v-if="isSubmitting">Processing...</span>
    <span v-else>{{ message }}</span>
  </SubmitButton>
</template>

The Function Analogy

Think of slots as function parameters:

// Slot content is like a callback defined in parent scope
function Parent() {
  const parentData = 'Hello'

  // This callback can only see parentData, not childData
  Child((slotProps) => {
    return parentData + (slotProps?.text || '')
  })
}

function Child(slotCallback) {
  const childData = 'World'  // Not visible to callback

  // Must explicitly pass data via slot props
  return slotCallback({ text: childData })
}

Reference