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.5 KiB

Raw Blame History

title, impact, impactDescription, type, tags

title

impact

impactDescription

type

Use immediate Option Instead of Duplicate Initial Call

Impact: LOW - Calling a function manually at setup and also in a watcher leads to duplicate code. The immediate: true option runs the watcher callback immediately with the current value, combining both behaviors.

Task Checklist

Use { immediate: true } instead of calling handler in onMounted/created
Consider watchEffect as an alternative (always runs immediately)
Remember immediate callback receives undefined as oldValue on first run

Incorrect:

<script setup>
import { ref, watch, onMounted } from 'vue'

const userId = ref(1)
const userData = ref(null)

// BAD: Duplicate calls - once in onMounted, once in watch
async function loadUser(id) {
  const response = await fetch(`/api/users/${id}`)
  userData.value = await response.json()
}

onMounted(() => {
  loadUser(userId.value)  // Initial call
})

watch(userId, (newId) => {
  loadUser(newId)  // On change
})
</script>

// Options API - BAD: Duplicate in created and watch
export default {
  data() {
    return { userId: 1, userData: null }
  },
  created() {
    this.loadUser()  // Initial call
  },
  watch: {
    userId() {
      this.loadUser()  // On change - duplicate!
    }
  },
  methods: {
    async loadUser() {
      const response = await fetch(`/api/users/${this.userId}`)
      this.userData = await response.json()
    }
  }
}

Correct:

<script setup>
import { ref, watch } from 'vue'

const userId = ref(1)
const userData = ref(null)

// GOOD: Single watch with immediate runs on mount and on change
watch(
  userId,
  async (newId) => {
    const response = await fetch(`/api/users/${newId}`)
    userData.value = await response.json()
  },
  { immediate: true }
)
</script>

// Options API - GOOD: Using immediate option
export default {
  data() {
    return { userId: 1, userData: null }
  },
  watch: {
    userId: {
      async handler(newId) {
        const response = await fetch(`/api/users/${newId}`)
        this.userData = await response.json()
      },
      immediate: true
    }
  }
}

Alternative: watchEffect

<script setup>
import { ref, watchEffect } from 'vue'

const userId = ref(1)
const userData = ref(null)

// watchEffect always runs immediately - no option needed
watchEffect(async () => {
  const response = await fetch(`/api/users/${userId.value}`)
  userData.value = await response.json()
})
</script>

Handling oldValue on Initial Run

<script setup>
import { ref, watch } from 'vue'

const count = ref(0)

watch(
  count,
  (newVal, oldVal) => {
    // On first run with immediate: true
    // oldVal is undefined
    if (oldVal === undefined) {
      console.log('Initial run, count is:', newVal)
    } else {
      console.log(`Count changed from ${oldVal} to ${newVal}`)
    }
  },
  { immediate: true }
)
</script>

One-Time Watch with once Option

<script setup>
import { ref, watch } from 'vue'

const data = ref(null)

// Run only once when data becomes available
watch(
  data,
  (value) => {
    if (value) {
      initializeWithData(value)
      // Watcher automatically stops after this
    }
  },
  { once: true }
)
</script>

Reference

Vue.js Watchers - Eager Watchers

3.5 KiB Raw Blame History