- 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 | |||||
|---|---|---|---|---|---|---|---|---|---|
| Props Are Validated Before Component Instance Creation | MEDIUM | Instance properties like data and computed are unavailable in prop default/validator functions | gotcha |
|
Props Are Validated Before Component Instance Creation
Impact: MEDIUM - Prop validation and default value functions execute before the component instance is created. This means this, data, computed, injections, and other instance properties are not available inside default or validator functions.
This timing catches developers who expect to use component state in prop validation logic.
Task Checklist
- Never reference
thisor instance properties in prop default/validator functions - Use factory functions for object/array defaults that only use the function parameters
- For validation depending on other props, use the second
propsparameter in validators - Move complex validation logic to watchers or lifecycle hooks if instance access is needed
Incorrect:
<script>
export default {
data() {
return {
validOptions: ['a', 'b', 'c'],
defaultMessage: 'Hello'
}
},
props: {
option: {
type: String,
// WRONG: 'this' is undefined during prop validation
validator(value) {
return this.validOptions.includes(value) // TypeError!
}
},
message: {
type: String,
// WRONG: Cannot access data properties
default() {
return this.defaultMessage // TypeError!
}
},
config: {
type: Object,
// WRONG: Cannot access computed properties
default() {
return this.computedDefaults // TypeError!
}
}
}
}
</script>
Correct:
<script>
// Define validation data outside the component
const VALID_OPTIONS = ['a', 'b', 'c']
const DEFAULT_MESSAGE = 'Hello'
export default {
props: {
option: {
type: String,
// CORRECT: Use external constants
validator(value) {
return VALID_OPTIONS.includes(value)
}
},
message: {
type: String,
// CORRECT: Use external constant or inline value
default: DEFAULT_MESSAGE
},
config: {
type: Object,
// CORRECT: Factory function with no instance dependencies
default() {
return { theme: 'light', size: 'medium' }
}
}
}
}
</script>
Using the props Parameter in Validators
Validators receive the full props object as the second parameter for cross-prop validation:
<script setup>
const props = defineProps({
min: {
type: Number,
default: 0
},
max: {
type: Number,
default: 100
},
value: {
type: Number,
required: true,
// CORRECT: Access other props via second parameter
validator(value, props) {
return value >= props.min && value <= props.max
}
}
})
</script>
Using rawProps in Default Functions
Default factory functions receive rawProps for accessing other prop values:
<script setup>
defineProps({
size: {
type: String,
default: 'medium'
},
padding: {
type: Number,
// Access other prop values via rawProps parameter
default(rawProps) {
// Use size to determine default padding
return rawProps.size === 'large' ? 20 : 10
}
}
})
</script>
Post-Mount Validation Pattern
For validation that needs instance access, use lifecycle hooks:
<script setup>
import { onMounted, inject, warn } from 'vue'
const props = defineProps({
theme: String
})
const availableThemes = inject('availableThemes', [])
// Validation that needs injected values
onMounted(() => {
if (props.theme && !availableThemes.includes(props.theme)) {
console.warn(`Invalid theme "${props.theme}". Available: ${availableThemes.join(', ')}`)
}
})
</script>