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

Raw Blame History

name, description

name	description
vite-plugin-uni-middleware	Route middleware support for uni-app - implement guards, auth, and page lifecycle hooks

vite-plugin-uni-middleware

Add Express-style middleware support to uni-app routing. Implement authentication guards, page analytics, and custom route logic.

Installation

npm i -D @uni-helper/vite-plugin-uni-middleware

Setup

// vite.config.ts
import Uni from '@dcloudio/vite-plugin-uni'
import UniMiddleware from '@uni-helper/vite-plugin-uni-middleware'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [UniMiddleware(), Uni()],
})

Creating Middleware

Create middleware files in src/middleware/ directory:

// src/middleware/auth.ts
import { defineMiddleware } from '@uni-helper/vite-plugin-middleware'

export default defineMiddleware((to, from, next) => {
  const token = uni.getStorageSync('token')

  if (!token && to.path !== '/pages/login/index') {
    // Redirect to login
    next('/pages/login/index')
  } else {
    // Continue navigation
    next()
  }
})

// src/middleware/analytics.ts
export default defineMiddleware((to, from, next) => {
  // Track page view
  uni.report('page_view', {
    path: to.path,
    from: from.path,
    timestamp: Date.now(),
  })

  next()
})

// src/middleware/logger.ts
export default defineMiddleware((to, from, next) => {
  console.log(`[Router] ${from.path} -> ${to.path}`)
  next()
})

Applying Middleware

Via definePage (recommended)

<script setup>
definePage({
  middlewares: ['auth', 'analytics'],
})
</script>

Via pages.json

{
  "pages": [{
    "path": "pages/profile/index",
    "middlewares": ["auth"]
  }]
}

Global Middleware

Create src/middleware/index.ts for global middleware:

// src/middleware/index.ts
export default defineMiddleware((to, from, next) => {
  // Runs on every navigation
  console.log('Global middleware')
  next()
})

Middleware Context

interface MiddlewareContext {
  to: {
    path: string
    query: Record<string, string>
    meta?: Record<string, any>
  }
  from: {
    path: string
    query: Record<string, string>
  }
  next: (path?: string) => void
}

Middleware Order

Middleware executes in declaration order:

<script setup>
definePage({
  // Runs: logger -> auth -> analytics
  middlewares: ['logger', 'auth', 'analytics'],
})
</script>

export default defineMiddleware((to, from, next) => {
  // Continue to route
  next()

  // Redirect to different route
  next('/pages/other/index')

  // Redirect with query
  next({
    path: '/pages/login/index',
    query: { redirect: to.path },
  })

  // Cancel navigation (stay on current page)
  next(false)
})

Async Middleware

export default defineMiddleware(async (to, from, next) => {
  try {
    const user = await fetchUserInfo()

    if (user.isBanned) {
      next('/pages/banned/index')
    } else {
      next()
    }
  } catch (error) {
    next('/pages/error/index')
  }
})

3.2 KiB Raw Blame History