- 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.6 KiB
3.6 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| v-model.number Uses parseFloat Not valueAsNumber | MEDIUM | .number modifier returns empty string for empty input and uses parseFloat, not native valueAsNumber | capability |
|
v-model.number Uses parseFloat Not valueAsNumber
Impact: MEDIUM - The .number modifier doesn't behave like the native valueAsNumber property. It returns an empty string (not NaN) for empty inputs, and uses parseFloat() which has different parsing rules. This can cause unexpected type issues in calculations and validations.
Understanding these differences is crucial when working with numeric forms, especially for calculations, min/max validation, or when interfacing with APIs that expect strict number types.
Task Checklist
- Expect empty string (not 0 or NaN) when input is cleared with
.numbermodifier - Handle the empty string case in your validation and calculations
- Remember
.numberuses parseFloat - "123abc" becomes 123, not NaN - For strict numeric parsing, add custom validation
Key Differences:
| Scenario | .number modifier |
Native valueAsNumber |
|---|---|---|
| Empty input | '' (empty string) |
NaN |
"123" |
123 |
123 |
"123.45" |
123.45 |
123.45 |
"123abc" |
123 |
NaN |
"abc" |
'abc' (original string) |
NaN |
Problem - Unexpected types:
<script setup>
import { ref, computed } from 'vue'
const price = ref(0)
const quantity = ref(1)
const total = computed(() => {
// PROBLEM: price might be '' (empty string) when input is cleared
return price.value * quantity.value // '' * 1 = 0, but typeof is still number
})
function validatePrice() {
// PROBLEM: This check fails when input is empty
if (typeof price.value !== 'number') {
// Never enters here! '' is still treated as "processed"
}
// PROBLEM: parseFloat("$100") returns NaN, but "100abc" returns 100
}
</script>
<template>
<input v-model.number="price" type="number">
<!-- When user clears input, price.value becomes '' not 0 or NaN -->
</template>
Solution - Handle empty string explicitly:
<script setup>
import { ref, computed } from 'vue'
const price = ref(0)
const quantity = ref(1)
const total = computed(() => {
// CORRECT: Handle empty string case
const priceNum = price.value === '' ? 0 : price.value
return priceNum * quantity.value
})
// Or use a wrapper computed for safer access
const safePrice = computed(() => {
if (price.value === '' || price.value === null) return 0
return Number(price.value) || 0
})
</script>
<template>
<input v-model.number="price" type="number" min="0">
<p>Total: ${{ total.toFixed(2) }}</p>
</template>
Solution - Custom input handling for strict parsing:
<script setup>
import { ref } from 'vue'
const price = ref(0)
function handlePriceInput(event) {
const value = event.target.value
// Strict parsing - only accept valid numbers
const parsed = parseFloat(value)
if (value === '') {
price.value = 0 // Or null, depending on your needs
} else if (!isNaN(parsed) && isFinite(parsed)) {
// Additional check: ensure entire string is numeric
if (/^-?\d*\.?\d+$/.test(value.trim())) {
price.value = parsed
}
}
// Invalid input - keep previous value
}
</script>
<template>
<!-- Manual binding for strict numeric control -->
<input
:value="price"
@input="handlePriceInput"
type="number"
>
</template>