Compare commits
34 Commits
868a3352ad
...
main
| Author | SHA1 | Date | |
|---|---|---|---|
|
db7b3562da | ||
|
|
f52970ae6c | ||
|
|
2c8524485b | ||
|
|
4c0207c6e6 | ||
|
|
5b8d6610ab | ||
|
|
a036b10641 | ||
|
|
c1a7118d35 | ||
|
|
f27bbacb1e | ||
|
|
acda0d82c8 | ||
| 99de03604d | |||
| 1baa6d87cf | |||
| f604791c69 | |||
| cfb6b52cc2 | |||
| 0c3065f970 | |||
|
|
ebf9739f06 | ||
|
|
d3b5f55c64 | ||
| 866a2587b3 | |||
| 85d158dfec | |||
| 2a8f4e40d6 | |||
|
|
908367ba5d | ||
|
|
2ecab976f5 | ||
|
|
e04a283319 | ||
|
|
d23e896f97 | ||
|
|
c5e4082c26 | ||
|
|
0c737a30c1 | ||
|
|
c5dae2993b | ||
|
|
3e6b3981f4 | ||
|
|
e563b81b6e | ||
|
|
322cd0dca5 | ||
|
|
ad56b82944 | ||
|
|
f62a8d98a4 | ||
|
|
76a526643e | ||
|
|
9ce48f1714 | ||
|
|
a162dcc650 |
@@ -19,7 +19,9 @@
|
||||
"Bash(findstr:*)",
|
||||
"Bash(npm run:*)",
|
||||
"Bash(find src/views -name *.vue -type f -exec grep -l \"device.*detail\\\\|设备详情\" {})",
|
||||
"Bash(2)"
|
||||
"Bash(2)",
|
||||
"Bash(grep -E \"\\\\.\\(vue|ts\\)$\")",
|
||||
"Bash(xargs grep:*)"
|
||||
],
|
||||
"deny": [],
|
||||
"ask": []
|
||||
|
||||
9
.gitignore
vendored
9
.gitignore
vendored
@@ -21,3 +21,12 @@ dist-ssr
|
||||
# Logs
|
||||
*.log
|
||||
npminstall-debug.log
|
||||
|
||||
# plan
|
||||
.scratch
|
||||
|
||||
# ai
|
||||
.agents
|
||||
|
||||
#build
|
||||
one-pipe-system-dist.zip
|
||||
|
||||
14
CLAUDE.md
14
CLAUDE.md
@@ -19,3 +19,17 @@ Use `@/openspec/AGENTS.md` to learn:
|
||||
Keep this managed block so 'openspec update' can refresh the instructions.
|
||||
|
||||
<!-- OPENSPEC:END -->
|
||||
|
||||
## Agent skills
|
||||
|
||||
### Issue tracker
|
||||
|
||||
Issues and PRDs are tracked as local markdown files under `.scratch/`; external PRs are not a triage surface. See `docs/agents/issue-tracker.md`.
|
||||
|
||||
### Triage labels
|
||||
|
||||
Uses the default triage state vocabulary: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. See `docs/agents/triage-labels.md`.
|
||||
|
||||
### Domain docs
|
||||
|
||||
Uses a single-context domain documentation layout. See `docs/agents/domain.md`.
|
||||
|
||||
21
CONTEXT.md
Normal file
21
CONTEXT.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# One Pipe System
|
||||
|
||||
This context captures the business language used by the admin system for orders, assets, finance operations, and operational batch tasks.
|
||||
|
||||
## Language
|
||||
|
||||
**Voucher attachment**: A user-provided proof file attached to an order, refund, recharge, or operational task. Voucher attachments may contain any file type and a business record may hold multiple voucher attachment keys. _Avoid_: Voucher image, comma-separated voucher string
|
||||
|
||||
**Voucher key list**: The canonical representation of voucher attachment object-storage keys at the frontend and API submission boundary. Legacy single-key strings or comma-separated strings may be read and normalized for display, but new submissions use key lists. _Avoid_: Comma-separated voucher string
|
||||
|
||||
**Batch import file**: The structured data file that drives an asynchronous operational batch task. Unlike voucher attachments, a batch import file is constrained by the task's required template format. _Avoid_: Voucher, attachment
|
||||
|
||||
**Operational batch task**: An asynchronous admin task created from an uploaded batch import file and tracked through task status, counts, operator identity, and failure details. _Avoid_: Inline order operation, synchronous import
|
||||
|
||||
**Operational remark**: A note captured when an admin creates a financial or operational record. Operational remarks are retained for later review and are not edited after creation. _Avoid_: Editable comment, processing note
|
||||
|
||||
**Recharge order**: A C-side asset recharge order created when a user recharges an IoT card or device asset wallet. It is identified by `recharge_order_no`, is associated with `resource_type` and `resource_id`, and may be rejected while pending payment. _Avoid_: Agent recharge order
|
||||
|
||||
**Rejected recharge order**: A recharge order that an admin has rejected before payment because the recharge request should not proceed. Rejection is an irreversible terminal state and does not involve refunds. _Avoid_: Refunded recharge, closed recharge
|
||||
|
||||
**Agent recharge order**: A financial recharge record for an agent/shop wallet in the admin finance module. It uses a different API contract and status model from C-side recharge orders. _Avoid_: Recharge order
|
||||
1
components.d.ts
vendored
1
components.d.ts
vendored
@@ -14,7 +14,6 @@ declare module 'vue' {
|
||||
ArtBreadcrumb: typeof import('./src/components/core/layouts/art-breadcrumb/index.vue')['default']
|
||||
ArtButtonMore: typeof import('./src/components/core/forms/ArtButtonMore.vue')['default']
|
||||
ArtButtonTable: typeof import('./src/components/core/forms/ArtButtonTable.vue')['default']
|
||||
ArtCardBanner: typeof import('./src/components/core/banners/ArtCardBanner.vue')['default']
|
||||
ArtChatWindow: typeof import('./src/components/core/layouts/art-chat-window/index.vue')['default']
|
||||
ArtCutterImg: typeof import('./src/components/core/media/ArtCutterImg.vue')['default']
|
||||
ArtDataListCard: typeof import('./src/components/core/cards/ArtDataListCard.vue')['default']
|
||||
|
||||
343
docs/API对接说明.md
343
docs/API对接说明.md
@@ -1,343 +0,0 @@
|
||||
# API 对接说明
|
||||
|
||||
> 更新时间: 2026-01-09
|
||||
|
||||
---
|
||||
|
||||
## ✅ 已完成的修改
|
||||
|
||||
### 1. 创建了认证 API 服务
|
||||
**文件**: `src/api/authApi.ts`
|
||||
|
||||
```typescript
|
||||
import { AuthService } from '@/api/authApi'
|
||||
|
||||
// 登录
|
||||
AuthService.login({ username, password, remember })
|
||||
|
||||
// 获取用户信息
|
||||
AuthService.getUserInfo()
|
||||
|
||||
// 登出
|
||||
AuthService.logout()
|
||||
|
||||
// 刷新Token
|
||||
AuthService.refreshToken(refreshToken)
|
||||
```
|
||||
|
||||
### 2. 修改了登录逻辑
|
||||
**文件**: `src/composables/useLogin.ts`
|
||||
|
||||
**关键修改**:
|
||||
- ✅ 添加了 `USE_MOCK` 开关（第 29 行）
|
||||
- ✅ 创建了 `handleRealLogin()` 真实API登录函数
|
||||
- ✅ 保留了 `handleMockLogin()` Mock登录函数（方便开发测试）
|
||||
|
||||
**切换方式**:
|
||||
```typescript
|
||||
// 文件: src/composables/useLogin.ts 第 29 行
|
||||
|
||||
// 使用 Mock 数据（开发测试）
|
||||
const USE_MOCK = true
|
||||
|
||||
// 使用真实 API（生产环境）
|
||||
const USE_MOCK = false // ← 当前设置
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔌 API 接口规范
|
||||
|
||||
### 登录接口
|
||||
|
||||
**请求地址**: `POST /api/auth/login`
|
||||
|
||||
**请求参数**:
|
||||
```typescript
|
||||
{
|
||||
username: string // 用户名
|
||||
password: string // 密码
|
||||
remember?: boolean // 是否记住密码
|
||||
captcha?: string // 验证码（可选）
|
||||
}
|
||||
```
|
||||
|
||||
**响应格式**:
|
||||
```typescript
|
||||
{
|
||||
code: number // 状态码：200 成功
|
||||
message: string // 消息
|
||||
data: {
|
||||
token: string // 访问令牌 (必需)
|
||||
refreshToken?: string // 刷新令牌 (可选)
|
||||
expiresIn?: number // 过期时间(秒) (可选)
|
||||
userInfo: { // 用户信息 (推荐返回，避免二次请求)
|
||||
id: string | number
|
||||
username: string
|
||||
realName: string
|
||||
roles: string[] // 角色列表 ['R_SUPER', 'R_ADMIN', ...]
|
||||
permissions: string[] // 权限列表 ['*:*:*', 'user:edit', ...]
|
||||
avatar?: string
|
||||
email?: string
|
||||
phone?: string
|
||||
// ... 其他用户信息
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 获取用户信息接口
|
||||
|
||||
**请求地址**: `GET /api/auth/userInfo`
|
||||
|
||||
**请求头**:
|
||||
```
|
||||
Authorization: Bearer {token}
|
||||
```
|
||||
|
||||
**响应格式**:
|
||||
```typescript
|
||||
{
|
||||
code: 200,
|
||||
message: 'success',
|
||||
data: {
|
||||
id: string | number
|
||||
username: string
|
||||
realName: string
|
||||
roles: string[]
|
||||
permissions: string[]
|
||||
avatar?: string
|
||||
email?: string
|
||||
phone?: string
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔐 权限控制说明
|
||||
|
||||
### 角色定义
|
||||
系统预定义了以下角色（可根据需求调整）：
|
||||
|
||||
```typescript
|
||||
enum UserRole {
|
||||
SUPER_ADMIN = 'R_SUPER', // 超级管理员
|
||||
ADMIN = 'R_ADMIN', // 管理员
|
||||
AGENT = 'R_AGENT', // 代理商
|
||||
ENTERPRISE = 'R_ENTERPRISE' // 企业客户
|
||||
}
|
||||
```
|
||||
|
||||
### 权限格式
|
||||
权限使用通配符格式：`模块:操作:范围`
|
||||
|
||||
**示例**:
|
||||
- `*:*:*` - 所有权限
|
||||
- `user:*:*` - 用户模块所有权限
|
||||
- `user:edit:*` - 用户编辑权限
|
||||
- `card:view:own` - 查看自己的卡
|
||||
|
||||
### 前端权限验证
|
||||
|
||||
**路由级权限**（在 `asyncRoutes.ts` 中配置）:
|
||||
```typescript
|
||||
{
|
||||
path: '/system/user',
|
||||
meta: {
|
||||
roles: ['R_SUPER', 'R_ADMIN'] // 只有超管和管理员可访问
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**按钮级权限**（使用 `v-auth` 指令）:
|
||||
```vue
|
||||
<el-button v-auth="'user:edit'">编辑</el-button>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📦 状态码规范
|
||||
|
||||
**推荐使用的状态码** (已在 `src/utils/http/status.ts` 定义):
|
||||
|
||||
```typescript
|
||||
export enum ApiStatus {
|
||||
success = 200, // 成功
|
||||
unauthorized = 401, // 未授权
|
||||
forbidden = 403, // 禁止访问
|
||||
notFound = 404, // 未找到
|
||||
serverError = 500 // 服务器错误
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🚀 快速上手
|
||||
|
||||
### 1. 配置API地址
|
||||
|
||||
**文件**: `.env.development`
|
||||
|
||||
```env
|
||||
# API 地址前缀
|
||||
VITE_API_URL = http://your-backend-api.com
|
||||
|
||||
# 或者使用代理（推荐）
|
||||
VITE_API_URL = /api
|
||||
```
|
||||
|
||||
**文件**: `vite.config.ts` (如果使用代理)
|
||||
|
||||
```typescript
|
||||
server: {
|
||||
proxy: {
|
||||
'/api': {
|
||||
target: 'http://your-backend-api.com', // 后端地址
|
||||
changeOrigin: true,
|
||||
rewrite: (path) => path.replace(/^\/api/, '')
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 2. 切换到真实API
|
||||
|
||||
**文件**: `src/composables/useLogin.ts` 第 29 行
|
||||
|
||||
```typescript
|
||||
const USE_MOCK = false // 改为 false
|
||||
```
|
||||
|
||||
### 3. 测试登录
|
||||
|
||||
1. 启动开发服务器：`npm run dev`
|
||||
2. 访问登录页面：`http://localhost:3006/#/auth/login`
|
||||
3. 输入后端提供的测试账号密码
|
||||
4. 点击登录
|
||||
|
||||
---
|
||||
|
||||
## 🔧 调试技巧
|
||||
|
||||
### 1. 查看请求/响应
|
||||
|
||||
打开浏览器开发者工具（F12）→ Network 标签，查看：
|
||||
- 请求URL
|
||||
- 请求参数
|
||||
- 响应数据
|
||||
- 状态码
|
||||
|
||||
### 2. Mock 和真实API切换
|
||||
|
||||
```typescript
|
||||
// src/composables/useLogin.ts
|
||||
|
||||
const USE_MOCK = true // 开发时使用 Mock
|
||||
const USE_MOCK = false // 对接时使用真实 API
|
||||
```
|
||||
|
||||
### 3. Token 检查
|
||||
|
||||
打开浏览器控制台（F12）→ Application → Local Storage → 查看 `user` 键：
|
||||
```json
|
||||
{
|
||||
"isLogin": true,
|
||||
"accessToken": "your-token-here",
|
||||
"info": { ... }
|
||||
}
|
||||
```
|
||||
|
||||
### 4. 请求拦截器日志
|
||||
|
||||
**文件**: `src/utils/http/interceptors.ts`
|
||||
|
||||
已自动添加请求/响应日志，在控制台可以看到：
|
||||
- 🚀 发送请求
|
||||
- ✅ 请求成功
|
||||
- ❌ 请求失败
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 常见问题
|
||||
|
||||
### Q1: 登录后提示"获取用户角色失败"
|
||||
|
||||
**原因**: 后端返回的用户信息中没有 `roles` 字段
|
||||
|
||||
**解决**:
|
||||
1. 确保后端返回的 `userInfo.roles` 是数组
|
||||
2. 至少包含一个角色，如：`["R_ADMIN"]`
|
||||
|
||||
### Q2: 登录成功但页面一直转圈
|
||||
|
||||
**原因**: 路由守卫中没有通过权限验证
|
||||
|
||||
**解决**:
|
||||
1. 检查用户信息中是否有 `roles` 字段
|
||||
2. 临时开启开发模式跳过权限验证（见下文）
|
||||
|
||||
### Q3: 如何临时跳过权限验证？
|
||||
|
||||
**文件**: `src/router/guards/beforeEach.ts` 第 28 行
|
||||
|
||||
```typescript
|
||||
const DEV_MODE_SKIP_AUTH = true // 改为 true，跳过所有权限验证
|
||||
```
|
||||
|
||||
### Q4: Token 过期如何处理？
|
||||
|
||||
系统已自动处理 Token 过期：
|
||||
1. 检测到 401 状态码自动跳转登录页
|
||||
2. 可实现自动刷新 Token（需要后端支持）
|
||||
|
||||
---
|
||||
|
||||
## 📝 后端接口开发建议
|
||||
|
||||
### 1. 登录接口返回完整用户信息
|
||||
避免前端登录后再次调用获取用户信息接口，减少请求次数。
|
||||
|
||||
### 2. 用户信息必须包含 roles
|
||||
```json
|
||||
{
|
||||
"roles": ["R_ADMIN", "R_USER"] // 必须
|
||||
}
|
||||
```
|
||||
|
||||
### 3. 支持 Token 刷新机制
|
||||
```typescript
|
||||
// 刷新Token接口
|
||||
POST /api/auth/refresh
|
||||
{
|
||||
"refreshToken": "refresh-token-here"
|
||||
}
|
||||
```
|
||||
|
||||
### 4. 统一响应格式
|
||||
```typescript
|
||||
{
|
||||
code: 200,
|
||||
message: "success",
|
||||
data: { ... }
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## ✨ 下一步
|
||||
|
||||
1. ✅ 后端提供测试环境API地址
|
||||
2. ✅ 配置 `VITE_API_URL` 或代理
|
||||
3. ✅ 切换 `USE_MOCK = false`
|
||||
4. ✅ 测试登录功能
|
||||
5. ✅ 根据实际API调整请求/响应格式
|
||||
6. ✅ 完善其他业务接口
|
||||
|
||||
---
|
||||
|
||||
**联系支持**:
|
||||
- 前端问题：查看本文档或项目 README
|
||||
- 后端对接：与后端开发人员沟通接口格式
|
||||
|
||||
祝对接顺利！🚀
|
||||
@@ -1,244 +0,0 @@
|
||||
# 登录模块说明文档
|
||||
|
||||
## 概述
|
||||
|
||||
本项目的登录模块已完成重构，采用了全新的架构设计，提供了完整的认证流程和权限管理功能。
|
||||
|
||||
## 功能特性
|
||||
|
||||
### 1. Mock 数据支持
|
||||
|
||||
系统内置了 4 个 Mock 账号，用于开发和演示：
|
||||
|
||||
| 账号类型 | 用户名 | 密码 | 角色 | 权限说明 |
|
||||
|---------|--------|------|------|---------|
|
||||
| 超级管理员 | super | 123456 | SUPER_ADMIN | 拥有所有权限 |
|
||||
| 平台管理员 | admin | 123456 | ADMIN | 账号、网卡、套餐、设备等管理权限 |
|
||||
| 代理商 | agent | 123456 | AGENT | 网卡查看/操作、佣金管理等权限 |
|
||||
| 企业客户 | enterprise | 123456 | ENTERPRISE | 自有网卡和设备的查看/操作权限 |
|
||||
|
||||
**文件位置**: `src/mock/auth.ts`
|
||||
|
||||
### 2. 记住密码功能
|
||||
|
||||
- 用户可以勾选"记住密码"选项
|
||||
- 登录成功后，用户名和密码会被加密存储到 localStorage
|
||||
- 下次访问登录页时自动填充账号信息
|
||||
- 取消勾选会清除已保存的凭证
|
||||
|
||||
**实现文件**: `src/utils/auth/rememberPassword.ts`
|
||||
|
||||
**核心函数**:
|
||||
```typescript
|
||||
// 保存凭证
|
||||
saveCredentials(username, password, remember)
|
||||
|
||||
// 获取保存的凭证
|
||||
getRememberedCredentials()
|
||||
|
||||
// 清除凭证
|
||||
clearRememberedCredentials()
|
||||
```
|
||||
|
||||
### 3. 完善的表单验证
|
||||
|
||||
提供了多种验证规则，适用于不同场景：
|
||||
|
||||
- **用户名验证**: 3-20个字符，只能包含字母、数字和下划线
|
||||
- **密码验证**: 6-20个字符
|
||||
- **强密码验证**: 8-20个字符，必须包含大小写字母和数字
|
||||
- **确认密码验证**: 必须与密码一致
|
||||
- **手机号验证**: 支持中国大陆手机号格式
|
||||
- **邮箱验证**: 标准邮箱格式验证
|
||||
- **验证码验证**: 4位数字
|
||||
|
||||
**实现文件**: `src/utils/auth/loginValidation.ts`
|
||||
|
||||
**使用示例**:
|
||||
```typescript
|
||||
import { usernameRules, passwordRules } from '@/utils/auth/loginValidation'
|
||||
|
||||
const rules = {
|
||||
username: usernameRules(t),
|
||||
password: passwordRules(t)
|
||||
}
|
||||
```
|
||||
|
||||
### 4. 权限路由守卫
|
||||
|
||||
优化了路由守卫，增加了以下功能：
|
||||
|
||||
#### 白名单机制
|
||||
不需要登录即可访问的路由：
|
||||
- `/login` - 登录页
|
||||
- `/register` - 注册页
|
||||
- `/forget-password` - 忘记密码
|
||||
- `/exception/*` - 异常页面
|
||||
|
||||
**文件位置**: `src/router/guards/permission.ts`
|
||||
|
||||
#### Token 验证
|
||||
- 自动检查 Token 是否存在
|
||||
- 验证 Token 是否有效
|
||||
- Token 过期自动跳转到登录页
|
||||
|
||||
#### 页面级权限验证
|
||||
- 根据路由 meta 中的 `roles` 和 `permissions` 进行验证
|
||||
- 无权限访问时自动跳转到 403 页面
|
||||
- 支持通配符权限（如 `*:*:*` 表示所有权限）
|
||||
|
||||
#### 登录重定向
|
||||
- 访问需要登录的页面时，会记录当前路径
|
||||
- 登录成功后自动跳转回之前访问的页面
|
||||
- 如果是白名单路由，则跳转到首页
|
||||
|
||||
**核心函数**:
|
||||
```typescript
|
||||
// 检查是否在白名单
|
||||
isInWhiteList(path)
|
||||
|
||||
// 检查路由权限
|
||||
hasRoutePermission(route, userInfo)
|
||||
|
||||
// 检查 Token 是否有效
|
||||
isTokenValid(token)
|
||||
|
||||
// 构建登录重定向URL
|
||||
buildLoginRedirect(currentPath)
|
||||
```
|
||||
|
||||
### 5. useLogin Composable
|
||||
|
||||
将登录逻辑抽取为可复用的 Composable，提高代码可维护性。
|
||||
|
||||
**文件位置**: `src/composables/useLogin.ts`
|
||||
|
||||
**提供的功能**:
|
||||
- 表单状态管理
|
||||
- Mock 账号切换
|
||||
- 登录逻辑处理
|
||||
- 自动记住密码
|
||||
- 登录成功通知
|
||||
- 重定向处理
|
||||
|
||||
**使用示例**:
|
||||
```vue
|
||||
<script setup>
|
||||
import { useLogin } from '@/composables/useLogin'
|
||||
|
||||
const {
|
||||
formRef,
|
||||
formData,
|
||||
rules,
|
||||
loading,
|
||||
mockAccounts,
|
||||
setupAccount,
|
||||
handleLogin
|
||||
} = useLogin()
|
||||
</script>
|
||||
```
|
||||
|
||||
## 文件结构
|
||||
|
||||
```
|
||||
src/
|
||||
├── mock/
|
||||
│ └── auth.ts # Mock 账号数据
|
||||
├── utils/auth/
|
||||
│ ├── rememberPassword.ts # 记住密码工具
|
||||
│ ├── loginValidation.ts # 表单验证规则
|
||||
│ └── index.ts # 统一导出
|
||||
├── router/guards/
|
||||
│ ├── permission.ts # 权限验证工具
|
||||
│ ├── beforeEach.ts # 路由前置守卫（已优化）
|
||||
│ └── afterEach.ts # 路由后置守卫
|
||||
├── composables/
|
||||
│ └── useLogin.ts # 登录逻辑 Composable
|
||||
└── views/auth/login/
|
||||
└── index.vue # 登录页面（已重构）
|
||||
```
|
||||
|
||||
## 权限配置示例
|
||||
|
||||
### 路由权限配置
|
||||
|
||||
```typescript
|
||||
// 在路由配置中添加 meta
|
||||
{
|
||||
path: '/account/platform',
|
||||
meta: {
|
||||
title: '平台账号管理',
|
||||
roles: ['R_SUPER', 'R_ADMIN'], // 允许的角色
|
||||
permissions: ['account:view:*'] // 需要的权限
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 用户权限定义
|
||||
|
||||
```typescript
|
||||
// 用户信息中包含角色和权限
|
||||
{
|
||||
roles: ['R_ADMIN'],
|
||||
permissions: [
|
||||
'account:*:*', // 账号管理所有权限
|
||||
'card:view:*', // 网卡查看权限
|
||||
'card:operation:*' // 网卡操作权限
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
## 开发建议
|
||||
|
||||
### 1. 切换到真实接口
|
||||
|
||||
当后端接口就绪后，只需修改 `useLogin.ts` 中的登录逻辑：
|
||||
|
||||
```typescript
|
||||
// 将 Mock 登录替换为真实 API
|
||||
// const loginResult = mockLogin(formData.username, formData.password)
|
||||
const loginResult = await AuthService.login({
|
||||
username: formData.username,
|
||||
password: formData.password
|
||||
})
|
||||
```
|
||||
|
||||
### 2. Token 刷新
|
||||
|
||||
在 `src/router/guards/permission.ts` 的 `isTokenValid` 函数中添加真实的 JWT 验证逻辑。
|
||||
|
||||
### 3. 权限粒度
|
||||
|
||||
根据实际业务需求，可以在以下层级添加权限验证：
|
||||
- **路由级**: 在路由 meta 中配置
|
||||
- **页面级**: 在页面组件中使用 v-if 判断
|
||||
- **按钮级**: 使用自定义指令（如 `v-permission`）
|
||||
|
||||
## 常见问题
|
||||
|
||||
### Q1: 如何添加新的 Mock 账号？
|
||||
|
||||
编辑 `src/mock/auth.ts`，在 `MOCK_ACCOUNTS` 数组中添加新账号即可。
|
||||
|
||||
### Q2: 记住密码的数据存在哪里？
|
||||
|
||||
存储在浏览器的 localStorage 中，key 为 `remembered_credentials`，数据经过 Base64 编码。
|
||||
|
||||
### Q3: 如何自定义白名单路由？
|
||||
|
||||
编辑 `src/router/guards/permission.ts` 的 `LOGIN_WHITE_LIST` 数组。
|
||||
|
||||
### Q4: 为什么登录后还是跳转到登录页？
|
||||
|
||||
检查以下几点：
|
||||
1. Token 是否正确保存到 store
|
||||
2. `userStore.isLogin` 是否设置为 true
|
||||
3. 路由守卫中的权限验证是否通过
|
||||
|
||||
## 下一步计划
|
||||
|
||||
- [ ] 添加双因素认证（2FA）
|
||||
- [ ] 实现 SSO 单点登录
|
||||
- [ ] 添加第三方登录（微信、钉钉等）
|
||||
- [ ] 完善密码强度检测
|
||||
- [ ] 添加登录日志记录
|
||||
@@ -1,9 +0,0 @@
|
||||
touch README.md
|
||||
git init
|
||||
git checkout -b main
|
||||
git add README.md
|
||||
git commit -m "first commit"
|
||||
git remote add origin https://git.boss160.cn/luo/admin-xm-iot.git
|
||||
git push -u origin main
|
||||
|
||||
你需要注意下.gitignore 是否需要加一些文件进去
|
||||
870
docs/代理账号管理.md
870
docs/代理账号管理.md
@@ -1,870 +0,0 @@
|
||||
# 账号管理下面新增一个代理账号管理, 页面样式可以参考/system/account 都需要token认证
|
||||
|
||||
# 代理账号列表
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shop-accounts:
|
||||
get:
|
||||
summary: 代理账号列表
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 代理账号管理
|
||||
- 代理账号管理
|
||||
parameters:
|
||||
- name: page
|
||||
in: query
|
||||
description: 页码
|
||||
required: false
|
||||
schema:
|
||||
description: 页码
|
||||
minimum: 1
|
||||
type: integer
|
||||
- name: page_size
|
||||
in: query
|
||||
description: 每页数量
|
||||
required: false
|
||||
schema:
|
||||
description: 每页数量
|
||||
maximum: 100
|
||||
minimum: 1
|
||||
type: integer
|
||||
- name: shop_id
|
||||
in: query
|
||||
description: 店铺ID过滤
|
||||
required: false
|
||||
schema:
|
||||
description: 店铺ID过滤
|
||||
minimum: 1
|
||||
type: integer
|
||||
nullable: true
|
||||
- name: username
|
||||
in: query
|
||||
description: 用户名（模糊查询）
|
||||
required: false
|
||||
schema:
|
||||
description: 用户名（模糊查询）
|
||||
maxLength: 50
|
||||
type: string
|
||||
- name: phone
|
||||
in: query
|
||||
description: 手机号（精确查询）
|
||||
required: false
|
||||
schema:
|
||||
description: 手机号（精确查询）
|
||||
maxLength: 11
|
||||
minLength: 11
|
||||
type: string
|
||||
- name: status
|
||||
in: query
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
required: false
|
||||
schema:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
nullable: true
|
||||
responses:
|
||||
'200':
|
||||
description: OK
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelShopAccountPageResult'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: '-jWpeN1-jYBl-SEBTmsrq'
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: '-jWpeN1-jYBl-SEBTmsrq'
|
||||
scopes:
|
||||
'-jWpeN1-jYBl-SEBTmsrq':
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 代理账号管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366334-run
|
||||
components:
|
||||
schemas:
|
||||
ModelShopAccountPageResult:
|
||||
properties:
|
||||
items:
|
||||
description: 代理账号列表
|
||||
items:
|
||||
$ref: '#/components/schemas/ModelShopAccountResponse'
|
||||
type: array
|
||||
nullable: true
|
||||
page:
|
||||
description: 当前页码
|
||||
type: integer
|
||||
size:
|
||||
description: 每页数量
|
||||
type: integer
|
||||
total:
|
||||
description: 总记录数
|
||||
type: integer
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- items
|
||||
- page
|
||||
- size
|
||||
- total
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ModelShopAccountResponse:
|
||||
properties:
|
||||
created_at:
|
||||
description: 创建时间
|
||||
type: string
|
||||
id:
|
||||
description: 账号ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
phone:
|
||||
description: 手机号
|
||||
type: string
|
||||
shop_id:
|
||||
description: 店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
updated_at:
|
||||
description: 更新时间
|
||||
type: string
|
||||
user_type:
|
||||
description: 用户类型 (1:超级管理员, 2:平台用户, 3:代理账号, 4:企业账号)
|
||||
type: integer
|
||||
username:
|
||||
description: 用户名
|
||||
type: string
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- created_at
|
||||
- id
|
||||
- phone
|
||||
- shop_id
|
||||
- shop_name
|
||||
- status
|
||||
- updated_at
|
||||
- user_type
|
||||
- username
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
# 创建代理账号
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shop-accounts:
|
||||
post:
|
||||
summary: 创建代理账号
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 代理账号管理
|
||||
- 代理账号管理
|
||||
parameters: []
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelCreateShopAccountRequest'
|
||||
responses:
|
||||
'200':
|
||||
description: OK
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelShopAccountResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: LdX0-6IzkTw-pXBT8t4Km
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: LdX0-6IzkTw-pXBT8t4Km
|
||||
scopes:
|
||||
LdX0-6IzkTw-pXBT8t4Km:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 代理账号管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366335-run
|
||||
components:
|
||||
schemas:
|
||||
ModelCreateShopAccountRequest:
|
||||
properties:
|
||||
password:
|
||||
description: 密码
|
||||
maxLength: 32
|
||||
minLength: 8
|
||||
type: string
|
||||
phone:
|
||||
description: 手机号
|
||||
maxLength: 11
|
||||
minLength: 11
|
||||
type: string
|
||||
shop_id:
|
||||
description: 店铺ID
|
||||
minimum: 1
|
||||
type: integer
|
||||
username:
|
||||
description: 用户名
|
||||
maxLength: 50
|
||||
minLength: 3
|
||||
type: string
|
||||
required:
|
||||
- password
|
||||
- phone
|
||||
- shop_id
|
||||
- username
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- password
|
||||
- phone
|
||||
- shop_id
|
||||
- username
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ModelShopAccountResponse:
|
||||
properties:
|
||||
created_at:
|
||||
description: 创建时间
|
||||
type: string
|
||||
id:
|
||||
description: 账号ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
phone:
|
||||
description: 手机号
|
||||
type: string
|
||||
shop_id:
|
||||
description: 店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
updated_at:
|
||||
description: 更新时间
|
||||
type: string
|
||||
user_type:
|
||||
description: 用户类型 (1:超级管理员, 2:平台用户, 3:代理账号, 4:企业账号)
|
||||
type: integer
|
||||
username:
|
||||
description: 用户名
|
||||
type: string
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- created_at
|
||||
- id
|
||||
- phone
|
||||
- shop_id
|
||||
- shop_name
|
||||
- status
|
||||
- updated_at
|
||||
- user_type
|
||||
- username
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
# 更新代理账号
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shop-accounts/{id}:
|
||||
put:
|
||||
summary: 更新代理账号
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 代理账号管理
|
||||
- 代理账号管理
|
||||
parameters:
|
||||
- name: id
|
||||
in: path
|
||||
description: ID
|
||||
required: true
|
||||
example: 0
|
||||
schema:
|
||||
description: ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelUpdateShopAccountParams'
|
||||
responses:
|
||||
'200':
|
||||
description: OK
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelShopAccountResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: TTw5I9JG_CJv8tEsi1Bk6
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: TTw5I9JG_CJv8tEsi1Bk6
|
||||
scopes:
|
||||
TTw5I9JG_CJv8tEsi1Bk6:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 代理账号管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366336-run
|
||||
components:
|
||||
schemas:
|
||||
ModelUpdateShopAccountParams:
|
||||
properties:
|
||||
username:
|
||||
description: 用户名
|
||||
maxLength: 50
|
||||
minLength: 3
|
||||
type: string
|
||||
required:
|
||||
- username
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- username
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ModelShopAccountResponse:
|
||||
properties:
|
||||
created_at:
|
||||
description: 创建时间
|
||||
type: string
|
||||
id:
|
||||
description: 账号ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
phone:
|
||||
description: 手机号
|
||||
type: string
|
||||
shop_id:
|
||||
description: 店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
updated_at:
|
||||
description: 更新时间
|
||||
type: string
|
||||
user_type:
|
||||
description: 用户类型 (1:超级管理员, 2:平台用户, 3:代理账号, 4:企业账号)
|
||||
type: integer
|
||||
username:
|
||||
description: 用户名
|
||||
type: string
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- created_at
|
||||
- id
|
||||
- phone
|
||||
- shop_id
|
||||
- shop_name
|
||||
- status
|
||||
- updated_at
|
||||
- user_type
|
||||
- username
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
# 重置代理账号密码
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shop-accounts/{id}/password:
|
||||
put:
|
||||
summary: 重置代理账号密码
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 代理账号管理
|
||||
- 代理账号管理
|
||||
parameters:
|
||||
- name: id
|
||||
in: path
|
||||
description: ID
|
||||
required: true
|
||||
example: 0
|
||||
schema:
|
||||
description: ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelUpdateShopAccountPasswordParams'
|
||||
responses:
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: IeBLfzHchBWHbFru7Ma0u
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: IeBLfzHchBWHbFru7Ma0u
|
||||
scopes:
|
||||
IeBLfzHchBWHbFru7Ma0u:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 代理账号管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366337-run
|
||||
components:
|
||||
schemas:
|
||||
ModelUpdateShopAccountPasswordParams:
|
||||
properties:
|
||||
new_password:
|
||||
description: 新密码
|
||||
maxLength: 32
|
||||
minLength: 8
|
||||
type: string
|
||||
required:
|
||||
- new_password
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- new_password
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
列表显示中状态用开关那个组件
|
||||
# 启用/禁用代理账号
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shop-accounts/{id}/status:
|
||||
put:
|
||||
summary: 启用/禁用代理账号
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 代理账号管理
|
||||
- 代理账号管理
|
||||
parameters:
|
||||
- name: id
|
||||
in: path
|
||||
description: ID
|
||||
required: true
|
||||
example: 0
|
||||
schema:
|
||||
description: ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelUpdateShopAccountStatusParams'
|
||||
responses:
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: QRYgZh2IcZgAVmdF1dNBU
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: QRYgZh2IcZgAVmdF1dNBU
|
||||
scopes:
|
||||
QRYgZh2IcZgAVmdF1dNBU:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 代理账号管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366338-run
|
||||
components:
|
||||
schemas:
|
||||
ModelUpdateShopAccountStatusParams:
|
||||
properties:
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
required:
|
||||
- status
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- status
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
488
docs/任务规划.md
488
docs/任务规划.md
@@ -1,488 +0,0 @@
|
||||
# 物联网卡管理系统 - 开发任务规划
|
||||
|
||||
> 项目开始日期: 2026-01-09
|
||||
> 当前状态: 进行中
|
||||
|
||||
---
|
||||
|
||||
## 📋 任务进度总览
|
||||
|
||||
- [ ] 阶段一：基础设施和认证模块（0/2）
|
||||
- [ ] 阶段二：账号管理模块（0/7）
|
||||
- [ ] 阶段三：财务管理模块（0/4）
|
||||
- [ ] 阶段四：商品管理模块（0/5）
|
||||
- [ ] 阶段五：资产管理模块（0/5）
|
||||
- [ ] 阶段六：批量操作模块（0/3）
|
||||
|
||||
**总体完成度**: 0/26 任务
|
||||
|
||||
---
|
||||
|
||||
## 🚀 阶段一：基础设施和认证模块
|
||||
|
||||
### 1.1 登录模块
|
||||
- [ ] 设计登录页面UI
|
||||
- [ ] 实现用户名密码登录
|
||||
- [ ] 实现记住密码功能
|
||||
- [ ] 集成验证码/滑块验证
|
||||
- [ ] 实现 Token 管理
|
||||
- [ ] 实现自动刷新 Token
|
||||
- [ ] 实现登出功能
|
||||
- [ ] 添加登录错误处理
|
||||
|
||||
### 1.2 权限管理基础
|
||||
- [ ] 设计权限控制策略（RBAC）
|
||||
- [ ] 实现路由权限守卫
|
||||
- [ ] 实现按钮级权限控制
|
||||
- [ ] 实现数据权限过滤
|
||||
- [ ] 完善角色权限映射
|
||||
|
||||
---
|
||||
|
||||
## 👥 阶段二：账号管理模块
|
||||
|
||||
### 2.1 平台角色管理
|
||||
- [ ] 角色列表页面（表格展示）
|
||||
- [ ] 新增角色功能
|
||||
- [ ] 角色基础信息表单
|
||||
- [ ] 权限分配（树形结构）
|
||||
- [ ] 编辑角色功能
|
||||
- [ ] 删除角色功能
|
||||
- [ ] 角色搜索和筛选
|
||||
- [ ] 角色权限预览
|
||||
|
||||
### 2.2 平台账号管理
|
||||
- [ ] 平台账号列表页面
|
||||
- [ ] 新增平台账号
|
||||
- [ ] 账号信息表单
|
||||
- [ ] 角色分配
|
||||
- [ ] 账号状态设置
|
||||
- [ ] 编辑平台账号
|
||||
- [ ] 禁用/启用账号
|
||||
- [ ] 重置密码功能
|
||||
- [ ] 账号操作日志查看
|
||||
|
||||
### 2.3 客户角色管理
|
||||
- [ ] 客户角色列表页面
|
||||
- [ ] 新增客户角色
|
||||
- [ ] 角色名称和描述
|
||||
- [ ] 能力边界配置（权限树）
|
||||
- [ ] 编辑客户角色
|
||||
- [ ] 删除客户角色
|
||||
- [ ] 角色能力说明文档
|
||||
|
||||
### 2.4 代理商管理
|
||||
- [ ] 代理商列表页面
|
||||
- [ ] 多级代理商树形展示
|
||||
- [ ] 代理商等级标识
|
||||
- [ ] 新增代理商
|
||||
- [ ] 代理商基础信息
|
||||
- [ ] 上级代理商选择
|
||||
- [ ] 代理商等级设置
|
||||
- [ ] 编辑代理商信息
|
||||
- [ ] 代理商账号管理
|
||||
- [ ] 查看代理商下的账号列表
|
||||
- [ ] 为代理商创建子账号
|
||||
- [ ] 代理商佣金配置
|
||||
- [ ] 代理商数据统计面板
|
||||
|
||||
### 2.5 企业客户管理
|
||||
- [ ] 企业客户列表页面
|
||||
- [ ] 新增企业客户
|
||||
- [ ] 企业基础信息
|
||||
- [ ] 客户角色分配
|
||||
- [ ] 联系人信息
|
||||
- [ ] 编辑企业客户
|
||||
- [ ] 企业客户账号管理
|
||||
- [ ] 创建企业管理账号
|
||||
- [ ] 账号权限设置
|
||||
- [ ] 企业客户数据看板
|
||||
|
||||
### 2.6 客户账号管理
|
||||
- [ ] 客户账号列表页面
|
||||
- [ ] 支持按代理商/企业筛选
|
||||
- [ ] 账号状态筛选
|
||||
- [ ] 查看账号详情
|
||||
- [ ] 解绑手机号
|
||||
- [ ] 重置登录密码
|
||||
- [ ] 禁用/启用账号
|
||||
- [ ] 账号操作记录
|
||||
|
||||
### 2.7 客户账号佣金管理
|
||||
- [ ] 客户账号佣金列表
|
||||
- [ ] 佣金统计卡片
|
||||
- [ ] 佣金明细表格
|
||||
- [ ] 佣金详情查看
|
||||
- [ ] 提现记录查看
|
||||
- [ ] 佣金统计图表
|
||||
|
||||
---
|
||||
|
||||
## 💰 阶段三：财务管理模块
|
||||
|
||||
### 3.1 佣金提现管理
|
||||
- [ ] 提现申请列表
|
||||
- [ ] 状态筛选（待审核、已通过、已拒绝）
|
||||
- [ ] 时间范围筛选
|
||||
- [ ] 提现申请详情
|
||||
- [ ] 审核提现申请
|
||||
- [ ] 通过操作
|
||||
- [ ] 拒绝操作（需填写原因）
|
||||
- [ ] 批量审核功能
|
||||
- [ ] 提现记录导出
|
||||
|
||||
### 3.2 佣金提现设置
|
||||
- [ ] 提现参数配置页面
|
||||
- [ ] 最低提现金额
|
||||
- [ ] 提现手续费设置
|
||||
- [ ] 单日提现次数限制
|
||||
- [ ] 提现规则说明
|
||||
- [ ] 配置历史记录
|
||||
- [ ] 参数生效管理
|
||||
|
||||
### 3.3 我的账户（当前登录账号）
|
||||
- [ ] 账户概览页面
|
||||
- [ ] 佣金总额卡片
|
||||
- [ ] 可提现金额卡片
|
||||
- [ ] 待入账金额卡片
|
||||
- [ ] 佣金收入明细
|
||||
- [ ] 提现申请功能
|
||||
- [ ] 收支流水记录
|
||||
- [ ] 佣金统计图表
|
||||
|
||||
### 3.4 收款商户设置
|
||||
- [ ] 支付参数配置页面
|
||||
- [ ] 支付商户信息
|
||||
- [ ] API密钥配置
|
||||
- [ ] 回调地址设置
|
||||
- [ ] 支付方式管理
|
||||
- [ ] 微信支付
|
||||
- [ ] 支付宝
|
||||
- [ ] 银行卡
|
||||
- [ ] 支付测试功能
|
||||
- [ ] 配置安全验证
|
||||
|
||||
---
|
||||
|
||||
## 🛍️ 阶段四：商品管理模块
|
||||
|
||||
### 4.1 号卡管理
|
||||
- [ ] 号卡列表页面
|
||||
- [ ] 号卡信息展示
|
||||
- [ ] 状态筛选
|
||||
- [ ] 新增号卡
|
||||
- [ ] 号卡基础信息
|
||||
- [ ] 运营商选择
|
||||
- [ ] 套餐配置
|
||||
- [ ] 编辑号卡
|
||||
- [ ] 号卡上下架
|
||||
- [ ] 号卡库存管理
|
||||
- [ ] 号卡详情页面
|
||||
|
||||
### 4.2 号卡分配
|
||||
- [ ] 分配记录列表
|
||||
- [ ] 为代理商分配号卡
|
||||
- [ ] 选择代理商
|
||||
- [ ] 选择号卡商品
|
||||
- [ ] 设置分配数量
|
||||
- [ ] 设置佣金模式
|
||||
- [ ] 查看分配详情
|
||||
- [ ] 撤销分配
|
||||
- [ ] 分配统计报表
|
||||
|
||||
### 4.3 套餐系列管理
|
||||
- [ ] 套餐系列列表
|
||||
- [ ] 新增套餐系列
|
||||
- [ ] 系列名称
|
||||
- [ ] 系列描述
|
||||
- [ ] 系列图标
|
||||
- [ ] 编辑套餐系列
|
||||
- [ ] 删除套餐系列
|
||||
- [ ] 套餐系列排序
|
||||
|
||||
### 4.4 套餐管理
|
||||
- [ ] 套餐列表页面
|
||||
- [ ] 权限过滤（管理员看全部，普通用户看自己的）
|
||||
- [ ] 按套餐系列筛选
|
||||
- [ ] 新增套餐
|
||||
- [ ] 套餐基础信息
|
||||
- [ ] 套餐类型（流量、语音、短信）
|
||||
- [ ] 套餐价格
|
||||
- [ ] 有效期设置
|
||||
- [ ] 编辑套餐
|
||||
- [ ] 套餐上下架
|
||||
- [ ] 套餐详情页面
|
||||
|
||||
### 4.5 套餐分配
|
||||
- [ ] 套餐分配列表
|
||||
- [ ] 为直级代理分配套餐
|
||||
- [ ] 选择代理商
|
||||
- [ ] 选择套餐
|
||||
- [ ] 设置佣金模式
|
||||
- [ ] 固定佣金
|
||||
- [ ] 比例佣金
|
||||
- [ ] 查看分配详情
|
||||
- [ ] 修改佣金设置
|
||||
- [ ] 分配统计
|
||||
|
||||
---
|
||||
|
||||
## 📦 阶段五：资产管理模块
|
||||
|
||||
### 5.1 单卡信息查询
|
||||
- [ ] ICCID 查询界面
|
||||
- [ ] 单卡详情页面
|
||||
- [ ] 基础信息展示
|
||||
- [ ] 套餐信息
|
||||
- [ ] 使用情况
|
||||
- [ ] 单卡操作功能
|
||||
- [ ] 套餐充值
|
||||
- [ ] 停机/复机
|
||||
- [ ] 查看流量详情
|
||||
- [ ] 更改过期时间
|
||||
- [ ] 转新卡
|
||||
- [ ] 查看停复机记录
|
||||
- [ ] 查看往期订单
|
||||
- [ ] 增减流量
|
||||
- [ ] 变更钱包余额
|
||||
- [ ] 充值支付密码
|
||||
- [ ] 续充
|
||||
- [ ] 设备操作入口
|
||||
|
||||
### 5.2 网卡管理
|
||||
- [ ] 网卡列表页面
|
||||
- [ ] 高级搜索
|
||||
- [ ] 状态筛选
|
||||
- [ ] 批量选择
|
||||
- [ ] 网卡详情页面
|
||||
- [ ] 批量操作入口
|
||||
- [ ] 批量充值
|
||||
- [ ] 批量停复机
|
||||
- [ ] 批量分配
|
||||
- [ ] 网卡导出功能
|
||||
- [ ] 网卡数据统计
|
||||
|
||||
### 5.3 设备管理
|
||||
- [ ] 设备列表页面
|
||||
- [ ] 设备信息展示
|
||||
- [ ] 在线状态
|
||||
- [ ] 设备详情页面
|
||||
- [ ] 设备基础信息
|
||||
- [ ] 绑定卡信息
|
||||
- [ ] 查看设备卡信息
|
||||
- [ ] 修改设备卡绑定
|
||||
- [ ] 设备相关操作
|
||||
- [ ] 设备重启
|
||||
- [ ] 设备诊断
|
||||
- [ ] 设备数据统计
|
||||
|
||||
### 5.4 资产分配
|
||||
- [ ] 资产分配页面
|
||||
- [ ] 设备批量分配
|
||||
- [ ] 选择代理商
|
||||
- [ ] 上传设备列表
|
||||
- [ ] 确认分配信息
|
||||
- [ ] 网卡批量分配
|
||||
- [ ] 选择代理商
|
||||
- [ ] 上传网卡列表（ICCID）
|
||||
- [ ] 自动关联设备处理
|
||||
- [ ] 分配预览和确认
|
||||
- [ ] 分配记录查看
|
||||
- [ ] 分配回滚功能
|
||||
|
||||
### 5.5 换卡申请管理
|
||||
- [ ] 换卡申请列表
|
||||
- [ ] 状态筛选（待处理、已完成、已拒绝）
|
||||
- [ ] 申请详情查看
|
||||
- [ ] 旧卡信息
|
||||
- [ ] 申请原因
|
||||
- [ ] 处理换卡申请
|
||||
- [ ] 填充新 ICCID
|
||||
- [ ] 确认换卡
|
||||
- [ ] 拒绝申请
|
||||
- [ ] 换卡记录追溯
|
||||
|
||||
---
|
||||
|
||||
## 🔄 阶段六：批量操作模块
|
||||
|
||||
### 6.1 网卡批量导入
|
||||
- [ ] 网卡导入页面
|
||||
- [ ] 模板下载
|
||||
- [ ] Excel 文件上传
|
||||
- [ ] 数据预览
|
||||
- [ ] 导入任务列表
|
||||
- [ ] 任务状态
|
||||
- [ ] 成功/失败统计
|
||||
- [ ] 查看导入详情
|
||||
- [ ] 成功记录
|
||||
- [ ] 失败记录和原因
|
||||
- [ ] 失败数据重新导入
|
||||
|
||||
### 6.2 设备批量导入
|
||||
- [ ] 设备导入页面
|
||||
- [ ] 模板下载
|
||||
- [ ] Excel 文件上传（设备+ICCID关系）
|
||||
- [ ] 数据预览和校验
|
||||
- [ ] 导入任务列表
|
||||
- [ ] 查看导入结果
|
||||
- [ ] 导入失败处理
|
||||
|
||||
### 6.3 线下批量充值
|
||||
- [ ] 批量充值记录列表
|
||||
- [ ] 新建批量充值
|
||||
- [ ] 模板下载
|
||||
- [ ] Excel 上传
|
||||
- [ ] 充值预览
|
||||
- [ ] 确认充值
|
||||
- [ ] 充值详情查看
|
||||
- [ ] 成功列表
|
||||
- [ ] 失败列表
|
||||
- [ ] 充值结果导出
|
||||
|
||||
### 6.4 换卡通知
|
||||
- [ ] 换卡通知列表
|
||||
- [ ] 单独创建换卡通知
|
||||
- [ ] 选择网卡
|
||||
- [ ] 填写通知内容
|
||||
- [ ] 选择通知方式（短信/邮件）
|
||||
- [ ] 批量创建换卡通知
|
||||
- [ ] 上传网卡列表
|
||||
- [ ] 设置通知内容
|
||||
- [ ] 查看通知记录
|
||||
- [ ] 发送状态
|
||||
- [ ] 已读状态
|
||||
|
||||
---
|
||||
|
||||
## 🎨 阶段七：开发能力和其他设置
|
||||
|
||||
### 7.1 开发能力管理
|
||||
- [ ] 开发能力列表页面
|
||||
- [ ] API 密钥管理
|
||||
- [ ] 生成密钥
|
||||
- [ ] 重置密钥
|
||||
- [ ] 密钥权限设置
|
||||
- [ ] Webhook 配置
|
||||
- [ ] API 文档集成
|
||||
- [ ] API 调用统计
|
||||
|
||||
### 7.2 分佣模板管理
|
||||
- [ ] 分佣模板列表
|
||||
- [ ] 新增分佣模板
|
||||
- [ ] 模板名称
|
||||
- [ ] 分佣规则配置
|
||||
- [ ] 适用范围
|
||||
- [ ] 编辑分佣模板
|
||||
- [ ] 删除分佣模板
|
||||
- [ ] 模板应用记录
|
||||
|
||||
---
|
||||
|
||||
## 📊 阶段八：数据统计和报表
|
||||
|
||||
### 8.1 数据概览（Dashboard）
|
||||
- [ ] 总体数据统计卡片
|
||||
- [ ] 网卡总数
|
||||
- [ ] 设备总数
|
||||
- [ ] 今日充值金额
|
||||
- [ ] 今日佣金
|
||||
- [ ] 数据趋势图表
|
||||
- [ ] 充值趋势
|
||||
- [ ] 新增网卡趋势
|
||||
- [ ] 代理商排行榜
|
||||
- [ ] 套餐销售排行
|
||||
|
||||
### 8.2 业务报表
|
||||
- [ ] 充值报表
|
||||
- [ ] 佣金报表
|
||||
- [ ] 代理商业绩报表
|
||||
- [ ] 套餐使用报表
|
||||
- [ ] 报表导出功能
|
||||
|
||||
---
|
||||
|
||||
## 🔧 阶段九：系统优化和完善
|
||||
|
||||
### 9.1 性能优化
|
||||
- [ ] 长列表虚拟滚动
|
||||
- [ ] 图片懒加载
|
||||
- [ ] 接口请求优化
|
||||
- [ ] 打包体积优化
|
||||
|
||||
### 9.2 用户体验优化
|
||||
- [ ] 页面加载状态
|
||||
- [ ] 错误提示优化
|
||||
- [ ] 操作反馈优化
|
||||
- [ ] 响应式适配
|
||||
|
||||
### 9.3 代码质量
|
||||
- [ ] 代码规范检查
|
||||
- [ ] 单元测试编写
|
||||
- [ ] E2E 测试
|
||||
- [ ] 代码注释完善
|
||||
|
||||
---
|
||||
|
||||
## 📝 开发规范
|
||||
|
||||
### 命名规范
|
||||
- 组件名：大驼峰，如 `UserManagement.vue`
|
||||
- 文件名：小写+连字符，如 `user-list.vue`
|
||||
- 接口名：RESTful 风格
|
||||
- 路由名：小写+连字符
|
||||
|
||||
### 代码结构
|
||||
```
|
||||
src/
|
||||
├── views/ # 页面组件
|
||||
├── components/ # 公共组件
|
||||
├── api/ # API 接口
|
||||
├── store/ # 状态管理
|
||||
├── router/ # 路由配置
|
||||
├── utils/ # 工具函数
|
||||
└── types/ # TypeScript 类型定义
|
||||
```
|
||||
|
||||
### Git 提交规范
|
||||
- `feat`: 新功能
|
||||
- `fix`: 修复bug
|
||||
- `docs`: 文档更新
|
||||
- `style`: 代码格式调整
|
||||
- `refactor`: 重构
|
||||
- `test`: 测试相关
|
||||
- `chore`: 构建/工具相关
|
||||
|
||||
---
|
||||
|
||||
## 🎯 里程碑
|
||||
|
||||
- [ ] **M1**: 基础设施完成（登录、权限） - 预计 3 天
|
||||
- [ ] **M2**: 账号管理模块完成 - 预计 7 天
|
||||
- [ ] **M3**: 财务管理模块完成 - 预计 5 天
|
||||
- [ ] **M4**: 商品管理模块完成 - 预计 5 天
|
||||
- [ ] **M5**: 资产管理模块完成 - 预计 7 天
|
||||
- [ ] **M6**: 批量操作模块完成 - 预计 4 天
|
||||
- [ ] **M7**: 数据统计和系统优化 - 预计 5 天
|
||||
|
||||
**预计总工期**: 36 个工作日
|
||||
|
||||
---
|
||||
|
||||
## 📌 注意事项
|
||||
|
||||
1. **优先级**：按阶段顺序开发，基础设施 > 核心业务 > 辅助功能
|
||||
2. **接口对接**：等待后端 API 完成后再进行集成
|
||||
3. **数据安全**：涉及敏感数据的操作需要二次确认
|
||||
4. **性能考虑**：列表超过 1000 条需要使用虚拟滚动
|
||||
5. **错误处理**：所有接口调用必须有错误处理
|
||||
6. **权限控制**：每个页面和操作都需要权限验证
|
||||
|
||||
---
|
||||
|
||||
## 🔄 更新日志
|
||||
|
||||
### 2026-01-09
|
||||
- 创建任务规划文档
|
||||
- 定义开发阶段和任务拆分
|
||||
- 明确开发规范和里程碑
|
||||
42
docs/功能.md
42
docs/功能.md
@@ -1,42 +0,0 @@
|
||||
# 物联网卡管理系统 - 功能列表
|
||||
|
||||
## 账号管理模块
|
||||
- 账号管理-客户角色 客户角色用以决定客户能力边界
|
||||
- 账号管理-代理商管理 用以创建代理商以及管理特定代理商账号
|
||||
- 账号管理-企业客户管理 用以创建企业管理账号,只能登录企业端,依赖客户角色
|
||||
- 账号管理-客户账号管理 管理客户(代理商+企业客户)的账号,解绑手机等或针对该账号的操作
|
||||
|
||||
## 账户管理/财务模块
|
||||
- 账户管理-客户账号 查看账号下全部的客户账号的佣金情况以及提现情况
|
||||
- 账户管理/我的财务-佣金提现 管理全部的提现申请
|
||||
- 账户管理-佣金提现设置 设置提现参数,生效最新的一条
|
||||
- 我的财务-我的账户 获取当前登录账号的佣金相关数据(这里不应该跟奇成一样用列表)
|
||||
|
||||
## 我的设置模块
|
||||
- 我的设置-收款商户设置 设置支付参数
|
||||
- 我的设置-开发能力管理 获取开发能力对接参数以及管理
|
||||
- 我的设置-分佣模板 用以创建以及管理分佣模板方便给代理分配产品时设置分佣规则
|
||||
|
||||
## 商品管理模块
|
||||
- 商品管理-号卡管理 新增管理号卡商品,管理基础信息
|
||||
- 商品管理-号卡分配 为特定代理分配号卡商品,同时设置佣金模式
|
||||
- 商品管理-套餐系列管理 新增以及管理套餐系列
|
||||
- 商品管理-套餐管理 新增以及管理套餐系列(只能看到自己的/管理员可以看到全部)
|
||||
- 商品管理-套餐分配 为直级代理分配套餐同时设置佣金模式
|
||||
|
||||
## 资产管理模块
|
||||
- 资产管理-单卡信息 通过ICCID查询单卡相关信息,以及相关操作如,套餐充值,停复机,流量详情,更改过期时间,转新卡,停复机记录,往期订单,增减流量,变更钱包余额,充值支付密码,续充,设备操作
|
||||
- 资产管理-网卡管理 查询网卡信息,提供相关批量操作入口
|
||||
- 资产管理-设备管理 查看设备信息,提供相关操作入口,查看设备卡信息,修改设备卡信息,设备相关操作
|
||||
- 资产管理-资产分配 为特定代理分配网卡,只支持批量操作,批量操作分为两种,一种是设备批量分配,一种是网卡批量分配,如果使用网卡批量分配且网卡有设备信息,那么会把该卡所属设备以及网卡都分配过去
|
||||
- 资产管理-换卡申请 客户提交的换卡申请管理,处理换卡的申请,填充新的iccid
|
||||
|
||||
## 批量操作模块
|
||||
- 网卡管理-批量操作-网卡导入 批量导入iccid,以及查看导入任务情况
|
||||
- 设备管理-批量操作-设备导入 批量导入设备以及iccid关系,查看导入任务情况
|
||||
- 网卡管理-批量操作-线下批量充值 查看批量充值记录,提供批量充值excel导入
|
||||
- 网卡管理-批量操作-换卡通知 可单独/批量新建换卡通知,查看换卡通知记录
|
||||
|
||||
---
|
||||
|
||||
**总计：25个功能模块**
|
||||
364
docs/完成总结.md
364
docs/完成总结.md
@@ -1,364 +0,0 @@
|
||||
# 物联网卡管理系统 - 页面开发完成总结
|
||||
|
||||
## 📊 完成概况
|
||||
|
||||
**完成时间**: 2026-01-09
|
||||
**开发进度**: 13/13 页面 (100%)
|
||||
**总计文件**: 13 个 Vue 页面组件
|
||||
|
||||
---
|
||||
|
||||
## ✅ 已完成的页面列表
|
||||
|
||||
### 1. 账号管理模块 (3个页面)
|
||||
|
||||
#### 1.1 客户角色管理
|
||||
- **文件路径**: `src/views/account-management/customer-role/index.vue`
|
||||
- **功能特性**:
|
||||
- 角色列表展示（CRUD操作）
|
||||
- 能力范围配置（使用 ElCheckboxGroup）
|
||||
- 角色启用/禁用状态管理
|
||||
- 应用统计
|
||||
- **组件使用**: ArtTable, ElDialog, ElForm, ElCheckboxGroup, ElTag
|
||||
|
||||
#### 1.2 代理商管理
|
||||
- **文件路径**: `src/views/account-management/agent/index.vue`
|
||||
- **功能特性**:
|
||||
- 多层级代理商管理（支持3级）
|
||||
- 代理商等级展示（一级/二级/三级）
|
||||
- 子账号管理对话框
|
||||
- 佣金配置（固定/比例佣金）
|
||||
- 状态管理（正常/禁用）
|
||||
- **组件使用**: ArtTable, ElDialog, ElDescriptions, ElRadioGroup, ElInputNumber
|
||||
|
||||
#### 1.3 客户账号管理
|
||||
- **文件路径**: `src/views/account-management/customer-account/index.vue`
|
||||
- **功能特性**:
|
||||
- 客户账号列表
|
||||
- 账号类型筛选（个人/企业/代理商）
|
||||
- 账号详情查看
|
||||
- 解绑手机、重置密码、启用/禁用操作
|
||||
- 操作记录追踪
|
||||
- **组件使用**: ArtTable, ElDialog, ElDescriptions, ElTag, ElButton
|
||||
|
||||
---
|
||||
|
||||
### 2. 财务管理模块 (3个页面)
|
||||
|
||||
#### 2.1 提现管理
|
||||
- **文件路径**: `src/views/finance/withdrawal/index.vue`
|
||||
- **功能特性**:
|
||||
- 提现申请列表
|
||||
- 状态筛选（待审核/已通过/已拒绝/已完成）
|
||||
- 批量审核功能（ElTable selection）
|
||||
- 审核/拒绝操作（带原因输入）
|
||||
- 详情对话框展示完整提现信息
|
||||
- **组件使用**: ArtTable, ElDialog, ElDescriptions, ElButton, ElTag
|
||||
|
||||
#### 2.2 我的账户
|
||||
- **文件路径**: `src/views/finance/my-account/index.vue`
|
||||
- **功能特性**:
|
||||
- 账户概览卡片（4个统计卡片，渐变背景）
|
||||
- 提现申请表单（带手续费自动计算）
|
||||
- 交易流水列表
|
||||
- 类型筛选（全部/收入/提现）
|
||||
- **组件使用**: ElCard, ElForm, ArtTable, ElTag
|
||||
- **样式特色**: 渐变背景统计卡片
|
||||
|
||||
#### 2.3 提现设置
|
||||
- **文件路径**: `src/views/finance/withdrawal-settings/index.vue`
|
||||
- **功能特性**:
|
||||
- 提现参数配置
|
||||
- 手续费模式（固定/比例）
|
||||
- 单日提现次数限制
|
||||
- 到账时间设置
|
||||
- 工作日限制开关
|
||||
- 提现时间段设置（ElTimePicker）
|
||||
- 配置历史记录
|
||||
- **组件使用**: ElForm, ElInputNumber, ElRadioGroup, ElSwitch, ElTimePicker, ArtTable
|
||||
|
||||
---
|
||||
|
||||
### 3. 设置管理模块 (3个页面)
|
||||
|
||||
#### 3.1 支付商户配置
|
||||
- **文件路径**: `src/views/settings/payment-merchant/index.vue`
|
||||
- **功能特性**:
|
||||
- 商户基础信息配置
|
||||
- API配置（AppID, AppSecret, API密钥）
|
||||
- 密钥显示/隐藏切换
|
||||
- 回调地址配置（支付/退款）
|
||||
- 支付方式启用（微信/支付宝/银行卡）
|
||||
- 测试模式开关
|
||||
- 配置说明文档
|
||||
- **组件使用**: ElCard, ElForm, ElInput, ElButton, ElCheckboxGroup, ElSwitch
|
||||
|
||||
#### 3.2 开发者API管理
|
||||
- **文件路径**: `src/views/settings/developer-api/index.vue`
|
||||
- **功能特性**:
|
||||
- API密钥管理（生成/重置/删除）
|
||||
- AppKey/AppSecret 展示（带复制功能）
|
||||
- 密钥显示/隐藏切换
|
||||
- 权限配置（读取/写入/删除）
|
||||
- Webhook配置（URL + 签名密钥）
|
||||
- 事件订阅（多选框）
|
||||
- API调用统计（最近7天）
|
||||
- **组件使用**: ArtTable, ElDialog, ElButton, ElTag, ElCheckboxGroup
|
||||
- **交互特色**: 一键复制到剪贴板
|
||||
|
||||
#### 3.3 分佣模板管理
|
||||
- **文件路径**: `src/views/settings/commission-template/index.vue`
|
||||
- **功能特性**:
|
||||
- 分佣模板 CRUD
|
||||
- 分佣模式（固定佣金/比例佣金）
|
||||
- 佣金规则配置
|
||||
- 适用范围设置
|
||||
- 应用次数统计
|
||||
- 应用记录查看
|
||||
- **组件使用**: ArtTable, ElDialog, ElForm, ElRadioGroup, ElInputNumber, ElTag
|
||||
|
||||
---
|
||||
|
||||
### 4. 批量操作模块 (3个页面)
|
||||
|
||||
#### 4.1 网卡批量导入
|
||||
- **文件路径**: `src/views/batch/sim-import/index.vue`
|
||||
- **功能特性**:
|
||||
- Excel模板下载
|
||||
- 拖拽上传（ElUpload drag）
|
||||
- 导入说明提示（ElAlert）
|
||||
- 导入记录列表
|
||||
- 导入进度展示（ElProgress）
|
||||
- 导入状态（处理中/完成/失败）
|
||||
- 详情查看（成功数/失败数/失败原因）
|
||||
- 失败数据下载
|
||||
- **组件使用**: ElCard, ElUpload, ArtTable, ElProgress, ElTag, ElDescriptions
|
||||
|
||||
#### 4.2 设备批量导入
|
||||
- **文件路径**: `src/views/batch/device-import/index.vue`
|
||||
- **功能特性**:
|
||||
- 设备批量导入（带ICCID绑定）
|
||||
- 导入统计卡片（今日导入/成功绑定/失败数/成功率）
|
||||
- 状态筛选
|
||||
- 导入进度跟踪
|
||||
- 失败明细表格
|
||||
- 已绑定ICCID统计
|
||||
- **组件使用**: ElCard, ElUpload, ArtTable, ElProgress, ElTag, ElTable
|
||||
- **特色**: 统计卡片带图标
|
||||
|
||||
#### 4.3 换卡通知管理
|
||||
- **文件路径**: `src/views/batch/card-change-notice/index.vue`
|
||||
- **功能特性**:
|
||||
- 通知列表（标题/类型/状态）
|
||||
- 通知类型（卡片更换/激活/停用/套餐变更）
|
||||
- 目标用户设置（全部/指定/批量导入）
|
||||
- 发送方式（短信/邮件/App推送）
|
||||
- 定时发送功能
|
||||
- 发送进度实时展示
|
||||
- 立即发送操作
|
||||
- 详情查看
|
||||
- **组件使用**: ArtTable, ElDialog, ElForm, ElRadioGroup, ElCheckboxGroup, ElUpload, ElProgress
|
||||
- **交互特色**: 实时发送进度动画
|
||||
|
||||
---
|
||||
|
||||
### 5. 产品管理模块 (1个页面)
|
||||
|
||||
#### 5.1 网卡产品管理
|
||||
- **文件路径**: `src/views/product/sim-card/index.vue`
|
||||
- **功能特性**:
|
||||
- 网卡产品 CRUD
|
||||
- 运营商筛选（移动/联通/电信）
|
||||
- 套餐规格配置
|
||||
- 价格设置
|
||||
- 库存管理
|
||||
- 上线/下线状态
|
||||
- **组件使用**: ArtTable, ElDialog, ElForm, ElSelect, ElInputNumber, ElSwitch
|
||||
|
||||
---
|
||||
|
||||
## 🔧 配置文件更新
|
||||
|
||||
### 1. 路由别名配置
|
||||
**文件**: `src/router/routesAlias.ts`
|
||||
|
||||
新增路由别名：
|
||||
```typescript
|
||||
// 账号管理
|
||||
CustomerRole = '/account-management/customer-role'
|
||||
AgentManagement = '/account-management/agent'
|
||||
CustomerAccount = '/account-management/customer-account'
|
||||
|
||||
// 产品管理
|
||||
SimCardManagement = '/product/sim-card'
|
||||
|
||||
// 财务管理
|
||||
WithdrawalManagement = '/finance/withdrawal'
|
||||
MyAccount = '/finance/my-account'
|
||||
WithdrawalSettings = '/finance/withdrawal-settings'
|
||||
|
||||
// 设置管理
|
||||
PaymentMerchant = '/settings/payment-merchant'
|
||||
DeveloperApi = '/settings/developer-api'
|
||||
CommissionTemplate = '/settings/commission-template'
|
||||
|
||||
// 批量操作
|
||||
SimImport = '/batch/sim-import'
|
||||
DeviceImport = '/batch/device-import'
|
||||
CardChangeNotice = '/batch/card-change-notice'
|
||||
```
|
||||
|
||||
### 2. 异步路由配置
|
||||
**文件**: `src/router/routes/asyncRoutes.ts`
|
||||
|
||||
新增路由模块：
|
||||
- **账号管理模块**: 扩展了3个子路由
|
||||
- **产品管理模块**: 新增模块，1个子路由
|
||||
- **财务管理模块**: 新增模块，3个子路由
|
||||
- **设置管理模块**: 新增模块，3个子路由
|
||||
- **批量操作模块**: 新增模块，3个子路由
|
||||
|
||||
### 3. 国际化配置
|
||||
**文件**: `src/locales/langs/zh.json`
|
||||
|
||||
新增菜单标题：
|
||||
```json
|
||||
{
|
||||
"menus": {
|
||||
"accountManagement": {
|
||||
"customerRole": "客户角色",
|
||||
"agent": "代理商管理",
|
||||
"customerAccount": "客户账号"
|
||||
},
|
||||
"product": {
|
||||
"title": "产品管理",
|
||||
"simCard": "网卡产品管理"
|
||||
},
|
||||
"finance": {
|
||||
"title": "财务管理",
|
||||
"withdrawal": "提现管理",
|
||||
"myAccount": "我的账户",
|
||||
"withdrawalSettings": "提现设置"
|
||||
},
|
||||
"settings": {
|
||||
"title": "设置管理",
|
||||
"paymentMerchant": "支付商户",
|
||||
"developerApi": "开发者API",
|
||||
"commissionTemplate": "分佣模板"
|
||||
},
|
||||
"batch": {
|
||||
"title": "批量操作",
|
||||
"simImport": "网卡批量导入",
|
||||
"deviceImport": "设备批量导入",
|
||||
"cardChangeNotice": "换卡通知"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 开发规范遵循
|
||||
|
||||
### 1. 代码风格
|
||||
- ✅ 使用 Vue 3 Composition API
|
||||
- ✅ 使用 `<script setup>` 语法
|
||||
- ✅ TypeScript 类型定义完整
|
||||
- ✅ 使用 defineOptions 定义组件名称
|
||||
|
||||
### 2. 组件使用
|
||||
- ✅ 优先使用项目自定义组件（ArtTable）
|
||||
- ✅ 使用 Element Plus 组件库
|
||||
- ✅ 统一的表单验证规则
|
||||
- ✅ 统一的对话框样式
|
||||
|
||||
### 3. 数据管理
|
||||
- ✅ 使用 ref 和 reactive 管理状态
|
||||
- ✅ 使用 computed 处理派生数据
|
||||
- ✅ Mock 数据结构完整
|
||||
- ✅ 包含完整的 CRUD 操作
|
||||
|
||||
### 4. 用户体验
|
||||
- ✅ 操作反馈（ElMessage）
|
||||
- ✅ 确认对话框（ElMessageBox）
|
||||
- ✅ 加载状态展示
|
||||
- ✅ 进度条展示
|
||||
- ✅ 标签状态提示
|
||||
|
||||
---
|
||||
|
||||
## 🎨 界面特色
|
||||
|
||||
### 统计卡片
|
||||
- 渐变背景色
|
||||
- 图标装饰
|
||||
- 数据对比
|
||||
- 响应式布局
|
||||
|
||||
### 表格功能
|
||||
- 搜索过滤
|
||||
- 状态筛选
|
||||
- 批量操作
|
||||
- 排序功能
|
||||
- 分页展示
|
||||
|
||||
### 表单交互
|
||||
- 动态表单项（根据选择显示/隐藏）
|
||||
- 实时验证
|
||||
- 条件渲染
|
||||
- 默认值设置
|
||||
|
||||
### 文件上传
|
||||
- 拖拽上传
|
||||
- 文件类型限制
|
||||
- 大小限制
|
||||
- 模板下载
|
||||
|
||||
---
|
||||
|
||||
## 🚀 下一步工作建议
|
||||
|
||||
### 1. API 对接
|
||||
- 将所有 Mock 数据替换为真实 API 调用
|
||||
- 统一错误处理
|
||||
- 添加请求拦截器
|
||||
- 实现 Token 刷新机制
|
||||
|
||||
### 2. 权限控制
|
||||
- 按钮级权限控制
|
||||
- 数据权限过滤
|
||||
- 角色权限映射
|
||||
|
||||
### 3. 数据验证
|
||||
- 表单验证规则完善
|
||||
- 后端数据校验
|
||||
- 异常数据处理
|
||||
|
||||
### 4. 性能优化
|
||||
- 列表分页加载
|
||||
- 虚拟滚动
|
||||
- 图片懒加载
|
||||
- 组件懒加载
|
||||
|
||||
### 5. 测试
|
||||
- 单元测试
|
||||
- 集成测试
|
||||
- E2E 测试
|
||||
|
||||
---
|
||||
|
||||
## 📚 相关文档
|
||||
|
||||
- [任务规划文档](./任务规划.md)
|
||||
- [页面创建模板](./页面创建模板.md)
|
||||
- [API对接说明](./API对接说明.md)
|
||||
|
||||
---
|
||||
|
||||
## ✨ 总结
|
||||
|
||||
本次开发共完成 **13 个页面组件**，涵盖账号管理、财务管理、设置管理、批量操作和产品管理 5 大模块。所有页面均遵循统一的代码规范，使用 Mock 数据进行开发，界面美观、交互流畅，为后续 API 对接和功能扩展打下了坚实基础。
|
||||
|
||||
**开发完成度**: 100% ✅
|
||||
**代码质量**: 优秀 ⭐⭐⭐⭐⭐
|
||||
**可维护性**: 良好 👍
|
||||
875
docs/店铺管理.md
875
docs/店铺管理.md
@@ -1,875 +0,0 @@
|
||||
# 在商品管理 /account-management 下面新增一个 店铺管理 需要对接的API如下, 然后页面样式可以参考 /account-management/account
|
||||
|
||||
# 店铺列表
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shops:
|
||||
get:
|
||||
summary: 店铺列表
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 店铺管理
|
||||
- 店铺管理
|
||||
parameters:
|
||||
- name: page
|
||||
in: query
|
||||
description: 页码
|
||||
required: false
|
||||
schema:
|
||||
description: 页码
|
||||
minimum: 1
|
||||
type: integer
|
||||
- name: page_size
|
||||
in: query
|
||||
description: 每页数量
|
||||
required: false
|
||||
schema:
|
||||
description: 每页数量
|
||||
maximum: 100
|
||||
minimum: 1
|
||||
type: integer
|
||||
- name: shop_name
|
||||
in: query
|
||||
description: 店铺名称模糊查询
|
||||
required: false
|
||||
schema:
|
||||
description: 店铺名称模糊查询
|
||||
maxLength: 100
|
||||
type: string
|
||||
- name: shop_code
|
||||
in: query
|
||||
description: 店铺编号模糊查询
|
||||
required: false
|
||||
schema:
|
||||
description: 店铺编号模糊查询
|
||||
maxLength: 50
|
||||
type: string
|
||||
- name: parent_id
|
||||
in: query
|
||||
description: 上级店铺ID
|
||||
required: false
|
||||
schema:
|
||||
description: 上级店铺ID
|
||||
minimum: 1
|
||||
type: integer
|
||||
nullable: true
|
||||
- name: level
|
||||
in: query
|
||||
description: 店铺层级 (1-7级)
|
||||
required: false
|
||||
schema:
|
||||
description: 店铺层级 (1-7级)
|
||||
maximum: 7
|
||||
minimum: 1
|
||||
type: integer
|
||||
nullable: true
|
||||
- name: status
|
||||
in: query
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
required: false
|
||||
schema:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
nullable: true
|
||||
responses:
|
||||
'200':
|
||||
description: OK
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelShopPageResult'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: AiK0MKfrzIq2Np2gS4yVd
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: AiK0MKfrzIq2Np2gS4yVd
|
||||
scopes:
|
||||
AiK0MKfrzIq2Np2gS4yVd:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 店铺管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366339-run
|
||||
components:
|
||||
schemas:
|
||||
ModelShopPageResult:
|
||||
properties:
|
||||
items:
|
||||
description: 店铺列表
|
||||
items:
|
||||
$ref: '#/components/schemas/ModelShopResponse'
|
||||
type: array
|
||||
nullable: true
|
||||
page:
|
||||
description: 当前页码
|
||||
type: integer
|
||||
size:
|
||||
description: 每页数量
|
||||
type: integer
|
||||
total:
|
||||
description: 总记录数
|
||||
type: integer
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- items
|
||||
- page
|
||||
- size
|
||||
- total
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ModelShopResponse:
|
||||
properties:
|
||||
address:
|
||||
description: 详细地址
|
||||
type: string
|
||||
city:
|
||||
description: 城市
|
||||
type: string
|
||||
contact_name:
|
||||
description: 联系人姓名
|
||||
type: string
|
||||
contact_phone:
|
||||
description: 联系人电话
|
||||
type: string
|
||||
created_at:
|
||||
description: 创建时间
|
||||
type: string
|
||||
district:
|
||||
description: 区县
|
||||
type: string
|
||||
id:
|
||||
description: 店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
level:
|
||||
description: 店铺层级 (1-7级)
|
||||
type: integer
|
||||
parent_id:
|
||||
description: 上级店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
nullable: true
|
||||
province:
|
||||
description: 省份
|
||||
type: string
|
||||
shop_code:
|
||||
description: 店铺编号
|
||||
type: string
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
updated_at:
|
||||
description: 更新时间
|
||||
type: string
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- address
|
||||
- city
|
||||
- contact_name
|
||||
- contact_phone
|
||||
- created_at
|
||||
- district
|
||||
- id
|
||||
- level
|
||||
- parent_id
|
||||
- province
|
||||
- shop_code
|
||||
- shop_name
|
||||
- status
|
||||
- updated_at
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
|
||||
# 创建店铺
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shops:
|
||||
post:
|
||||
summary: 创建店铺
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 店铺管理
|
||||
- 店铺管理
|
||||
parameters: []
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelCreateShopRequest'
|
||||
responses:
|
||||
'200':
|
||||
description: OK
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelShopResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: CgtLTd_zQ5XPrx3y7BdLh
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: CgtLTd_zQ5XPrx3y7BdLh
|
||||
scopes:
|
||||
CgtLTd_zQ5XPrx3y7BdLh:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 店铺管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366340-run
|
||||
components:
|
||||
schemas:
|
||||
ModelCreateShopRequest:
|
||||
properties:
|
||||
address:
|
||||
description: 详细地址
|
||||
maxLength: 255
|
||||
type: string
|
||||
city:
|
||||
description: 城市
|
||||
maxLength: 50
|
||||
type: string
|
||||
contact_name:
|
||||
description: 联系人姓名
|
||||
maxLength: 50
|
||||
type: string
|
||||
contact_phone:
|
||||
description: 联系人电话
|
||||
maxLength: 11
|
||||
minLength: 11
|
||||
type: string
|
||||
district:
|
||||
description: 区县
|
||||
maxLength: 50
|
||||
type: string
|
||||
init_password:
|
||||
description: 初始账号密码
|
||||
maxLength: 32
|
||||
minLength: 8
|
||||
type: string
|
||||
init_phone:
|
||||
description: 初始账号手机号
|
||||
maxLength: 11
|
||||
minLength: 11
|
||||
type: string
|
||||
init_username:
|
||||
description: 初始账号用户名
|
||||
maxLength: 50
|
||||
minLength: 3
|
||||
type: string
|
||||
parent_id:
|
||||
description: 上级店铺ID（一级店铺可不填）
|
||||
minimum: 1
|
||||
type: integer
|
||||
nullable: true
|
||||
province:
|
||||
description: 省份
|
||||
maxLength: 50
|
||||
type: string
|
||||
shop_code:
|
||||
description: 店铺编号
|
||||
maxLength: 50
|
||||
minLength: 1
|
||||
type: string
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
maxLength: 100
|
||||
minLength: 1
|
||||
type: string
|
||||
required:
|
||||
- init_password
|
||||
- init_phone
|
||||
- init_username
|
||||
- shop_code
|
||||
- shop_name
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- address
|
||||
- city
|
||||
- contact_name
|
||||
- contact_phone
|
||||
- district
|
||||
- init_password
|
||||
- init_phone
|
||||
- init_username
|
||||
- parent_id
|
||||
- province
|
||||
- shop_code
|
||||
- shop_name
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ModelShopResponse:
|
||||
properties:
|
||||
address:
|
||||
description: 详细地址
|
||||
type: string
|
||||
city:
|
||||
description: 城市
|
||||
type: string
|
||||
contact_name:
|
||||
description: 联系人姓名
|
||||
type: string
|
||||
contact_phone:
|
||||
description: 联系人电话
|
||||
type: string
|
||||
created_at:
|
||||
description: 创建时间
|
||||
type: string
|
||||
district:
|
||||
description: 区县
|
||||
type: string
|
||||
id:
|
||||
description: 店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
level:
|
||||
description: 店铺层级 (1-7级)
|
||||
type: integer
|
||||
parent_id:
|
||||
description: 上级店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
nullable: true
|
||||
province:
|
||||
description: 省份
|
||||
type: string
|
||||
shop_code:
|
||||
description: 店铺编号
|
||||
type: string
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
updated_at:
|
||||
description: 更新时间
|
||||
type: string
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- address
|
||||
- city
|
||||
- contact_name
|
||||
- contact_phone
|
||||
- created_at
|
||||
- district
|
||||
- id
|
||||
- level
|
||||
- parent_id
|
||||
- province
|
||||
- shop_code
|
||||
- shop_name
|
||||
- status
|
||||
- updated_at
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
# 删除店铺
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shops/{id}:
|
||||
delete:
|
||||
summary: 删除店铺
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 店铺管理
|
||||
- 店铺管理
|
||||
parameters:
|
||||
- name: id
|
||||
in: path
|
||||
description: ID
|
||||
required: true
|
||||
example: 0
|
||||
schema:
|
||||
description: ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
responses:
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: ivp0VlbXbNhnY2xcsCWbS
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: ivp0VlbXbNhnY2xcsCWbS
|
||||
scopes:
|
||||
ivp0VlbXbNhnY2xcsCWbS:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 店铺管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366341-run
|
||||
components:
|
||||
schemas:
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
|
||||
# 更新店铺
|
||||
|
||||
## OpenAPI Specification
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.1
|
||||
info:
|
||||
title: ''
|
||||
description: ''
|
||||
version: 1.0.0
|
||||
paths:
|
||||
/api/admin/shops/{id}:
|
||||
put:
|
||||
summary: 更新店铺
|
||||
deprecated: false
|
||||
description: ''
|
||||
tags:
|
||||
- 店铺管理
|
||||
- 店铺管理
|
||||
parameters:
|
||||
- name: id
|
||||
in: path
|
||||
description: ID
|
||||
required: true
|
||||
example: 0
|
||||
schema:
|
||||
description: ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelUpdateShopParams'
|
||||
responses:
|
||||
'200':
|
||||
description: OK
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/ModelShopResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'400':
|
||||
description: 请求参数错误
|
||||
content:
|
||||
application/json:
|
||||
schema: &ref_0
|
||||
$ref: '#/components/schemas/ErrorResponse'
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'401':
|
||||
description: 未认证或认证已过期
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'403':
|
||||
description: 无权访问
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
'500':
|
||||
description: 服务器内部错误
|
||||
content:
|
||||
application/json:
|
||||
schema: *ref_0
|
||||
headers: {}
|
||||
x-apifox-name: ''
|
||||
security:
|
||||
- BearerAuth: []
|
||||
x-apifox:
|
||||
schemeGroups:
|
||||
- id: 2BoHA3GVAX6-zd8XmFxez
|
||||
schemeIds:
|
||||
- BearerAuth
|
||||
required: true
|
||||
use:
|
||||
id: 2BoHA3GVAX6-zd8XmFxez
|
||||
scopes:
|
||||
2BoHA3GVAX6-zd8XmFxez:
|
||||
BearerAuth: []
|
||||
x-apifox-folder: 店铺管理
|
||||
x-apifox-status: released
|
||||
x-run-in-apifox: https://app.apifox.com/web/project/7591618/apis/api-408366342-run
|
||||
components:
|
||||
schemas:
|
||||
ModelUpdateShopParams:
|
||||
properties:
|
||||
address:
|
||||
description: 详细地址
|
||||
maxLength: 255
|
||||
type: string
|
||||
city:
|
||||
description: 城市
|
||||
maxLength: 50
|
||||
type: string
|
||||
contact_name:
|
||||
description: 联系人姓名
|
||||
maxLength: 50
|
||||
type: string
|
||||
contact_phone:
|
||||
description: 联系人电话
|
||||
maxLength: 11
|
||||
minLength: 11
|
||||
type: string
|
||||
district:
|
||||
description: 区县
|
||||
maxLength: 50
|
||||
type: string
|
||||
province:
|
||||
description: 省份
|
||||
maxLength: 50
|
||||
type: string
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
maxLength: 100
|
||||
minLength: 1
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
required:
|
||||
- shop_name
|
||||
- status
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- address
|
||||
- city
|
||||
- contact_name
|
||||
- contact_phone
|
||||
- district
|
||||
- province
|
||||
- shop_name
|
||||
- status
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ModelShopResponse:
|
||||
properties:
|
||||
address:
|
||||
description: 详细地址
|
||||
type: string
|
||||
city:
|
||||
description: 城市
|
||||
type: string
|
||||
contact_name:
|
||||
description: 联系人姓名
|
||||
type: string
|
||||
contact_phone:
|
||||
description: 联系人电话
|
||||
type: string
|
||||
created_at:
|
||||
description: 创建时间
|
||||
type: string
|
||||
district:
|
||||
description: 区县
|
||||
type: string
|
||||
id:
|
||||
description: 店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
level:
|
||||
description: 店铺层级 (1-7级)
|
||||
type: integer
|
||||
parent_id:
|
||||
description: 上级店铺ID
|
||||
minimum: 0
|
||||
type: integer
|
||||
nullable: true
|
||||
province:
|
||||
description: 省份
|
||||
type: string
|
||||
shop_code:
|
||||
description: 店铺编号
|
||||
type: string
|
||||
shop_name:
|
||||
description: 店铺名称
|
||||
type: string
|
||||
status:
|
||||
description: 状态 (0:禁用, 1:启用)
|
||||
type: integer
|
||||
updated_at:
|
||||
description: 更新时间
|
||||
type: string
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- address
|
||||
- city
|
||||
- contact_name
|
||||
- contact_phone
|
||||
- created_at
|
||||
- district
|
||||
- id
|
||||
- level
|
||||
- parent_id
|
||||
- province
|
||||
- shop_code
|
||||
- shop_name
|
||||
- status
|
||||
- updated_at
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
ErrorResponse:
|
||||
properties:
|
||||
code:
|
||||
description: 错误码
|
||||
type: integer
|
||||
message:
|
||||
description: 错误消息
|
||||
type: string
|
||||
timestamp:
|
||||
description: 时间戳
|
||||
format: date-time
|
||||
type: string
|
||||
required:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
type: object
|
||||
x-apifox-orders:
|
||||
- code
|
||||
- message
|
||||
- timestamp
|
||||
x-apifox-ignore-properties: []
|
||||
x-apifox-folder: ''
|
||||
securitySchemes:
|
||||
BearerAuth:
|
||||
bearerFormat: JWT
|
||||
scheme: bearer
|
||||
type: jwt
|
||||
servers:
|
||||
- url: https://cmp-api.xm-iot.cn
|
||||
description: 测试环境
|
||||
security: []
|
||||
|
||||
```
|
||||
194
docs/开发进度.md
194
docs/开发进度.md
@@ -1,194 +0,0 @@
|
||||
# 物联网卡管理系统 - 开发进度
|
||||
|
||||
> 更新时间: 2026-01-09
|
||||
|
||||
---
|
||||
|
||||
## ✅ 已完成的页面（5个）
|
||||
|
||||
### 账号管理模块 (4/4) ✅
|
||||
- [x] **客户角色管理** `account-management/customer-role/index.vue`
|
||||
- 角色列表、新增、编辑、删除
|
||||
- 能力边界配置（多选框）
|
||||
- 状态管理
|
||||
|
||||
- [x] **代理商管理** `account-management/agent/index.vue`
|
||||
- 代理商列表（多级代理）
|
||||
- 新增/编辑代理商
|
||||
- 账号管理（子账号列表）
|
||||
- 佣金配置（固定/比例佣金）
|
||||
|
||||
- [x] **客户账号管理** `account-management/customer-account/index.vue`
|
||||
- 客户账号列表
|
||||
- 账号详情（Descriptions）
|
||||
- 解绑手机、重置密码
|
||||
- 禁用/启用账号
|
||||
- 操作记录查看
|
||||
|
||||
- [x] **企业客户管理** `account-management/customer/index.vue`
|
||||
- ⚠️ 已存在，无需创建
|
||||
|
||||
### 商品管理模块 (1/2)
|
||||
- [x] **号卡管理** `product/sim-card/index.vue`
|
||||
- 号卡列表（运营商筛选）
|
||||
- 新增/编辑号卡
|
||||
- 上架/下架管理
|
||||
- 库存管理
|
||||
|
||||
---
|
||||
|
||||
## 📋 待创建的页面（10个）
|
||||
|
||||
### 1. 账号管理模块
|
||||
- [ ] **客户账号佣金** `account-management/customer-commission/index.vue`
|
||||
- 佣金统计卡片
|
||||
- 佣金明细列表
|
||||
- 提现记录
|
||||
|
||||
### 2. 财务管理模块 (0/3)
|
||||
- [ ] **佣金提现管理** `finance/withdrawal/index.vue`
|
||||
- 提现申请列表（状态筛选）
|
||||
- 审核功能（通过/拒绝）
|
||||
- 批量审核
|
||||
- 提现记录导出
|
||||
|
||||
- [ ] **佣金提现设置** `finance/withdrawal-settings/index.vue`
|
||||
- 提现参数配置（最低金额、手续费等）
|
||||
- 配置历史记录
|
||||
|
||||
- [ ] **我的账户** `finance/my-account/index.vue`
|
||||
- 账户概览（卡片统计）
|
||||
- 佣金收入明细
|
||||
- 提现申请功能
|
||||
- 收支流水记录
|
||||
|
||||
### 3. 设置管理模块 (0/3)
|
||||
- [ ] **收款商户设置** `settings/payment-merchant/index.vue`
|
||||
- 支付商户信息配置
|
||||
- API 密钥管理
|
||||
- 回调地址设置
|
||||
- 支付方式管理（微信/支付宝/银行卡）
|
||||
|
||||
- [ ] **开发能力管理** `settings/developer-api/index.vue`
|
||||
- API 密钥列表
|
||||
- 生成/重置密钥
|
||||
- Webhook 配置
|
||||
- API 调用统计
|
||||
|
||||
- [ ] **分佣模板** `settings/commission-template/index.vue`
|
||||
- 分佣模板列表
|
||||
- 新增/编辑模板
|
||||
- 分佣规则配置
|
||||
- 模板应用记录
|
||||
|
||||
### 4. 商品管理模块
|
||||
- [ ] **号卡分配** `product/sim-card-assign/index.vue`
|
||||
- 分配记录列表
|
||||
- 为代理商分配号卡
|
||||
- 设置佣金模式
|
||||
- 分配统计报表
|
||||
|
||||
### 5. 批量操作模块 (0/3)
|
||||
- [ ] **网卡批量导入** `batch/sim-import/index.vue`
|
||||
- Excel 上传（模板下载）
|
||||
- 导入任务列表
|
||||
- 导入结果查看（成功/失败）
|
||||
|
||||
- [ ] **设备批量导入** `batch/device-import/index.vue`
|
||||
- Excel 上传（设备+ICCID关系）
|
||||
- 导入任务列表
|
||||
- 导入结果查看
|
||||
|
||||
- [ ] **换卡通知** `batch/card-change-notice/index.vue`
|
||||
- 换卡通知列表
|
||||
- 单独/批量创建通知
|
||||
- 通知方式选择（短信/邮件）
|
||||
- 通知记录查看
|
||||
|
||||
---
|
||||
|
||||
## 📂 项目文件结构
|
||||
|
||||
```
|
||||
src/views/
|
||||
├── account-management/ # 账号管理
|
||||
│ ├── customer/ ✅ 已存在
|
||||
│ ├── customer-role/ ✅ 已创建
|
||||
│ ├── agent/ ✅ 已创建
|
||||
│ ├── customer-account/ ✅ 已创建
|
||||
│ └── customer-commission/ ❌ 待创建
|
||||
├── finance/ # 财务管理
|
||||
│ ├── withdrawal/ ❌ 待创建
|
||||
│ ├── withdrawal-settings/ ❌ 待创建
|
||||
│ └── my-account/ ❌ 待创建
|
||||
├── settings/ # 设置管理
|
||||
│ ├── payment-merchant/ ❌ 待创建
|
||||
│ ├── developer-api/ ❌ 待创建
|
||||
│ └── commission-template/ ❌ 待创建
|
||||
├── product/ # 商品管理
|
||||
│ ├── sim-card/ ✅ 已创建
|
||||
│ └── sim-card-assign/ ❌ 待创建
|
||||
└── batch/ # 批量操作
|
||||
├── sim-import/ ❌ 待创建
|
||||
├── device-import/ ❌ 待创建
|
||||
└── card-change-notice/ ❌ 待创建
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🚀 快速创建指南
|
||||
|
||||
### 方法1: 使用模板快速创建
|
||||
参考 `docs/页面创建模板.md` 中的标准模板，只需：
|
||||
1. 复制模板代码
|
||||
2. 修改组件名和接口定义
|
||||
3. 调整 Mock 数据
|
||||
4. 根据需求调整表单和表格
|
||||
|
||||
### 方法2: 复制现有页面修改
|
||||
推荐复制以下页面作为基础：
|
||||
- **列表+CRUD**: 复制 `customer-role/index.vue`
|
||||
- **复杂列表+多对话框**: 复制 `agent/index.vue`
|
||||
- **详情查看**: 复制 `customer-account/index.vue`
|
||||
|
||||
---
|
||||
|
||||
## 📌 下一步工作
|
||||
|
||||
### 优先级1 - 核心业务页面
|
||||
1. ⚠️ 财务管理模块（3个页面）- 核心功能
|
||||
2. ⚠️ 商品管理 - 号卡分配
|
||||
|
||||
### 优先级2 - 辅助功能页面
|
||||
3. 设置管理模块（3个页面）
|
||||
4. 批量操作模块（3个页面）
|
||||
5. 客户账号佣金页面
|
||||
|
||||
### 优先级3 - 路由和配置
|
||||
6. 更新 `src/router/routesAlias.ts` 添加新路由别名
|
||||
7. 更新 `src/router/routes/asyncRoutes.ts` 添加路由配置
|
||||
8. 测试所有页面是否正常访问
|
||||
|
||||
---
|
||||
|
||||
## ✨ 已完成的文档
|
||||
|
||||
- ✅ `docs/任务规划.md` - 完整的任务规划和分解
|
||||
- ✅ `docs/页面创建模板.md` - 标准页面模板和快速创建指南
|
||||
- ✅ `docs/开发进度.md` - 当前开发进度追踪
|
||||
|
||||
---
|
||||
|
||||
## 💡 开发建议
|
||||
|
||||
1. **使用模板**：严格按照模板创建，保持代码风格一致
|
||||
2. **Mock 数据**：确保 Mock 数据完整且真实，方便测试
|
||||
3. **组件复用**：最大化使用 ArtTable 等现有组件
|
||||
4. **渐进开发**：先完成基础功能，再添加高级特性
|
||||
5. **及时测试**：每完成一个页面立即测试功能
|
||||
|
||||
---
|
||||
|
||||
**总体完成度**: 5/15 页面 (33.3%)
|
||||
|
||||
继续加油！🚀
|
||||
378
docs/新功能.md
378
docs/新功能.md
@@ -1,378 +0,0 @@
|
||||
# 在账号管理下面新增一个平台账号, 然后需要写页面对接API, 页面样式可以参考/system/account 都需要token认证 逻辑啥的跟/system/account差不多
|
||||
|
||||
## 1. 平台账号列表
|
||||
|
||||
```json
|
||||
"url": "/api/admin/platform-accounts",
|
||||
"methods": "GET",
|
||||
Query 参数:
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 页码
|
||||
*/
|
||||
page?: number;
|
||||
/**
|
||||
* 每页数量
|
||||
*/
|
||||
page_size?: number;
|
||||
/**
|
||||
* 手机号模糊查询
|
||||
*/
|
||||
phone?: string;
|
||||
/**
|
||||
* 状态 (0:禁用, 1:启用)
|
||||
*/
|
||||
status?: number | null;
|
||||
/**
|
||||
* 用户名模糊查询
|
||||
*/
|
||||
username?: string;
|
||||
[property: string]: any;
|
||||
}
|
||||
返回响应
|
||||
/**
|
||||
* ModelAccountPageResult
|
||||
*/
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 账号列表
|
||||
*/
|
||||
items?: ModelAccountResponse[] | null;
|
||||
/**
|
||||
* 当前页码
|
||||
*/
|
||||
page?: number;
|
||||
/**
|
||||
* 每页数量
|
||||
*/
|
||||
size?: number;
|
||||
/**
|
||||
* 总记录数
|
||||
*/
|
||||
total?: number;
|
||||
[property: string]: any;
|
||||
}
|
||||
|
||||
/**
|
||||
* ModelAccountResponse
|
||||
*/
|
||||
export interface ModelAccountResponse {
|
||||
/**
|
||||
* 创建时间
|
||||
*/
|
||||
created_at?: string;
|
||||
/**
|
||||
* 创建人ID
|
||||
*/
|
||||
creator?: number;
|
||||
/**
|
||||
* 关联企业ID
|
||||
*/
|
||||
enterprise_id?: number | null;
|
||||
/**
|
||||
* 账号ID
|
||||
*/
|
||||
id?: number;
|
||||
/**
|
||||
* 手机号
|
||||
*/
|
||||
phone?: string;
|
||||
/**
|
||||
* 关联店铺ID
|
||||
*/
|
||||
shop_id?: number | null;
|
||||
/**
|
||||
* 状态 (0:禁用, 1:启用)
|
||||
*/
|
||||
status?: number;
|
||||
/**
|
||||
* 更新时间
|
||||
*/
|
||||
updated_at?: string;
|
||||
/**
|
||||
* 更新人ID
|
||||
*/
|
||||
updater?: number;
|
||||
/**
|
||||
* 用户类型 (1:超级管理员, 2:平台用户, 3:代理账号, 4:企业账号)
|
||||
*/
|
||||
user_type?: number;
|
||||
/**
|
||||
* 用户名
|
||||
*/
|
||||
username?: string;
|
||||
[property: string]: any;
|
||||
}
|
||||
|
||||
{
|
||||
"items": [
|
||||
{
|
||||
"created_at": "string",
|
||||
"creator": 0,
|
||||
"enterprise_id": 0,
|
||||
"id": 0,
|
||||
"phone": "string",
|
||||
"shop_id": 0,
|
||||
"status": 0,
|
||||
"updated_at": "string",
|
||||
"updater": 0,
|
||||
"user_type": 0,
|
||||
"username": "string"
|
||||
}
|
||||
],
|
||||
"page": 0,
|
||||
"size": 0,
|
||||
"total": 0
|
||||
}
|
||||
```
|
||||
|
||||
## 2. 新增平台账号
|
||||
url: /api/admin/platform-accounts,
|
||||
methods: post,
|
||||
Body 参数
|
||||
/**
|
||||
* ModelCreateAccountRequest
|
||||
*/
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 关联企业ID（企业账号必填）
|
||||
*/
|
||||
enterprise_id?: number | null;
|
||||
/**
|
||||
* 密码
|
||||
*/
|
||||
password: string;
|
||||
/**
|
||||
* 手机号
|
||||
*/
|
||||
phone: string;
|
||||
/**
|
||||
* 关联店铺ID（代理账号必填）
|
||||
*/
|
||||
shop_id?: number | null;
|
||||
/**
|
||||
* 用户类型 (1:超级管理员, 2:平台用户, 3:代理账号, 4:企业账号)
|
||||
*/
|
||||
user_type: number;
|
||||
/**
|
||||
* 用户名
|
||||
*/
|
||||
username: string;
|
||||
[property: string]: any;
|
||||
}
|
||||
返回响应:
|
||||
/**
|
||||
* ModelAccountResponse
|
||||
*/
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 创建时间
|
||||
*/
|
||||
created_at?: string;
|
||||
/**
|
||||
* 创建人ID
|
||||
*/
|
||||
creator?: number;
|
||||
/**
|
||||
* 关联企业ID
|
||||
*/
|
||||
enterprise_id?: number | null;
|
||||
/**
|
||||
* 账号ID
|
||||
*/
|
||||
id?: number;
|
||||
/**
|
||||
* 手机号
|
||||
*/
|
||||
phone?: string;
|
||||
/**
|
||||
* 关联店铺ID
|
||||
*/
|
||||
shop_id?: number | null;
|
||||
/**
|
||||
* 状态 (0:禁用, 1:启用)
|
||||
*/
|
||||
status?: number;
|
||||
/**
|
||||
* 更新时间
|
||||
*/
|
||||
updated_at?: string;
|
||||
/**
|
||||
* 更新人ID
|
||||
*/
|
||||
updater?: number;
|
||||
/**
|
||||
* 用户类型 (1:超级管理员, 2:平台用户, 3:代理账号, 4:企业账号)
|
||||
*/
|
||||
user_type?: number;
|
||||
/**
|
||||
* 用户名
|
||||
*/
|
||||
username?: string;
|
||||
[property: string]: any;
|
||||
}
|
||||
*
|
||||
{
|
||||
"created_at": "string",
|
||||
"creator": 0,
|
||||
"enterprise_id": 0,
|
||||
"id": 0,
|
||||
"phone": "string",
|
||||
"shop_id": 0,
|
||||
"status": 0,
|
||||
"updated_at": "string",
|
||||
"updater": 0,
|
||||
"user_type": 0,
|
||||
"username": "string"
|
||||
}
|
||||
|
||||
|
||||
|
||||
## 3. 移除角色
|
||||
url: /api/admin/platform-accounts/{account_id}/roles/{role_id}
|
||||
methods: delete
|
||||
path参数:
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 账号ID
|
||||
*/
|
||||
account_id: number;
|
||||
/**
|
||||
* 角色ID
|
||||
*/
|
||||
role_id: number;
|
||||
[property: string]: any;
|
||||
}
|
||||
* 返回响应:
|
||||
* {
|
||||
"code": 0,
|
||||
"message": "string",
|
||||
"timestamp": "2019-08-24T14:15:22.123Z"
|
||||
}
|
||||
|
||||
|
||||
## 4. 删除平台账号
|
||||
url: /api/admin/platform-accounts/{id}
|
||||
methods: delete
|
||||
path参数:
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* ID
|
||||
*/
|
||||
id: number;
|
||||
[property: string]: any;
|
||||
}
|
||||
响应:
|
||||
* {
|
||||
"code": 0,
|
||||
"message": "string",
|
||||
"timestamp": "2019-08-24T14:15:22.123Z"
|
||||
}
|
||||
|
||||
|
||||
## 5. 获取平台账号详情
|
||||
url: /api/admin/platform-accounts/{id}
|
||||
methods: get
|
||||
响应: {
|
||||
"created_at": "string",
|
||||
"creator": 0,
|
||||
"enterprise_id": 0,
|
||||
"id": 0,
|
||||
"phone": "string",
|
||||
"shop_id": 0,
|
||||
"status": 0,
|
||||
"updated_at": "string",
|
||||
"updater": 0,
|
||||
"user_type": 0,
|
||||
"username": "string"
|
||||
}
|
||||
|
||||
## 6. 编辑平台账号
|
||||
url: /api/admin/platform-accounts/{id}
|
||||
methods: put
|
||||
body:/**
|
||||
* ModelUpdateAccountParams
|
||||
*/
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 密码
|
||||
*/
|
||||
password?: null | string;
|
||||
/**
|
||||
* 手机号
|
||||
*/
|
||||
phone?: null | string;
|
||||
/**
|
||||
* 状态 (0:禁用, 1:启用)
|
||||
*/
|
||||
status?: number | null;
|
||||
/**
|
||||
* 用户名
|
||||
*/
|
||||
username?: null | string;
|
||||
[property: string]: any;
|
||||
}
|
||||
响应: {
|
||||
"created_at": "string",
|
||||
"creator": 0,
|
||||
"enterprise_id": 0,
|
||||
"id": 0,
|
||||
"phone": "string",
|
||||
"shop_id": 0,
|
||||
"status": 0,
|
||||
"updated_at": "string",
|
||||
"updater": 0,
|
||||
"user_type": 0,
|
||||
"username": "string"
|
||||
}
|
||||
|
||||
## 7. 修改密码
|
||||
url: /api/admin/platform-accounts/{id}/password
|
||||
methods: put
|
||||
body:{
|
||||
"new_password": "stringst"
|
||||
}
|
||||
response: {
|
||||
"code": 0,
|
||||
"message": "string",
|
||||
"timestamp": "2019-08-24T14:15:22.123Z"
|
||||
}
|
||||
|
||||
|
||||
|
||||
## 8. 获取账号角色
|
||||
url: /api/admin/platform-accounts/{id}/roles
|
||||
methods: get
|
||||
响应: [
|
||||
{
|
||||
"creator": 0,
|
||||
"role_desc": "string",
|
||||
"role_name": "string",
|
||||
"role_type": 0,
|
||||
"status": 0,
|
||||
"updater": 0
|
||||
}
|
||||
]
|
||||
|
||||
|
||||
## 9. 分配角色
|
||||
url: /api/admin/platform-accounts/{id}/roles,
|
||||
methods: post
|
||||
body: {
|
||||
"role_ids": [
|
||||
0
|
||||
]
|
||||
}
|
||||
响应: {
|
||||
"code": 0,
|
||||
"message": "string",
|
||||
"timestamp": "2019-08-24T14:15:22.123Z"
|
||||
}
|
||||
|
||||
|
||||
## 10. 启用/禁用账号
|
||||
url: /api/admin/platform-accounts/{id}/status
|
||||
methods: put,
|
||||
body: {
|
||||
"status": 0
|
||||
}
|
||||
@@ -1,72 +0,0 @@
|
||||
# 角色管理中少了三个接口对接
|
||||
|
||||
## 1. 获取角色权限
|
||||
url: /api/admin/roles/{id}/permissions
|
||||
methods: get
|
||||
response: [
|
||||
{
|
||||
"available_for_role_types": "string",
|
||||
"creator": 0,
|
||||
"parent_id": 0,
|
||||
"perm_code": "string",
|
||||
"perm_name": "string",
|
||||
"perm_type": 0,
|
||||
"platform": "string",
|
||||
"sort": 0,
|
||||
"status": 0,
|
||||
"updater": 0,
|
||||
"url": "string"
|
||||
}
|
||||
]
|
||||
/**
|
||||
* ModelPermission
|
||||
*/
|
||||
export interface ApifoxModel {
|
||||
available_for_role_types?: string;
|
||||
creator?: number;
|
||||
parent_id?: number | null;
|
||||
perm_code?: string;
|
||||
perm_name?: string;
|
||||
perm_type?: number;
|
||||
platform?: string;
|
||||
sort?: number;
|
||||
status?: number;
|
||||
updater?: number;
|
||||
url?: string;
|
||||
[property: string]: any;
|
||||
}
|
||||
|
||||
## 2. 分配权限
|
||||
url: /api/admin/roles/{id}/permissions
|
||||
methods: post
|
||||
body: {
|
||||
"perm_ids": [
|
||||
0
|
||||
]
|
||||
}
|
||||
response: {
|
||||
"code": 0,
|
||||
"message": "string",
|
||||
"timestamp": "2019-08-24T14:15:22.123Z"
|
||||
}
|
||||
## 3. 移除权限
|
||||
url: /api/admin/roles/{role_id}/permissions/{perm_id}
|
||||
export interface ApifoxModel {
|
||||
/**
|
||||
* 权限ID
|
||||
*/
|
||||
perm_id: number;
|
||||
/**
|
||||
* 角色ID
|
||||
*/
|
||||
role_id: number;
|
||||
[property: string]: any;
|
||||
}
|
||||
|
||||
methods: delete
|
||||
|
||||
响应: {
|
||||
"code": 0,
|
||||
"message": "string",
|
||||
"timestamp": "2019-08-24T14:15:22.123Z"
|
||||
}
|
||||
6146
docs/部分API.md
6146
docs/部分API.md
File diff suppressed because it is too large
Load Diff
297
docs/页面创建模板.md
297
docs/页面创建模板.md
@@ -1,297 +0,0 @@
|
||||
# 页面创建模板
|
||||
|
||||
本文档提供快速创建页面的模板，所有页面遵循统一的风格和结构。
|
||||
|
||||
## 📋 已完成的页面
|
||||
|
||||
### ✅ 账号管理模块
|
||||
- [x] 客户角色管理 (`account-management/customer-role`)
|
||||
- [x] 代理商管理 (`account-management/agent`)
|
||||
- [x] 客户账号管理 (`account-management/customer-account`)
|
||||
- [ ] 客户账号佣金 (`account-management/customer-commission`) - 待创建
|
||||
|
||||
### ✅ 商品管理模块
|
||||
- [x] 号卡管理 (`product/sim-card`)
|
||||
- [ ] 号卡分配 (`product/sim-card-assign`) - 待创建
|
||||
|
||||
## 🔨 待创建的页面
|
||||
|
||||
### 财务管理模块 (`finance/`)
|
||||
1. **佣金提现管理** (`withdrawal/index.vue`)
|
||||
2. **佣金提现设置** (`withdrawal-settings/index.vue`)
|
||||
3. **我的账户** (`my-account/index.vue`)
|
||||
|
||||
### 设置管理模块 (`settings/`)
|
||||
1. **收款商户设置** (`payment-merchant/index.vue`)
|
||||
2. **开发能力管理** (`developer-api/index.vue`)
|
||||
3. **分佣模板** (`commission-template/index.vue`)
|
||||
|
||||
### 批量操作模块 (`batch/`)
|
||||
1. **网卡批量导入** (`sim-import/index.vue`)
|
||||
2. **设备批量导入** (`device-import/index.vue`)
|
||||
3. **换卡通知** (`card-change-notice/index.vue`)
|
||||
|
||||
---
|
||||
|
||||
## 📝 标准页面模板
|
||||
|
||||
### 基础列表页面模板
|
||||
|
||||
```vue
|
||||
<template>
|
||||
<div class="page-content">
|
||||
<!-- 搜索栏 -->
|
||||
<ElRow>
|
||||
<ElCol :xs="24" :sm="12" :lg="6">
|
||||
<ElInput v-model="searchQuery" placeholder="搜索关键词" clearable></ElInput>
|
||||
</ElCol>
|
||||
<div style="width: 12px"></div>
|
||||
<ElCol :xs="24" :sm="12" :lg="6" class="el-col2">
|
||||
<ElButton v-ripple @click="handleSearch">搜索</ElButton>
|
||||
<ElButton v-ripple @click="showDialog('add')">新增</ElButton>
|
||||
</ElCol>
|
||||
</ElRow>
|
||||
|
||||
<!-- 表格 -->
|
||||
<ArtTable :data="filteredData" index>
|
||||
<template #default>
|
||||
<ElTableColumn label="名称" prop="name" />
|
||||
<ElTableColumn label="编码" prop="code" />
|
||||
<ElTableColumn label="状态" prop="status">
|
||||
<template #default="scope">
|
||||
<ElTag :type="scope.row.status === 'active' ? 'success' : 'info'">
|
||||
{{ scope.row.status === 'active' ? '启用' : '禁用' }}
|
||||
</ElTag>
|
||||
</template>
|
||||
</ElTableColumn>
|
||||
<ElTableColumn label="创建时间" prop="createTime" width="180" />
|
||||
<ElTableColumn fixed="right" label="操作" width="180">
|
||||
<template #default="scope">
|
||||
<el-button link @click="showDialog('edit', scope.row)">编辑</el-button>
|
||||
<el-button link @click="handleDelete(scope.row)">删除</el-button>
|
||||
</template>
|
||||
</ElTableColumn>
|
||||
</template>
|
||||
</ArtTable>
|
||||
|
||||
<!-- 新增/编辑对话框 -->
|
||||
<ElDialog
|
||||
v-model="dialogVisible"
|
||||
:title="dialogType === 'add' ? '新增' : '编辑'"
|
||||
width="600px"
|
||||
align-center
|
||||
>
|
||||
<ElForm ref="formRef" :model="form" :rules="rules" label-width="120px">
|
||||
<ElFormItem label="名称" prop="name">
|
||||
<ElInput v-model="form.name" placeholder="请输入名称" />
|
||||
</ElFormItem>
|
||||
<ElFormItem label="编码" prop="code">
|
||||
<ElInput v-model="form.code" placeholder="请输入编码" />
|
||||
</ElFormItem>
|
||||
<ElFormItem label="状态">
|
||||
<ElSwitch v-model="form.status" active-value="active" inactive-value="inactive" />
|
||||
</ElFormItem>
|
||||
</ElForm>
|
||||
<template #footer>
|
||||
<div class="dialog-footer">
|
||||
<ElButton @click="dialogVisible = false">取消</ElButton>
|
||||
<ElButton type="primary" @click="handleSubmit(formRef)">提交</ElButton>
|
||||
</div>
|
||||
</template>
|
||||
</ElDialog>
|
||||
</div>
|
||||
</template>
|
||||
|
||||
<script setup lang="ts">
|
||||
import { ElMessage, ElMessageBox } from 'element-plus'
|
||||
import type { FormInstance, FormRules } from 'element-plus'
|
||||
|
||||
defineOptions({ name: 'YourPageName' })
|
||||
|
||||
interface DataItem {
|
||||
id?: string
|
||||
name: string
|
||||
code: string
|
||||
status: 'active' | 'inactive'
|
||||
createTime?: string
|
||||
}
|
||||
|
||||
// Mock 数据
|
||||
const mockData = ref<DataItem[]>([
|
||||
{
|
||||
id: '1',
|
||||
name: '示例数据1',
|
||||
code: 'CODE001',
|
||||
status: 'active',
|
||||
createTime: '2026-01-01 10:00:00'
|
||||
}
|
||||
])
|
||||
|
||||
const searchQuery = ref('')
|
||||
const dialogVisible = ref(false)
|
||||
const dialogType = ref<'add' | 'edit'>('add')
|
||||
const formRef = ref<FormInstance>()
|
||||
|
||||
const form = reactive<DataItem>({
|
||||
name: '',
|
||||
code: '',
|
||||
status: 'active'
|
||||
})
|
||||
|
||||
const rules = reactive<FormRules>({
|
||||
name: [{ required: true, message: '请输入名称', trigger: 'blur' }],
|
||||
code: [{ required: true, message: '请输入编码', trigger: 'blur' }]
|
||||
})
|
||||
|
||||
const filteredData = computed(() => {
|
||||
if (!searchQuery.value) return mockData.value
|
||||
return mockData.value.filter((item) =>
|
||||
item.name.toLowerCase().includes(searchQuery.value.toLowerCase())
|
||||
)
|
||||
})
|
||||
|
||||
const handleSearch = () => {}
|
||||
|
||||
const showDialog = (type: 'add' | 'edit', row?: DataItem) => {
|
||||
dialogType.value = type
|
||||
dialogVisible.value = true
|
||||
if (type === 'edit' && row) {
|
||||
Object.assign(form, row)
|
||||
} else {
|
||||
Object.assign(form, { name: '', code: '', status: 'active' })
|
||||
}
|
||||
}
|
||||
|
||||
const handleSubmit = async (formEl: FormInstance | undefined) => {
|
||||
if (!formEl) return
|
||||
await formEl.validate((valid) => {
|
||||
if (valid) {
|
||||
if (dialogType.value === 'add') {
|
||||
mockData.value.push({
|
||||
...form,
|
||||
id: Date.now().toString(),
|
||||
createTime: new Date().toLocaleString('zh-CN')
|
||||
})
|
||||
ElMessage.success('新增成功')
|
||||
} else {
|
||||
const index = mockData.value.findIndex((item) => item.id === form.id)
|
||||
if (index !== -1) mockData.value[index] = { ...form }
|
||||
ElMessage.success('修改成功')
|
||||
}
|
||||
dialogVisible.value = false
|
||||
formEl.resetFields()
|
||||
}
|
||||
})
|
||||
}
|
||||
|
||||
const handleDelete = (row: DataItem) => {
|
||||
ElMessageBox.confirm('确定删除吗？', '删除确认', {
|
||||
confirmButtonText: '确定',
|
||||
cancelButtonText: '取消',
|
||||
type: 'error'
|
||||
}).then(() => {
|
||||
const index = mockData.value.findIndex((item) => item.id === row.id)
|
||||
if (index !== -1) mockData.value.splice(index, 1)
|
||||
ElMessage.success('删除成功')
|
||||
})
|
||||
}
|
||||
</script>
|
||||
|
||||
<style lang="scss" scoped>
|
||||
.page-content {
|
||||
// 自定义样式
|
||||
}
|
||||
</style>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 快速创建步骤
|
||||
|
||||
1. **复制模板**：复制上面的标准模板
|
||||
2. **修改组件名**：修改 `defineOptions({ name: 'YourPageName' })`
|
||||
3. **调整接口**：根据业务需求修改 `DataItem` 接口
|
||||
4. **修改 Mock 数据**：替换 `mockData` 中的示例数据
|
||||
5. **调整表单字段**：根据需求增删表单项
|
||||
6. **调整表格列**：修改 `ElTableColumn` 配置
|
||||
|
||||
---
|
||||
|
||||
## 📚 常用组件
|
||||
|
||||
### 1. ArtTable - 表格组件
|
||||
```vue
|
||||
<ArtTable :data="tableData" index>
|
||||
<template #default>
|
||||
<ElTableColumn label="列名" prop="propName" />
|
||||
</template>
|
||||
</ArtTable>
|
||||
```
|
||||
|
||||
### 2. 搜索栏布局
|
||||
```vue
|
||||
<ElRow>
|
||||
<ElCol :xs="24" :sm="12" :lg="6">
|
||||
<ElInput v-model="search" placeholder="搜索" clearable />
|
||||
</ElCol>
|
||||
<div style="width: 12px"></div>
|
||||
<ElCol :xs="24" :sm="12" :lg="6">
|
||||
<ElSelect v-model="filter" placeholder="筛选" clearable style="width: 100%">
|
||||
<ElOption label="选项1" value="1" />
|
||||
</ElSelect>
|
||||
</ElCol>
|
||||
<div style="width: 12px"></div>
|
||||
<ElCol :xs="24" :sm="12" :lg="6" class="el-col2">
|
||||
<ElButton v-ripple>搜索</ElButton>
|
||||
</ElCol>
|
||||
</ElRow>
|
||||
```
|
||||
|
||||
### 3. 状态标签
|
||||
```vue
|
||||
<ElTag :type="getStatusType(status)">
|
||||
{{ getStatusText(status) }}
|
||||
</ElTag>
|
||||
```
|
||||
|
||||
### 4. 操作按钮
|
||||
```vue
|
||||
<el-button link @click="handleEdit(row)">编辑</el-button>
|
||||
<el-button link type="danger" @click="handleDelete(row)">删除</el-button>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 💡 开发规范
|
||||
|
||||
1. **命名规范**
|
||||
- 组件名：大驼峰 `YourComponent`
|
||||
- 变量名：小驼峰 `yourVariable`
|
||||
- 文件名：小写+连字符 `your-file.vue`
|
||||
|
||||
2. **Mock 数据格式**
|
||||
- 统一使用 `ref<Type[]>([])` 定义
|
||||
- 包含 `id`, `createTime` 等公共字段
|
||||
- 数据应具有代表性，便于测试
|
||||
|
||||
3. **表单验证**
|
||||
- 必填字段添加 `required` 规则
|
||||
- 手机号/邮箱使用正则验证
|
||||
- 提供友好的错误提示
|
||||
|
||||
4. **用户体验**
|
||||
- 操作前使用 `ElMessageBox.confirm` 确认
|
||||
- 操作后使用 `ElMessage` 提示结果
|
||||
- 表单提交后关闭对话框并重置
|
||||
|
||||
---
|
||||
|
||||
## 🔄 下一步
|
||||
|
||||
1. 根据模板快速创建剩余页面
|
||||
2. 完善 Mock 数据使其更真实
|
||||
3. 添加路由配置
|
||||
4. 测试页面功能
|
||||
5. 优化用户体验
|
||||
|
||||
祝开发顺利！🚀
|
||||
433
docs/项目完成总结.md
433
docs/项目完成总结.md
@@ -1,433 +0,0 @@
|
||||
# 物联网卡管理系统 - 完整项目总结
|
||||
|
||||
## 📊 完成概况
|
||||
|
||||
**完成时间**: 2026-01-09
|
||||
**开发进度**: 18/18 页面 (100%)
|
||||
**总计文件**: 18 个 Vue 页面组件
|
||||
**状态**: ✅ 全部完成
|
||||
|
||||
---
|
||||
|
||||
## ✅ 新创建的页面列表（18个）
|
||||
|
||||
### 第一批：基础模块（13个页面）
|
||||
|
||||
#### 1. 账号管理模块 (3个)
|
||||
1. **客户角色管理** - `src/views/account-management/customer-role/index.vue`
|
||||
2. **代理商管理** - `src/views/account-management/agent/index.vue`
|
||||
3. **客户账号管理** - `src/views/account-management/customer-account/index.vue`
|
||||
|
||||
#### 2. 财务管理模块 (3个)
|
||||
4. **提现管理** - `src/views/finance/withdrawal/index.vue`
|
||||
5. **我的账户** - `src/views/finance/my-account/index.vue`
|
||||
6. **提现设置** - `src/views/finance/withdrawal-settings/index.vue`
|
||||
|
||||
#### 3. 设置管理模块 (3个)
|
||||
7. **支付商户配置** - `src/views/settings/payment-merchant/index.vue`
|
||||
8. **开发者API管理** - `src/views/settings/developer-api/index.vue`
|
||||
9. **分佣模板管理** - `src/views/settings/commission-template/index.vue`
|
||||
|
||||
#### 4. 批量操作模块 (3个)
|
||||
10. **网卡批量导入** - `src/views/batch/sim-import/index.vue`
|
||||
11. **设备批量导入** - `src/views/batch/device-import/index.vue`
|
||||
12. **换卡通知管理** - `src/views/batch/card-change-notice/index.vue`
|
||||
|
||||
#### 5. 产品管理模块 (1个)
|
||||
13. **网卡产品管理** - `src/views/product/sim-card/index.vue`
|
||||
|
||||
---
|
||||
|
||||
### 第二批：补充模块（5个页面）
|
||||
|
||||
#### 6. 账号管理扩展 (2个)
|
||||
14. **企业客户管理** - `src/views/account-management/enterprise-customer/index.vue`
|
||||
- 创建企业管理账号，只能登录企业端
|
||||
- 依赖客户角色，决定能力边界
|
||||
- 营业执照上传，统一社会信用代码管理
|
||||
- 角色分配和初始余额设置
|
||||
|
||||
15. **客户账号佣金** - `src/views/account-management/customer-commission/index.vue`
|
||||
- 查看账号下全部客户的佣金情况
|
||||
- 提现情况统计和查询
|
||||
- 佣金明细和提现记录
|
||||
- 统计卡片展示（总佣金、已提现、待提现）
|
||||
|
||||
#### 7. 商品管理扩展 (1个)
|
||||
16. **号卡分配** - `src/views/product/sim-card-assign/index.vue`
|
||||
- 为特定代理分配号卡商品
|
||||
- 设置分佣模式（固定/比例/模板）
|
||||
- 特殊折扣设置
|
||||
- 分配记录和取消分配功能
|
||||
|
||||
#### 8. 资产管理模块 (2个)
|
||||
17. **资产分配** - `src/views/asset-management/asset-assign/index.vue`
|
||||
- 支持三种分配模式：网卡批量分配、设备批量分配、网卡+设备分配
|
||||
- 网卡有设备信息时，可同时分配网卡和设备
|
||||
- 批量选择和分配给代理商
|
||||
- 分配记录和批次管理
|
||||
|
||||
18. **换卡申请管理** - `src/views/asset-management/card-replacement-request/index.vue`
|
||||
- 客户提交的换卡申请管理
|
||||
- 处理换卡申请，填充新ICCID
|
||||
- 新卡验证和自动换卡操作
|
||||
- 申请审核（通过/拒绝）
|
||||
|
||||
---
|
||||
|
||||
## 📦 已存在的页面（复用）
|
||||
|
||||
项目中以下页面已经存在，功能完整，无需重复创建：
|
||||
|
||||
### 卡片管理（card-management）
|
||||
- ✓ 单卡信息 - `card-management/single-card`
|
||||
- ✓ 网卡管理 - `card-management/card-list`
|
||||
- ✓ 网卡明细 - `card-management/card-detail`
|
||||
- ✓ 网卡分配 - `card-management/card-assign`
|
||||
- ✓ 停机管理 - `card-management/card-shutdown`
|
||||
- ✓ 我的网卡 - `card-management/my-cards`
|
||||
- ✓ 线下批量充值 - `card-management/offline-batch-recharge`
|
||||
- ✓ 网卡转接 - `card-management/card-transfer`
|
||||
- ✓ 换卡管理 - `card-management/card-replacement`
|
||||
- ✓ 套餐赠送 - `card-management/package-gift`
|
||||
- ✓ 换卡网卡 - `card-management/card-change-card`
|
||||
|
||||
### 套餐管理（package-management）
|
||||
- ✓ 新建套餐 - `package-management/package-create`
|
||||
- ✓ 批量管理 - `package-management/package-batch`
|
||||
- ✓ 我的套餐 - `package-management/package-list`
|
||||
- ✓ 套餐变更 - `package-management/package-change`
|
||||
- ✓ 套餐分配 - `package-management/package-assign`
|
||||
- ✓ 套餐系列 - `package-management/package-series`
|
||||
- ✓ 套餐佣金 - `package-management/package-commission`
|
||||
|
||||
### 设备管理（device-management）
|
||||
- ✓ 设备管理 - `device-management/devices`
|
||||
|
||||
### 客户管理（account-management）
|
||||
- ✓ 客户管理 - `account-management/customer`
|
||||
|
||||
---
|
||||
|
||||
## 🔄 功能与页面对应关系
|
||||
|
||||
根据你提供的完整需求，所有功能已全部实现：
|
||||
|
||||
| 序号 | 功能名称 | 对应页面 | 状态 |
|
||||
|------|---------|---------|------|
|
||||
| 1 | 账号管理-客户角色 | account-management/customer-role | ✅ 已创建 |
|
||||
| 2 | 账号管理-代理商管理 | account-management/agent | ✅ 已创建 |
|
||||
| 3 | 账号管理-企业客户管理 | account-management/enterprise-customer | ✅ 已创建 |
|
||||
| 4 | 账号管理-客户账号管理 | account-management/customer-account | ✅ 已创建 |
|
||||
| 5 | 账户管理-客户账号佣金 | account-management/customer-commission | ✅ 已创建 |
|
||||
| 6 | 账户管理-佣金提现 | finance/withdrawal | ✅ 已创建 |
|
||||
| 7 | 账户管理-佣金提现设置 | finance/withdrawal-settings | ✅ 已创建 |
|
||||
| 8 | 我的财务-我的账户 | finance/my-account | ✅ 已创建 |
|
||||
| 9 | 我的设置-收款商户设置 | settings/payment-merchant | ✅ 已创建 |
|
||||
| 10 | 我的设置-开发能力管理 | settings/developer-api | ✅ 已创建 |
|
||||
| 11 | 我的设置-分佣模板 | settings/commission-template | ✅ 已创建 |
|
||||
| 12 | 商品管理-号卡管理 | product/sim-card | ✅ 已创建 |
|
||||
| 13 | 商品管理-号卡分配 | product/sim-card-assign | ✅ 已创建 |
|
||||
| 14 | 商品管理-套餐系列管理 | package-management/package-series | ✅ 已存在 |
|
||||
| 15 | 商品管理-套餐管理 | package-management/package-list | ✅ 已存在 |
|
||||
| 16 | 商品管理-套餐分配 | package-management/package-assign | ✅ 已存在 |
|
||||
| 17 | 资产管理-单卡信息 | card-management/single-card | ✅ 已存在 |
|
||||
| 18 | 资产管理-网卡管理 | card-management/card-list | ✅ 已存在 |
|
||||
| 19 | 资产管理-设备管理 | device-management/devices | ✅ 已存在 |
|
||||
| 20 | 资产管理-资产分配 | asset-management/asset-assign | ✅ 已创建 |
|
||||
| 21 | 资产管理-换卡申请 | asset-management/card-replacement-request | ✅ 已创建 |
|
||||
| 22 | 批量操作-网卡导入 | batch/sim-import | ✅ 已创建 |
|
||||
| 23 | 批量操作-设备导入 | batch/device-import | ✅ 已创建 |
|
||||
| 24 | 批量操作-线下批量充值 | card-management/offline-batch-recharge | ✅ 已存在 |
|
||||
| 25 | 批量操作-换卡通知 | batch/card-change-notice | ✅ 已创建 |
|
||||
|
||||
**总计：25个功能全部实现 ✅**
|
||||
|
||||
---
|
||||
|
||||
## 🔧 配置文件更新
|
||||
|
||||
### 1. 路由别名配置
|
||||
**文件**: `src/router/routesAlias.ts`
|
||||
|
||||
新增路由别名：
|
||||
```typescript
|
||||
// 账号管理（扩展）
|
||||
EnterpriseCustomer = '/account-management/enterprise-customer'
|
||||
CustomerCommission = '/account-management/customer-commission'
|
||||
|
||||
// 产品管理（扩展）
|
||||
SimCardAssign = '/product/sim-card-assign'
|
||||
|
||||
// 资产管理（新增模块）
|
||||
AssetAssign = '/asset-management/asset-assign'
|
||||
CardReplacementRequest = '/asset-management/card-replacement-request'
|
||||
```
|
||||
|
||||
### 2. 异步路由配置
|
||||
**文件**: `src/router/routes/asyncRoutes.ts`
|
||||
|
||||
新增路由模块：
|
||||
- 账号管理模块：扩展2个子路由（企业客户、客户佣金）
|
||||
- 产品管理模块：扩展1个子路由（号卡分配）
|
||||
- 资产管理模块：新增模块，2个子路由（资产分配、换卡申请）
|
||||
|
||||
### 3. 国际化配置
|
||||
**文件**: `src/locales/langs/zh.json`
|
||||
|
||||
新增菜单标题：
|
||||
```json
|
||||
{
|
||||
"menus": {
|
||||
"accountManagement": {
|
||||
"enterpriseCustomer": "企业客户管理",
|
||||
"customerCommission": "客户账号佣金"
|
||||
},
|
||||
"product": {
|
||||
"simCardAssign": "号卡分配"
|
||||
},
|
||||
"assetManagement": {
|
||||
"title": "资产管理",
|
||||
"assetAssign": "资产分配",
|
||||
"cardReplacementRequest": "换卡申请"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📝 页面功能特性
|
||||
|
||||
### 🔑 核心功能亮点
|
||||
|
||||
#### 1. 企业客户管理（EnterpriseCustomer）
|
||||
- ✨ 企业信息完整管理（企业名称、统一社会信用代码、地址）
|
||||
- 📄 营业执照上传功能
|
||||
- 👤 联系人信息管理
|
||||
- 🔐 企业端独立登录账号（不能登录管理端）
|
||||
- 🎭 角色分配，依赖客户角色决定能力边界
|
||||
- 💰 初始余额设置
|
||||
- 📊 卡片和设备数量统计
|
||||
- ✅ 状态管理（正常/禁用/待审核）
|
||||
|
||||
#### 2. 客户账号佣金（CustomerCommission）
|
||||
- 📈 统计卡片展示（客户总数、累计佣金、已提现、待提现）
|
||||
- 🔍 多维度筛选（客户类型、佣金范围）
|
||||
- 💵 佣金明细查看（来源、订单号、佣金金额、比例）
|
||||
- 📜 提现记录追踪（提现单号、金额、手续费、状态）
|
||||
- 📊 排序功能（按佣金、提现金额排序）
|
||||
- 📤 数据导出功能
|
||||
|
||||
#### 3. 号卡分配（SimCardAssign）
|
||||
- 🎯 为代理商分配号卡产品
|
||||
- 💰 三种分佣模式：
|
||||
- 固定佣金（每张固定金额）
|
||||
- 比例佣金（按百分比）
|
||||
- 模板佣金（使用预设模板）
|
||||
- 🎁 特殊折扣设置
|
||||
- 📊 库存管理和分配数量追踪
|
||||
- 📝 分配记录查询
|
||||
- ❌ 取消分配功能（恢复库存）
|
||||
|
||||
#### 4. 资产分配（AssetAssign）
|
||||
- 🔀 三种分配模式：
|
||||
- 网卡批量分配（仅分配网卡）
|
||||
- 设备批量分配（仅分配设备）
|
||||
- 网卡+设备分配（网卡有绑定设备时同时分配）
|
||||
- ✅ 批量选择功能
|
||||
- 🎯 分配给指定代理商
|
||||
- 📝 分配说明和备注
|
||||
- 📊 分配历史记录
|
||||
- ⚠️ 资产所有权转移警告
|
||||
|
||||
#### 5. 换卡申请管理（CardReplacementRequest）
|
||||
- 📈 统计卡片（待处理、处理中、已完成、已拒绝）
|
||||
- 🔄 状态流转：待处理 → 处理中 → 已完成
|
||||
- 🆕 填充新卡ICCID功能
|
||||
- ✅ ICCID验证（长度、是否已使用）
|
||||
- ❌ 申请拒绝（需填写拒绝原因）
|
||||
- 📊 申请详情查看
|
||||
- 🔍 多条件筛选（状态、日期范围）
|
||||
|
||||
---
|
||||
|
||||
## 🎨 统一设计规范
|
||||
|
||||
### UI组件使用
|
||||
- ✅ ArtTable - 自定义表格组件
|
||||
- ✅ ElCard - 卡片容器
|
||||
- ✅ ElDialog - 对话框
|
||||
- ✅ ElForm - 表单
|
||||
- ✅ ElDescriptions - 描述列表
|
||||
- ✅ ElTag - 标签
|
||||
- ✅ ElProgress - 进度条
|
||||
- ✅ ElUpload - 文件上传
|
||||
|
||||
### 交互模式
|
||||
- ✅ 搜索 + 筛选 + 操作按钮布局
|
||||
- ✅ 列表 + 详情对话框模式
|
||||
- ✅ 确认对话框（删除、状态变更）
|
||||
- ✅ 表单验证和错误提示
|
||||
- ✅ 加载状态和进度展示
|
||||
|
||||
### 数据展示
|
||||
- ✅ 统计卡片（带图标和渐变色）
|
||||
- ✅ 状态标签（不同颜色区分）
|
||||
- ✅ 金额格式化显示
|
||||
- ✅ 时间格式化显示
|
||||
- ✅ 空状态提示
|
||||
|
||||
---
|
||||
|
||||
## 🚀 如何访问新页面
|
||||
|
||||
开发服务器运行在 `http://localhost:3006`
|
||||
|
||||
### 账号管理模块
|
||||
- `/account-management/customer-role` - 客户角色
|
||||
- `/account-management/agent` - 代理商管理
|
||||
- `/account-management/customer-account` - 客户账号管理
|
||||
- `/account-management/enterprise-customer` - 企业客户管理 ⭐ 新增
|
||||
- `/account-management/customer-commission` - 客户账号佣金 ⭐ 新增
|
||||
|
||||
### 财务管理模块
|
||||
- `/finance/withdrawal` - 提现管理
|
||||
- `/finance/my-account` - 我的账户
|
||||
- `/finance/withdrawal-settings` - 提现设置
|
||||
|
||||
### 设置管理模块
|
||||
- `/settings/payment-merchant` - 支付商户
|
||||
- `/settings/developer-api` - 开发者API
|
||||
- `/settings/commission-template` - 分佣模板
|
||||
|
||||
### 商品管理模块
|
||||
- `/product/sim-card` - 网卡产品管理
|
||||
- `/product/sim-card-assign` - 号卡分配 ⭐ 新增
|
||||
|
||||
### 资产管理模块
|
||||
- `/asset-management/asset-assign` - 资产分配 ⭐ 新增
|
||||
- `/asset-management/card-replacement-request` - 换卡申请 ⭐ 新增
|
||||
|
||||
### 批量操作模块
|
||||
- `/batch/sim-import` - 网卡批量导入
|
||||
- `/batch/device-import` - 设备批量导入
|
||||
- `/batch/card-change-notice` - 换卡通知
|
||||
|
||||
---
|
||||
|
||||
## 📊 开发统计
|
||||
|
||||
### 代码规模
|
||||
- **Vue组件**: 18个
|
||||
- **总代码行数**: 约 6000+ 行
|
||||
- **TypeScript接口**: 50+ 个
|
||||
- **Mock数据**: 完整覆盖
|
||||
|
||||
### 开发时间
|
||||
- **第一批页面**: 13个（约2小时）
|
||||
- **第二批页面**: 5个（约1小时）
|
||||
- **配置更新**: 路由+国际化（约30分钟）
|
||||
- **总计**: 约3.5小时
|
||||
|
||||
### 功能覆盖率
|
||||
- ✅ CRUD操作: 100%
|
||||
- ✅ 搜索筛选: 100%
|
||||
- ✅ 状态管理: 100%
|
||||
- ✅ 表单验证: 100%
|
||||
- ✅ 数据统计: 100%
|
||||
|
||||
---
|
||||
|
||||
## 🎯 下一步工作建议
|
||||
|
||||
### 1. API 对接 🔌
|
||||
- [ ] 将所有 Mock 数据替换为真实 API 调用
|
||||
- [ ] 统一错误处理和提示
|
||||
- [ ] 添加请求拦截器和响应拦截器
|
||||
- [ ] 实现 Token 刷新机制
|
||||
- [ ] 处理接口超时和重试
|
||||
|
||||
### 2. 权限控制 🔐
|
||||
- [ ] 按钮级权限控制（v-permission 指令）
|
||||
- [ ] 数据权限过滤（根据用户角色）
|
||||
- [ ] 路由权限守卫（动态路由注册）
|
||||
- [ ] 操作日志记录
|
||||
|
||||
### 3. 数据验证 ✅
|
||||
- [ ] 完善表单验证规则
|
||||
- [ ] 后端数据校验
|
||||
- [ ] 异常数据处理
|
||||
- [ ] 防重复提交
|
||||
|
||||
### 4. 性能优化 ⚡
|
||||
- [ ] 列表虚拟滚动（大数据量）
|
||||
- [ ] 组件懒加载
|
||||
- [ ] 图片懒加载
|
||||
- [ ] 防抖节流
|
||||
- [ ] 缓存策略
|
||||
|
||||
### 5. 用户体验 ✨
|
||||
- [ ] 骨架屏loading
|
||||
- [ ] 空状态优化
|
||||
- [ ] 错误页面优化
|
||||
- [ ] 操作引导（新手引导）
|
||||
- [ ] 快捷键支持
|
||||
|
||||
### 6. 测试 🧪
|
||||
- [ ] 单元测试（Vitest）
|
||||
- [ ] 集成测试
|
||||
- [ ] E2E 测试（Playwright）
|
||||
- [ ] 性能测试
|
||||
- [ ] 兼容性测试
|
||||
|
||||
---
|
||||
|
||||
## 📚 相关文档
|
||||
|
||||
- [任务规划文档](./任务规划.md)
|
||||
- [页面创建模板](./页面创建模板.md)
|
||||
- [API对接说明](./API对接说明.md)
|
||||
- [功能需求文档](./功能.md)
|
||||
|
||||
---
|
||||
|
||||
## ✨ 项目亮点
|
||||
|
||||
### 1. 完整性 ✅
|
||||
- 25个功能需求全部实现
|
||||
- 页面布局统一美观
|
||||
- 交互流程完整合理
|
||||
|
||||
### 2. 规范性 📐
|
||||
- 代码风格统一
|
||||
- TypeScript 类型完整
|
||||
- 组件复用率高
|
||||
- 命名规范清晰
|
||||
|
||||
### 3. 可维护性 🔧
|
||||
- 模块化清晰
|
||||
- Mock数据结构完整
|
||||
- 注释清晰
|
||||
- 易于扩展
|
||||
|
||||
### 4. 用户体验 🎨
|
||||
- 界面美观大方
|
||||
- 操作流程顺畅
|
||||
- 反馈及时明确
|
||||
- 状态提示清晰
|
||||
|
||||
---
|
||||
|
||||
## 🎉 总结
|
||||
|
||||
本次开发共完成 **18 个新页面组件**，配合项目中已有的页面，完整实现了物联网卡管理系统的全部 **25 个功能模块**。
|
||||
|
||||
**开发完成度**: 100% ✅
|
||||
**代码质量**: 优秀 ⭐⭐⭐⭐⭐
|
||||
**可维护性**: 优秀 👍
|
||||
**用户体验**: 优秀 🎨
|
||||
|
||||
所有页面均遵循统一的代码规范，使用 Mock 数据进行开发，界面美观、交互流畅，为后续 API 对接和功能扩展打下了坚实基础。
|
||||
|
||||
项目已经具备完整的功能框架，可以直接对接后端API进行真实数据调试。恭喜项目顺利完成！🎊
|
||||
@@ -5,6 +5,7 @@
|
||||
当前后台“资产信息”页还没有消费接口新增的 `gateway_extend` 字段，因此运营人员无法在资产详情中直接看到运营商侧实际停机原因。
|
||||
|
||||
最新接口契约已经补充两类返回：
|
||||
|
||||
- 设备资产的绑定卡列表项新增 `gateway_extend`
|
||||
- 卡资产详情新增 `gateway_extend`
|
||||
|
||||
|
||||
@@ -0,0 +1,28 @@
|
||||
## Context
|
||||
|
||||
The feature exposes high-impact package usage adjustments from the asset information package list. Because it can change real package consumption and expiration, the UI gate must combine deployment environment, account type, and production button permissions.
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: Add two package-list operations, call the documented PATCH APIs, validate operator input, and refresh page data after success.
|
||||
- Goals: Keep production access limited to platform users (`user_type=2`) with explicit button permissions.
|
||||
- Goals: Keep test/development access limited to super admins (`user_type=1`) without requiring button permissions.
|
||||
- Non-Goals: Add backend endpoints, change package list data retrieval, or change existing refund/package display behavior.
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: Treat non-production as `import.meta.env.DEV` or a project-defined test mode discovered during implementation; production behavior MUST be used for production builds.
|
||||
- Decision: Use separate permission codes for the two production-only buttons so operators can be granted one action without the other.
|
||||
- Decision: Prefer small modal forms from the package list component unless an existing asset-operation dialog pattern provides a clearer reuse point.
|
||||
- Decision: Send `data_usage_mb` as a non-negative integer MB value and `expires_at` as the selected formatted datetime string.
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- Permission code names are not specified in the request. Implementation MUST confirm or define final codes before wiring production checks.
|
||||
- Environment naming can vary by deployment. Implementation MUST inspect existing env conventions and avoid making test-only access available in production mode.
|
||||
- Adjusting real used data can make displayed virtual/remaining values stale if the list is not refreshed. The UI MUST refresh after success.
|
||||
|
||||
## Open Questions
|
||||
|
||||
- What are the final production permission codes for “修改已用量” and “修改过期时间”?
|
||||
- Which env flag identifies the requested “测试环境” if it is not `import.meta.env.DEV`?
|
||||
@@ -0,0 +1,33 @@
|
||||
# Change: Add asset package admin adjustment actions
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页的套餐列表目前只能查看套餐使用记录，缺少运营侧直接修正套餐真实已用量和过期时间的入口。后端已提供对应 PATCH 接口，前端需要补齐受环境、账号类型和按钮权限约束的操作能力。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在资产信息页“套餐列表”的“操作”列新增两个操作：
|
||||
- 修改已用量
|
||||
- 修改过期时间
|
||||
- 新增两个 PATCH 接口的前端契约：
|
||||
- `PATCH /api/admin/assets/{identifier}/packages/{package_usage_id}/used-data`
|
||||
- `PATCH /api/admin/assets/{identifier}/packages/{package_usage_id}/expires-at`
|
||||
- 两个操作按钮使用环境差异化可见性规则：
|
||||
- 线上环境：仅 `user_type=2` 且拥有对应按钮权限时显示
|
||||
- 测试/开发环境：仅 `user_type=1` 显示，不要求按钮权限
|
||||
- 为两个操作提供弹窗表单、输入校验、提交 loading、成功提示和刷新套餐列表行为。
|
||||
- 不改变套餐列表既有字段展示、退款入口或现有套餐流量展示口径。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-package-admin-adjustments`
|
||||
- Affected code:
|
||||
- `src/api/modules/asset.ts`
|
||||
- `src/types/api/asset.ts`
|
||||
- `src/views/asset-management/asset-information/components/PackageListCard.vue`
|
||||
- Potential dialog component(s) under `src/views/asset-management/asset-information/components/dialogs/`
|
||||
- Dependencies:
|
||||
- Current asset identifier from asset information page context
|
||||
- Current logged-in account `user_type`
|
||||
- Button permissions for production visibility
|
||||
@@ -0,0 +1,134 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Package List Adjustment Actions
|
||||
|
||||
The asset information package list SHALL provide operator actions to update a package usage record's real used data and expiration time.
|
||||
|
||||
#### Scenario: Render adjustment actions in the package list
|
||||
|
||||
- **GIVEN** 用户正在查看资产信息页的“套餐列表”
|
||||
- **AND** 当前登录账号满足对应操作的可见性规则
|
||||
- **WHEN** 页面渲染套餐列表操作列
|
||||
- **THEN** 系统 MUST 显示“修改已用量”操作
|
||||
- **AND** 系统 MUST 显示“修改过期时间”操作
|
||||
|
||||
#### Scenario: Open used-data adjustment form
|
||||
|
||||
- **GIVEN** 用户可见“修改已用量”操作
|
||||
- **WHEN** 用户点击某条套餐记录的“修改已用量”
|
||||
- **THEN** 系统 MUST 打开修改已用量弹窗
|
||||
- **AND** 弹窗 MUST 展示当前套餐记录上下文
|
||||
- **AND** 表单 MUST 要求输入新的套餐真实已用量 MB
|
||||
|
||||
#### Scenario: Open expiration adjustment form
|
||||
|
||||
- **GIVEN** 用户可见“修改过期时间”操作
|
||||
- **WHEN** 用户点击某条套餐记录的“修改过期时间”
|
||||
- **THEN** 系统 MUST 打开修改过期时间弹窗
|
||||
- **AND** 弹窗 MUST 展示当前套餐记录上下文
|
||||
- **AND** 表单 MUST 要求输入新的套餐过期时间
|
||||
|
||||
### Requirement: Used Data Update API Integration
|
||||
|
||||
The frontend SHALL update a package usage record's real used data through `PATCH /api/admin/assets/{identifier}/packages/{package_usage_id}/used-data`.
|
||||
|
||||
#### Scenario: Submit valid used-data update
|
||||
|
||||
- **GIVEN** 用户正在修改某条套餐记录的已用量
|
||||
- **AND** 当前资产标识符为 `identifier`
|
||||
- **AND** 当前套餐使用记录 ID 为 `package_usage_id`
|
||||
- **WHEN** 用户输入非负整数 `data_usage_mb` 并提交
|
||||
- **THEN** 系统 MUST send `PATCH /api/admin/assets/{identifier}/packages/{package_usage_id}/used-data`
|
||||
- **AND** 请求体 MUST be JSON with `data_usage_mb`
|
||||
- **AND** `data_usage_mb` MUST be a non-negative integer MB value
|
||||
|
||||
#### Scenario: Reject invalid used-data input
|
||||
|
||||
- **GIVEN** 用户正在修改套餐已用量
|
||||
- **WHEN** 用户未输入值、输入负数或输入非整数
|
||||
- **THEN** 系统 MUST block submission
|
||||
- **AND** 系统 MUST show a validation message explaining that the used data must be a non-negative integer MB value
|
||||
- **AND** 系统 MUST NOT call the PATCH endpoint
|
||||
|
||||
#### Scenario: Used-data update succeeds
|
||||
|
||||
- **GIVEN** used-data PATCH request returns `code=0`
|
||||
- **WHEN** 系统收到响应
|
||||
- **THEN** 系统 MUST show a success message
|
||||
- **AND** 系统 MUST close the edit dialog
|
||||
- **AND** 系统 MUST refresh the asset package list so the latest package usage data is displayed
|
||||
|
||||
### Requirement: Expiration Time Update API Integration
|
||||
|
||||
The frontend SHALL update a package usage record's expiration time through `PATCH /api/admin/assets/{identifier}/packages/{package_usage_id}/expires-at`.
|
||||
|
||||
#### Scenario: Submit valid expiration update
|
||||
|
||||
- **GIVEN** 用户正在修改某条套餐记录的过期时间
|
||||
- **AND** 当前资产标识符为 `identifier`
|
||||
- **AND** 当前套餐使用记录 ID 为 `package_usage_id`
|
||||
- **WHEN** 用户输入有效的 `expires_at` 并提交
|
||||
- **THEN** 系统 MUST send `PATCH /api/admin/assets/{identifier}/packages/{package_usage_id}/expires-at`
|
||||
- **AND** 请求体 MUST be JSON with `expires_at`
|
||||
- **AND** `expires_at` MUST be formatted as `YYYY-MM-DD HH:MM:SS` or another backend-accepted RFC3339 string
|
||||
|
||||
#### Scenario: Reject missing expiration input
|
||||
|
||||
- **GIVEN** 用户正在修改套餐过期时间
|
||||
- **WHEN** 用户未选择或未输入过期时间
|
||||
- **THEN** 系统 MUST block submission
|
||||
- **AND** 系统 MUST show a validation message explaining that expiration time is required
|
||||
- **AND** 系统 MUST NOT call the PATCH endpoint
|
||||
|
||||
#### Scenario: Expiration update succeeds
|
||||
|
||||
- **GIVEN** expires-at PATCH request returns `code=0`
|
||||
- **WHEN** 系统收到响应
|
||||
- **THEN** 系统 MUST show a success message
|
||||
- **AND** 系统 MUST close the edit dialog
|
||||
- **AND** 系统 MUST refresh the asset package list so the latest expiration time is displayed
|
||||
|
||||
### Requirement: Environment And Account Visibility Gate
|
||||
|
||||
The frontend SHALL gate both package adjustment actions by environment, current account `user_type`, and production button permissions.
|
||||
|
||||
#### Scenario: Production platform user with permission sees matching action
|
||||
|
||||
- **GIVEN** 当前运行环境为线上环境
|
||||
- **AND** 当前登录账号的 `user_type` 为 `2`
|
||||
- **AND** 当前登录账号拥有“修改已用量”的按钮权限
|
||||
- **WHEN** 页面渲染套餐列表操作列
|
||||
- **THEN** 系统 MUST show “修改已用量”
|
||||
|
||||
#### Scenario: Production platform user without permission cannot see matching action
|
||||
|
||||
- **GIVEN** 当前运行环境为线上环境
|
||||
- **AND** 当前登录账号的 `user_type` 为 `2`
|
||||
- **AND** 当前登录账号缺少“修改过期时间”的按钮权限
|
||||
- **WHEN** 页面渲染套餐列表操作列
|
||||
- **THEN** 系统 MUST NOT show “修改过期时间”
|
||||
|
||||
#### Scenario: Production super admin cannot see adjustment actions
|
||||
|
||||
- **GIVEN** 当前运行环境为线上环境
|
||||
- **AND** 当前登录账号的 `user_type` 为 `1`
|
||||
- **WHEN** 页面渲染套餐列表操作列
|
||||
- **THEN** 系统 MUST NOT show “修改已用量”
|
||||
- **AND** 系统 MUST NOT show “修改过期时间”
|
||||
|
||||
#### Scenario: Test environment super admin sees actions without permissions
|
||||
|
||||
- **GIVEN** 当前运行环境为测试或开发环境
|
||||
- **AND** 当前登录账号的 `user_type` 为 `1`
|
||||
- **AND** 当前登录账号没有两个调整操作的按钮权限
|
||||
- **WHEN** 页面渲染套餐列表操作列
|
||||
- **THEN** 系统 MUST show “修改已用量”
|
||||
- **AND** 系统 MUST show “修改过期时间”
|
||||
|
||||
#### Scenario: Test environment non-super-admin cannot see actions
|
||||
|
||||
- **GIVEN** 当前运行环境为测试或开发环境
|
||||
- **AND** 当前登录账号的 `user_type` is not `1`
|
||||
- **WHEN** 页面渲染套餐列表操作列
|
||||
- **THEN** 系统 MUST NOT show “修改已用量”
|
||||
- **AND** 系统 MUST NOT show “修改过期时间”
|
||||
@@ -0,0 +1,21 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 Add API request/response types for package used-data and expires-at updates.
|
||||
- [x] 1.2 Add AssetService PATCH methods for `/assets/{identifier}/packages/{package_usage_id}/used-data` and `/assets/{identifier}/packages/{package_usage_id}/expires-at`.
|
||||
- [x] 1.3 Pass the current asset identifier to the package list component if it is not already available there.
|
||||
- [x] 1.4 Add operation buttons to the package list with environment, `user_type`, and permission visibility rules.
|
||||
- [x] 1.5 Add edit-used-data dialog/form with non-negative integer MB validation and submit handling.
|
||||
- [x] 1.6 Add edit-expires-at dialog/form with required datetime validation and submit handling.
|
||||
- [x] 1.7 Refresh package list data and show success feedback after each successful update.
|
||||
- [x] 1.8 Run targeted lint/type checks for changed files and document any unrelated existing failures.
|
||||
|
||||
## 2. Permission Setup
|
||||
|
||||
- [x] 2.1 Confirm final production permission codes for “修改已用量” and “修改过期时间”.
|
||||
- [x] 2.2 Wire the confirmed permission codes into button visibility checks.
|
||||
|
||||
## 3. Validation
|
||||
|
||||
- [x] 3.1 Verify production-mode behavior: `user_type=2` requires the matching permission for each button.
|
||||
- [x] 3.2 Verify test/development-mode behavior: only `user_type=1` sees the buttons and permissions are ignored.
|
||||
- [x] 3.3 Verify unauthorized account types do not see either operation.
|
||||
@@ -0,0 +1,20 @@
|
||||
# Change: 新增资产业务状态和世代编号字段
|
||||
|
||||
## Why
|
||||
|
||||
后端已在 IoT 卡和设备的资产详情接口中新增 `asset_status`（业务状态）和 `generation`（资产世代编号）字段，前端需要展示这些字段供运营人员查看。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 资产信息详情新增 `asset_status` 和 `asset_status_name` 字段，展示业务状态（1:在库, 2:已销售, 3:已换货, 4:已停用）
|
||||
- 资产信息详情新增 `generation` 字段，展示资产世代编号（初始值1，每次换货转新后+1）
|
||||
- 相关格式化函数更新以支持新字段
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-information`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/types.ts` - AssetInfo 接口
|
||||
- `src/views/asset-management/asset-information/components/BasicInfoCard.vue` - 详情展示
|
||||
- `src/views/asset-management/asset-information/composables/useAssetFormatters.ts` - 格式化函数
|
||||
@@ -0,0 +1,34 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Asset Status and Generation Display
|
||||
|
||||
The admin frontend SHALL display `asset_status`, `asset_status_name`, and `generation` fields in the asset information detail page for both IoT cards and devices.
|
||||
|
||||
#### Scenario: Display IoT card asset status and generation
|
||||
|
||||
- **GIVEN** 用户打开 IoT 卡资产信息详情页
|
||||
- **WHEN** 后端返回 `asset_status`、`asset_status_name` 和 `generation` 字段
|
||||
- **THEN** 页面 MUST display the asset status with appropriate tag type
|
||||
- **AND** 页面 MUST display the generation number
|
||||
|
||||
#### Scenario: Display device asset status and generation
|
||||
|
||||
- **GIVEN** 用户打开设备资产信息详情页
|
||||
- **WHEN** 后端返回 `asset_status`、`asset_status_name` 和 `generation` 字段
|
||||
- **THEN** 页面 MUST display the asset status with appropriate tag type
|
||||
- **AND** 页面 MUST display the generation number
|
||||
|
||||
### Requirement: Asset Status Formatting
|
||||
|
||||
The admin frontend SHALL format asset status values with appropriate labels and tag types.
|
||||
|
||||
#### Scenario: Map asset status to display name
|
||||
|
||||
- **GIVEN** `asset_status` value is 1
|
||||
- **THEN** display name MUST be "在库"
|
||||
- **WHEN** `asset_status` value is 2
|
||||
- **THEN** display name MUST be "已销售"
|
||||
- **WHEN** `asset_status` value is 3
|
||||
- **THEN** display name MUST be "已换货"
|
||||
- **WHEN** `asset_status` value is 4
|
||||
- **THEN** display name MUST be "已停用"
|
||||
@@ -0,0 +1,28 @@
|
||||
## 1. Proposal Review
|
||||
|
||||
- [ ] 1.1 确认 `asset_status` 字段含义：1:在库, 2:已销售, 3:已换货, 4:已停用
|
||||
- [ ] 1.2 确认 `generation` 字段含义：资产世代编号，初始值1，每次换货转新后+1
|
||||
|
||||
## 2. Type Updates
|
||||
|
||||
- [ ] 2.1 在 `AssetInfo` 接口中添加 `asset_status?: number`
|
||||
- [ ] 2.2 在 `AssetInfo` 接口中添加 `asset_status_name?: string`
|
||||
- [ ] 2.3 在 `AssetInfo` 接口中添加 `generation?: number`
|
||||
|
||||
## 3. Formatter Functions
|
||||
|
||||
- [ ] 3.1 在 `useAssetFormatters` 中添加 `getAssetStatusName` 函数（如果不存在）
|
||||
- [ ] 3.2 在 `useAssetFormatters` 中添加 `getAssetStatusType` 函数（如果不存在）
|
||||
|
||||
## 4. BasicInfoCard Component
|
||||
|
||||
- [ ] 4.1 在卡信息区域添加「业务状态」展示行
|
||||
- [ ] 4.2 在卡信息区域添加「资产世代」展示行
|
||||
- [ ] 4.3 在设备信息区域添加「业务状态」展示行
|
||||
- [ ] 4.4 在设备信息区域添加「资产世代」展示行
|
||||
|
||||
## 5. Verification
|
||||
|
||||
- [ ] 5.1 验证 IoT 卡详情页正确显示业务状态和世代编号
|
||||
- [ ] 5.2 验证设备详情页正确显示业务状态和世代编号
|
||||
- [ ] 5.3 验证格式化函数正确处理各状态值
|
||||
73
openspec/changes/add-export-task-management/design.md
Normal file
73
openspec/changes/add-export-task-management/design.md
Normal file
@@ -0,0 +1,73 @@
|
||||
## Context
|
||||
|
||||
`docs/api.md` 定义了统一导出任务接口，支持 `device` 和 `iot_card` 两个场景，导出格式支持 `xlsx` / `csv`。前端需要提供两个业务列表的导出入口，以及一个可复用的导出任务管理视角，用于查看任务进度、查看详情、下载结果和取消任务。
|
||||
|
||||
现有项目使用 Vue 3 + TypeScript + Element Plus，API 按业务模块放在 `src/api/modules`，类型放在 `src/types/api`，按钮权限通过 `useAuth` 和 `v-permission` 接入。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: 提供统一导出任务 API 封装、可复用创建弹窗、资产管理下导出列表页面、IoT 卡和设备列表导出入口、按钮权限控制。
|
||||
- Goals: 创建导出任务时传入当前列表检索条件快照，避免用户修改筛选条件后影响已经提交的任务。
|
||||
- Non-Goals: 不实现后端导出任务调度、文件生成、对象存储上传或 JWT 鉴权逻辑。
|
||||
- Non-Goals: 不替换现有导入任务页面，也不将导出任务与导入任务合并成同一个页面。
|
||||
- Non-Goals: 不在前端根据 `file_key` 拼接下载地址，下载必须使用详情接口返回的 `download_url`。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 新增独立能力 `export-task-management`，不复用导入任务能力命名。
|
||||
- Rationale: 导出任务接口、状态流转、下载逻辑和业务入口与导入任务不同，独立能力更容易扩展到更多导出场景。
|
||||
|
||||
- Decision: 创建导出任务弹窗做成业务无关组件，只通过 props 接收 `scene`、`query`、`format`、标题和说明文案。
|
||||
- Rationale: IoT 卡管理和设备管理只需传入不同场景与当前筛选条件，后续其他业务列表可以复用同一组件。
|
||||
|
||||
- Decision: 导出列表页面做成可按 `scene` 筛选的管理视角，而不是为 `device` 和 `iot_card` 各建一套页面。
|
||||
- Rationale: `GET /api/admin/export-tasks` 已提供 `scene` 过滤，统一列表能减少重复代码，也支持未来新增默认场景视角。
|
||||
|
||||
- Decision: 下载操作先调用 `GET /api/admin/export-tasks/{id}`，再使用详情中的 `download_url`。
|
||||
- Rationale: 文档说明下载地址仅在已完成任务详情中返回且有效期 24 小时，列表中的 `file_key` 不应被前端直接用于下载。
|
||||
|
||||
- Decision: 权限编码按业务入口隔离。
|
||||
- Rationale: 创建任务属于来源业务列表权限，导出任务列表中的详情、下载、取消属于导出任务管理权限，避免用户拥有某个列表导出权限后自动获得管理全部导出任务的权限。
|
||||
|
||||
## Data Model
|
||||
|
||||
- `scene`: `device` / `iot_card`。
|
||||
- `format`: `xlsx` / `csv`。
|
||||
- `status`: `1` 待处理、`2` 处理中、`3` 已完成、`4` 失败、`5` 已取消。
|
||||
- `query`: 任意对象，保存发起导出时的业务列表筛选条件快照。
|
||||
|
||||
## Permission Codes
|
||||
|
||||
- `iot_card:export`: IoT 卡管理页导出按钮。
|
||||
- `devices:export`: 设备管理页导出按钮。
|
||||
- `export_task:list`: 导出列表页面访问和查询入口。
|
||||
- `export_task:detail`: 导出列表行详情操作。
|
||||
- `export_task:download`: 导出列表行下载操作。
|
||||
- `export_task:cancel`: 导出列表行取消操作。
|
||||
|
||||
最终权限编码以产品/后端权限配置为准；如需调整，应在实施前同步更新本提案与任务。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- Risk: 业务列表筛选字段与后端导出任务 `query` 支持字段不一致。
|
||||
- Mitigation: 复用列表请求参数构造逻辑，并在提测时分别验证 `iot_card` 和 `device` 场景。
|
||||
|
||||
- Risk: 下载地址有效期为 24 小时，用户在旧页面点击下载时可能失效。
|
||||
- Mitigation: 每次下载前重新调用详情接口获取最新可用的 `download_url`。
|
||||
|
||||
- Risk: 取消处理中任务时后端可能只是标记 `cancel_requested`，不是立即变成已取消。
|
||||
- Mitigation: 取消成功后刷新列表并展示后端返回的状态和提示信息。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 增加 API、类型、路由、菜单和组件。
|
||||
2. 在 IoT 卡管理和设备管理接入导出弹窗。
|
||||
3. 新增导出列表页面并接入详情、下载、取消操作。
|
||||
4. 接入权限编码并验证不同权限组合。
|
||||
5. 如后端权限菜单需要同步，按上述权限编码补齐配置。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 导出格式是否需要在第一版开放给用户选择，还是固定 `xlsx`。
|
||||
- 权限编码是否采用本设计建议，还是需对齐后端已有权限命名。
|
||||
- 导出列表是否需要默认按当前入口过滤场景，还是资产管理下统一列表默认展示全部场景。
|
||||
44
openspec/changes/add-export-task-management/proposal.md
Normal file
44
openspec/changes/add-export-task-management/proposal.md
Normal file
@@ -0,0 +1,44 @@
|
||||
# Change: 新增统一导出任务管理
|
||||
|
||||
## Why
|
||||
|
||||
资产管理中的 IoT 卡与设备列表需要按当前检索条件执行全量导出，直接在前端同步导出容易超时且无法追踪进度。`docs/api.md` 已定义统一导出任务接口，需要在后台管理端补齐创建导出任务、查看任务列表、查看详情、下载结果和取消任务的前端能力。
|
||||
|
||||
同时，导出入口会覆盖多个业务列表和后续可扩展的导出视角，必须做成可复用的弹窗与任务管理能力，并按现有 RBAC 体系为所有按钮和操作补充权限编码。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在资产管理下新增“导出管理”，并在其下新增“导出列表”页面。
|
||||
- 新增统一导出任务前端 API 与类型契约，对接：
|
||||
- `GET /api/admin/export-tasks`
|
||||
- `POST /api/admin/export-tasks`
|
||||
- `GET /api/admin/export-tasks/{id}`
|
||||
- `POST /api/admin/export-tasks/{id}/cancel`
|
||||
- 新增可复用的创建导出任务弹窗，打开时说明“导出规则基于列表中的检索条件全量导出”。
|
||||
- 在 IoT 卡管理页增加导出按钮，默认创建 `scene=iot_card` 的导出任务。
|
||||
- 在设备管理页增加导出按钮，默认创建 `scene=device` 的导出任务。
|
||||
- 导出列表支持分页、场景、状态、创建时间范围筛选，列表数据调用导出任务列表接口，详情/下载调用详情接口，取消操作调用取消接口。
|
||||
- 所有新增按钮和行操作均需要接入权限编码，不允许无权限用户看到或触发对应操作。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `export-task-management`
|
||||
- Affected code:
|
||||
- `src/api/modules/exportTask.ts`
|
||||
- `src/types/api/exportTask.ts`
|
||||
- `src/types/api/index.ts`
|
||||
- `src/api/modules/index.ts`
|
||||
- `src/router/routesAlias.ts`
|
||||
- `src/router/routes/asyncRoutes.ts`
|
||||
- `src/views/asset-management/iot-card-management/index.vue`
|
||||
- `src/views/asset-management/device-list/index.vue`
|
||||
- `src/views/asset-management/export-task-management/export-task-list/index.vue`
|
||||
- `src/components/business/ExportTaskCreateDialog.vue`
|
||||
- 菜单与国际化文案配置文件
|
||||
- Dependencies:
|
||||
- 依赖后端按 `docs/api.md` 提供导出任务接口和 JWT 鉴权。
|
||||
- 依赖现有 `useAuth` / `v-permission` 权限基础设施。
|
||||
- 导出创建时传入的 `query` 需要与对应业务列表接口的检索参数保持一致。
|
||||
- Breaking changes:
|
||||
- 无。新增页面、按钮、API 模块和类型均为增量能力。
|
||||
@@ -0,0 +1,146 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Export Task API Integration
|
||||
|
||||
The admin frontend SHALL provide a typed API integration for unified export tasks using the REST contract from `docs/api.md`.
|
||||
|
||||
#### Scenario: Query export tasks with filters
|
||||
|
||||
- **GIVEN** 用户打开导出列表页面
|
||||
- **WHEN** 用户按分页、场景、状态或创建时间范围查询导出任务
|
||||
- **THEN** 系统 MUST call `GET /api/admin/export-tasks`
|
||||
- **AND** 系统 MUST support optional query parameters `page`, `page_size`, `scene`, `status`, `start_time`, and `end_time`
|
||||
- **AND** 系统 MUST parse `data.page`, `data.size`, `data.total`, and `data.items` from the response
|
||||
|
||||
#### Scenario: Create export task
|
||||
|
||||
- **GIVEN** 用户在业务列表中确认创建导出任务
|
||||
- **WHEN** 系统提交导出任务
|
||||
- **THEN** 系统 MUST call `POST /api/admin/export-tasks`
|
||||
- **AND** 请求体 MUST include required `scene` and `format`
|
||||
- **AND** 请求体 MAY include `query` containing the current list filter conditions
|
||||
- **AND** 系统 MUST handle the response fields `task_id`, `task_no`, `status`, `status_name`, and `message`
|
||||
|
||||
#### Scenario: Fetch export task detail
|
||||
|
||||
- **GIVEN** 用户需要查看或下载某个导出任务
|
||||
- **WHEN** 系统读取任务详情
|
||||
- **THEN** 系统 MUST call `GET /api/admin/export-tasks/{id}` with the numeric task id
|
||||
- **AND** 系统 MUST support detail fields including progress, row counts, shard counts, `file_key`, `error_message`, timestamps, `download_url`, and `download_expires_at`
|
||||
- **AND** 系统 MUST treat `download_url` as available only when the task is completed and the backend returns it
|
||||
|
||||
#### Scenario: Cancel export task
|
||||
|
||||
- **GIVEN** 用户取消待处理或处理中的导出任务
|
||||
- **WHEN** 系统提交取消请求
|
||||
- **THEN** 系统 MUST call `POST /api/admin/export-tasks/{id}/cancel`
|
||||
- **AND** 系统 MUST handle `task_id`, `status`, `status_name`, `cancel_requested`, and `message` from the response
|
||||
|
||||
### Requirement: Reusable Export Task Creation Dialog
|
||||
|
||||
The admin frontend SHALL provide a reusable dialog for creating export tasks from business list pages.
|
||||
|
||||
#### Scenario: Explain full export rule before task creation
|
||||
|
||||
- **GIVEN** 用户点击业务列表中的导出按钮
|
||||
- **WHEN** 导出弹窗打开
|
||||
- **THEN** 弹窗 MUST clearly state that export rules are based on the current list search conditions and export the full matched result set
|
||||
- **AND** 弹窗 MUST NOT imply that only the current page rows will be exported
|
||||
|
||||
#### Scenario: Create IoT card export task from IoT card management
|
||||
|
||||
- **GIVEN** 用户在 IoT 卡管理页设置了列表检索条件
|
||||
- **AND** 当前用户具备 IoT 卡导出权限
|
||||
- **WHEN** 用户确认创建导出任务
|
||||
- **THEN** 系统 MUST submit `scene="iot_card"`
|
||||
- **AND** 系统 MUST submit the current IoT card list filter conditions as `query`
|
||||
|
||||
#### Scenario: Create device export task from device management
|
||||
|
||||
- **GIVEN** 用户在设备管理页设置了列表检索条件
|
||||
- **AND** 当前用户具备设备导出权限
|
||||
- **WHEN** 用户确认创建导出任务
|
||||
- **THEN** 系统 MUST submit `scene="device"`
|
||||
- **AND** 系统 MUST submit the current device list filter conditions as `query`
|
||||
|
||||
#### Scenario: Snapshot current filters at submission time
|
||||
|
||||
- **GIVEN** 用户修改业务列表筛选条件并重新搜索
|
||||
- **WHEN** 用户随后打开弹窗并确认导出
|
||||
- **THEN** 系统 MUST use the latest applied search conditions in the export task `query`
|
||||
- **AND** 已提交任务的 `query` MUST NOT change when the user later edits the page filters
|
||||
|
||||
### Requirement: Asset Export Task List Page
|
||||
|
||||
The admin frontend SHALL add an export task list under Asset Management > Export Management for viewing and operating export tasks.
|
||||
|
||||
#### Scenario: Render export management navigation
|
||||
|
||||
- **GIVEN** 当前用户具备导出任务列表访问权限
|
||||
- **WHEN** 系统渲染资产管理菜单
|
||||
- **THEN** 系统 MUST provide an Export Management group under Asset Management
|
||||
- **AND** 系统 MUST provide an Export List entry under that group
|
||||
- **AND** 导出列表路由 MUST load the export task list page
|
||||
|
||||
#### Scenario: Display export task rows
|
||||
|
||||
- **GIVEN** 导出任务列表接口返回任务记录
|
||||
- **WHEN** 页面渲染表格
|
||||
- **THEN** 页面 MUST display task number, scene, status name, progress, format, total rows, processed rows, shard counts, file key, error message, and task timestamps when present
|
||||
- **AND** 页面 MUST use stable empty placeholders for missing optional fields
|
||||
|
||||
#### Scenario: View task detail from row action
|
||||
|
||||
- **GIVEN** 用户具备导出任务详情权限
|
||||
- **WHEN** 用户点击某条任务的详情操作
|
||||
- **THEN** 系统 MUST call the task detail API for that row
|
||||
- **AND** 页面 MUST present the returned task detail without losing the current list filters and pagination state
|
||||
|
||||
#### Scenario: Download completed task from row action
|
||||
|
||||
- **GIVEN** 某条导出任务状态为已完成
|
||||
- **AND** 当前用户具备导出任务下载权限
|
||||
- **WHEN** 用户点击下载操作
|
||||
- **THEN** 系统 MUST call the task detail API to obtain `download_url`
|
||||
- **AND** 系统 MUST open or download the file using the returned `download_url`
|
||||
- **AND** 系统 MUST NOT construct a download URL from `file_key` on the frontend
|
||||
|
||||
#### Scenario: Cancel cancellable task from row action
|
||||
|
||||
- **GIVEN** 某条导出任务状态为待处理或处理中
|
||||
- **AND** 当前用户具备导出任务取消权限
|
||||
- **WHEN** 用户确认取消该任务
|
||||
- **THEN** 系统 MUST call the cancel API for that task
|
||||
- **AND** 系统 MUST refresh the list or update the row using the backend response
|
||||
|
||||
#### Scenario: Hide unavailable row actions
|
||||
|
||||
- **GIVEN** 某条导出任务状态为已完成、失败或已取消
|
||||
- **WHEN** 页面渲染该行操作
|
||||
- **THEN** 页面 MUST NOT show the cancel action for that row
|
||||
- **AND** 页面 MUST show the download action only when the task is completed and the user has download permission
|
||||
|
||||
### Requirement: Export Task Permissions
|
||||
|
||||
The admin frontend MUST gate every export-task-related button and row action with explicit permission codes.
|
||||
|
||||
#### Scenario: Hide business export buttons without permission
|
||||
|
||||
- **GIVEN** 当前用户 lacks the IoT card export permission
|
||||
- **WHEN** 用户打开 IoT 卡管理页
|
||||
- **THEN** 页面 MUST NOT display the IoT card export button
|
||||
- **AND** 缺少设备导出权限时，设备管理页 MUST NOT display the device export button
|
||||
|
||||
#### Scenario: Hide export task management operations without permission
|
||||
|
||||
- **GIVEN** 当前用户可以访问导出列表但 lacks download or cancel permissions
|
||||
- **WHEN** 页面渲染导出任务行操作
|
||||
- **THEN** 页面 MUST NOT display the download action without download permission
|
||||
- **AND** 页面 MUST NOT display the cancel action without cancel permission
|
||||
|
||||
#### Scenario: Keep permissions isolated by entry point
|
||||
|
||||
- **GIVEN** 当前用户具备 `iot_card` 导出权限但不具备 `device` 导出权限
|
||||
- **WHEN** 用户分别访问 IoT 卡管理页和设备管理页
|
||||
- **THEN** IoT 卡管理页 MAY display its export button
|
||||
- **AND** 设备管理页 MUST NOT display its export button because of the IoT card permission
|
||||
51
openspec/changes/add-export-task-management/tasks.md
Normal file
51
openspec/changes/add-export-task-management/tasks.md
Normal file
@@ -0,0 +1,51 @@
|
||||
## 1. Proposal Review
|
||||
|
||||
- [x] 1.1 确认导出按钮权限编码：IoT 卡管理使用 `iot_card:export`，设备管理使用 `devices:export`。
|
||||
- [x] 1.2 确认导出任务管理权限编码：使用 `export_task:list`、`export_task:detail`、`export_task:download`、`export_task:cancel`。
|
||||
- [x] 1.3 确认导出格式默认 `xlsx`，并允许用户在弹窗中切换 `xlsx` / `csv`。
|
||||
- [x] 1.4 确认 IoT 卡和设备列表现有筛选参数作为导出任务 `query` 传给后端。
|
||||
|
||||
## 2. API And Types
|
||||
|
||||
- [x] 2.1 新增导出任务状态、场景、格式、列表项、详情、创建请求、取消响应等 TypeScript 类型。
|
||||
- [x] 2.2 新增 `ExportTaskService`，实现列表、创建、详情、取消接口。
|
||||
- [x] 2.3 在 API 和类型入口文件导出新增模块。
|
||||
- [x] 2.4 对齐统一响应结构 `code`、`msg`、`timestamp`、`data` 和分页结构 `page`、`size`、`total`、`items`。
|
||||
|
||||
## 3. Reusable Export Dialog
|
||||
|
||||
- [x] 3.1 新增可复用创建导出任务弹窗组件，支持传入 `scene`、当前列表查询条件和默认导出格式。
|
||||
- [x] 3.2 弹窗中明确展示导出规则说明：导出规则基于列表中的检索条件全量导出。
|
||||
- [x] 3.3 提交时调用创建导出任务接口，并在成功后提示任务已创建。
|
||||
- [x] 3.4 确保弹窗确认按钮和触发按钮均受对应权限控制。
|
||||
|
||||
## 4. Business Entry Points
|
||||
|
||||
- [x] 4.1 在 IoT 卡管理页增加导出按钮，打开弹窗时默认 `scene=iot_card`，并传入当前筛选条件快照。
|
||||
- [x] 4.2 在设备管理页增加导出按钮，打开弹窗时默认 `scene=device`，并传入当前筛选条件快照。
|
||||
- [x] 4.3 确保重置筛选、分页切换、重新搜索后导出使用最新检索条件。
|
||||
|
||||
## 5. Export Task List Page
|
||||
|
||||
- [x] 5.1 在资产管理下新增“导出管理”分组和“导出列表”路由、菜单、路由别名。
|
||||
- [x] 5.2 导出列表支持分页、场景、状态、创建开始时间、创建结束时间筛选。
|
||||
- [x] 5.3 表格展示任务编号、场景、状态、进度、格式、行数、分片、错误信息和时间字段；列表不展示文件 key。
|
||||
- [x] 5.4 任务编号支持点击进入导出任务详情页，行操作支持下载已完成任务、取消待处理/处理中任务。
|
||||
- [x] 5.5 下载操作必须先调用详情接口获取 `download_url`，且仅在已完成任务可用。
|
||||
- [x] 5.6 取消操作必须调用取消接口，并在成功后刷新列表。
|
||||
|
||||
## 6. Permissions And UX
|
||||
|
||||
- [x] 6.1 为所有新增按钮和行操作添加权限编码检查。
|
||||
- [x] 6.2 无权限时不显示对应入口，不依赖禁用态作为唯一保护。
|
||||
- [x] 6.3 对创建、详情、下载、取消失败提供稳定错误提示，不破坏列表渲染。
|
||||
|
||||
## 7. Verification
|
||||
|
||||
- [x] 7.1 验证 IoT 卡管理页可按当前筛选条件创建 `iot_card` 导出任务。
|
||||
- [x] 7.2 验证设备管理页可按当前筛选条件创建 `device` 导出任务。
|
||||
- [x] 7.3 验证导出列表分页和筛选参数与接口契约一致，且文件 key 不在列表字段中展示。
|
||||
- [x] 7.4 验证点击任务编号进入详情页，已完成任务可通过详情接口获取下载地址并下载。
|
||||
- [x] 7.5 验证待处理/处理中任务可取消，已完成/失败/已取消任务不可取消。
|
||||
- [x] 7.6 验证所有新增按钮和操作在无权限时不可见。
|
||||
- [x] 7.7 运行类型检查和相关 lint；新增文件 lint 通过，整仓构建受既有 TypeScript 债务阻塞。
|
||||
24
openspec/changes/add-order-export-scene/proposal.md
Normal file
24
openspec/changes/add-order-export-scene/proposal.md
Normal file
@@ -0,0 +1,24 @@
|
||||
# Change: 新增订单导出场景
|
||||
|
||||
## Why
|
||||
|
||||
导出管理现已支持设备管理和IoT卡管理两个导出场景，需要扩展至订单管理，以便订单列表也能按当前检索条件全量导出。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在导出任务中新增 `order` 导出场景支持
|
||||
- 导出管理列表的场景筛选中新增「订单管理」选项
|
||||
- 订单列表页面新增导出按钮，创建 `scene=order` 的导出任务
|
||||
- 订单导出按钮需要权限编码控制
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `export-task-management`
|
||||
- Affected code:
|
||||
- `src/types/api/exportTask.ts` - ExportTaskScene 类型
|
||||
- `src/views/asset-management/export-task-management/export-task-list/index.vue` - 场景选项
|
||||
- `src/components/business/ExportTaskCreateDialog.vue` - sceneName 映射
|
||||
- `src/views/order-management/order-list/index.vue` - 导出按钮
|
||||
- Dependencies:
|
||||
- 依赖后端 export task API 支持 `scene=order`
|
||||
@@ -0,0 +1,35 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Order Export Scene Support
|
||||
|
||||
The system SHALL support `scene="order"` for creating export tasks from the order management list.
|
||||
|
||||
#### Scenario: Create order export task from order management
|
||||
|
||||
- **GIVEN** 用户在订单管理页设置了列表检索条件
|
||||
- **AND** 当前用户具备订单导出权限
|
||||
- **WHEN** 用户确认创建导出任务
|
||||
- **THEN** 系统 MUST submit `scene="order"`
|
||||
- **AND** 系统 MUST submit the current order list filter conditions as `query`
|
||||
|
||||
### Requirement: Order Export in Export Task List
|
||||
|
||||
The admin frontend SHALL display "订单管理" as a selectable scene option when filtering export tasks.
|
||||
|
||||
#### Scenario: Filter export tasks by order scene
|
||||
|
||||
- **GIVEN** 用户打开导出列表页面
|
||||
- **WHEN** 用户选择「订单管理」作为场景筛选条件
|
||||
- **THEN** 系统 MUST call `GET /api/admin/export-tasks` with `scene=order`
|
||||
|
||||
## MODIFIED Requirements
|
||||
|
||||
### Requirement: Reusable Export Task Creation Dialog
|
||||
|
||||
The admin frontend already provides a reusable dialog for creating export tasks. This requirement adds the order scene to the scene name mapping.
|
||||
|
||||
#### Scenario: Display order scene name in dialog
|
||||
|
||||
- **GIVEN** 导出弹窗通过 `scene="order"` 打开
|
||||
- **WHEN** 弹窗渲染
|
||||
- **THEN** 弹窗 MUST display "订单管理" as the scene name
|
||||
33
openspec/changes/add-order-export-scene/tasks.md
Normal file
33
openspec/changes/add-order-export-scene/tasks.md
Normal file
@@ -0,0 +1,33 @@
|
||||
## 1. Proposal Review
|
||||
|
||||
- [ ] 1.1 确认订单导出权限编码（如 `orders:export`）
|
||||
- [ ] 1.2 确认导出任务 scene 值使用 `order`
|
||||
|
||||
## 2. Type Updates
|
||||
|
||||
- [ ] 2.1 在 `ExportTaskScene` 类型中添加 `order` 选项
|
||||
|
||||
## 3. Export Task List Page
|
||||
|
||||
- [ ] 3.1 在导出列表的场景筛选选项中添加「订单管理」
|
||||
|
||||
## 4. Export Dialog Component
|
||||
|
||||
- [ ] 4.1 在 `ExportTaskCreateDialog` 的 `sceneName` 映射中添加 `order` → '订单管理'
|
||||
|
||||
## 5. Order List Page
|
||||
|
||||
- [ ] 5.1 在订单列表页添加导出按钮
|
||||
- [ ] 5.2 使用 `ExportTaskCreateDialog`，传入 `scene="order"` 和当前筛选条件
|
||||
- [ ] 5.3 添加权限控制（按钮需检查 `orders:export` 权限）
|
||||
|
||||
## 6. Permissions And UX
|
||||
|
||||
- [ ] 6.1 导出按钮在无权限时隐藏
|
||||
- [ ] 6.2 创建导出任务成功后提示
|
||||
|
||||
## 7. Verification
|
||||
|
||||
- [ ] 7.1 验证订单列表页可按当前筛选条件创建 `order` 导出任务
|
||||
- [ ] 7.2 验证导出管理列表可按场景筛选 `order` 任务
|
||||
- [ ] 7.3 验证无权限时导出按钮不显示
|
||||
@@ -33,15 +33,19 @@
|
||||
## Decisions
|
||||
|
||||
- Decision: 能力名称使用 `payment-configuration-management`，而不是沿用页面路径中的 `wechat-config`
|
||||
|
||||
- Rationale: 该能力已经覆盖微信、小程序、公众号、支付宝和富友相关字段，业务边界明显大于“微信配置”。
|
||||
|
||||
- Decision: `provider_type` 在本次 spec 中严格按文档限定为 `wechat`、`wechat_v2`、`fuiou`
|
||||
|
||||
- Rationale: 这是文档明确枚举出的渠道主类型，spec 不应凭猜测新增 `alipay`。
|
||||
|
||||
- Decision: `ali_*` 字段在本次 spec 中被视为支付配置对象支持的可选扩展字段，但不单独引入新的 `provider_type`
|
||||
|
||||
- Rationale: 文档已经明确给出这些字段；在没有更正枚举之前，先把它们作为统一字段模型的一部分记录下来。
|
||||
|
||||
- Decision: 所有读取响应中的敏感信息都必须采用脱敏或配置状态标记，不能返回明文密钥
|
||||
|
||||
- Rationale: 文档的详情和当前生效配置示例已经给出了 `***`、`已配置`、`未配置` 这类语义。
|
||||
|
||||
- Decision: 更新接口采用部分更新语义，只要求提交实际需要修改的字段
|
||||
@@ -50,6 +54,7 @@
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 风险: 当前前端类型定义尚未覆盖 `ali_*` 字段，按 spec 对齐后会触发类型和页面联动修改。
|
||||
|
||||
- Mitigation: 实施时先调整 `src/types/api/wechatConfig.ts`，再逐步修改列表、表单和详情展示。
|
||||
|
||||
- 风险: 文档没有给出“如何切换当前生效配置”的写接口，只有 `is_active` 状态和 `/active` 查询接口。
|
||||
|
||||
@@ -0,0 +1,20 @@
|
||||
# Change: Add asset links to main wallet transactions
|
||||
|
||||
## Why
|
||||
|
||||
The agent fund overview detail drawer shows main wallet transaction records, but users cannot identify or navigate to the related asset for deductions tied to asset activity. The backend now returns `asset_identifier` from `GET /api/admin/shops/{shop_id}/main-wallet/transactions`, so the UI should expose it.
|
||||
|
||||
## What Changes
|
||||
|
||||
- Add an "资产标识" column to the "预充值钱包流水" table inside the agent fund overview commission detail drawer.
|
||||
- Read and type the new `asset_identifier` response field from main wallet transaction rows.
|
||||
- Render non-empty asset identifiers as clickable links that navigate to the asset information page for that identifier.
|
||||
- Render empty asset identifiers as `-` and do not make them clickable.
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `commission-management`
|
||||
- Affected code:
|
||||
- `src/types/api/commission.ts`
|
||||
- `src/views/commission-management/agent-fund-overview/index.vue`
|
||||
- Asset information route query handling is reused via `RoutesAlias.AssetInformation` and `identifier` search behavior.
|
||||
@@ -0,0 +1,25 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Main Wallet Transaction Asset Identifier Link
|
||||
|
||||
The agent fund overview commission detail drawer SHALL display the `asset_identifier` returned by `GET /api/admin/shops/{shop_id}/main-wallet/transactions` in the "预充值钱包流水" table as "资产标识" and allow users to navigate from that value to the asset information page.
|
||||
|
||||
#### Scenario: Display asset identifier in main wallet transactions
|
||||
|
||||
- **WHEN** a user opens an agent's commission detail drawer
|
||||
- **AND** selects the "预充值钱包流水" tab
|
||||
- **AND** a transaction row contains a non-empty `asset_identifier`
|
||||
- **THEN** the table displays that value in a column labeled "资产标识"
|
||||
- **AND** the value is visually presented as a clickable link
|
||||
|
||||
#### Scenario: Navigate to asset information from asset identifier
|
||||
|
||||
- **WHEN** a user clicks a non-empty "资产标识" value in the "预充值钱包流水" table
|
||||
- **THEN** the system navigates to the asset information page
|
||||
- **AND** the asset information page searches or loads using the clicked asset identifier
|
||||
|
||||
#### Scenario: Empty asset identifier is not clickable
|
||||
|
||||
- **WHEN** a main wallet transaction row has no `asset_identifier`
|
||||
- **THEN** the "资产标识" column displays `-`
|
||||
- **AND** no navigation action is available for that cell
|
||||
@@ -0,0 +1,13 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 Add optional `asset_identifier` to `MainWalletTransactionItem`.
|
||||
- [x] 1.2 Add an "资产标识" column to the agent fund overview detail drawer's "预充值钱包流水" table.
|
||||
- [x] 1.3 Render `asset_identifier` as a clickable link when present and `-` when absent.
|
||||
- [x] 1.4 Navigate clicks to the asset information page using the clicked asset identifier as the search query.
|
||||
- [x] 1.5 Ensure the click does not trigger unrelated row/table interactions.
|
||||
|
||||
## 2. Verification
|
||||
|
||||
- [x] 2.1 Verify the changed Vue file with lint or equivalent available project checks.
|
||||
- [ ] 2.2 Manually verify rows with `asset_identifier` display and navigate correctly.
|
||||
- [ ] 2.3 Manually verify rows without `asset_identifier` display `-` and are not clickable.
|
||||
@@ -0,0 +1,20 @@
|
||||
# Change: 为资产卡信息月内流量字段增加权限控制
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页卡信息中的“本月已用流量”和“运营商周期月内已用流量”属于敏感用量字段，需要统一通过同一个权限编码控制可见性，并对代理账号和企业账号强制隐藏。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 为资产信息页卡信息中的“本月已用流量”增加权限控制。
|
||||
- 为资产信息页卡信息中的“运营商周期月内已用流量”增加相同权限控制。
|
||||
- 两个字段统一使用权限编码 `asset_info:view_card_month_usage`。
|
||||
- 当当前登录账号 `user_type` 为 `3` 代理账号或 `4` 企业账号时，即使拥有权限也不显示这两个字段。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-card-usage-field-permission`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/components/BasicInfoCard.vue`
|
||||
- 角色/权限树配置中与 `asset_info:view_card_month_usage` 相关的注册位置
|
||||
@@ -0,0 +1,37 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Asset Card Month Usage Field Permission
|
||||
|
||||
The asset information page SHALL gate the card information fields `本月已用流量` and `运营商周期月内已用流量` with the same permission code `asset_info:view_card_month_usage`.
|
||||
|
||||
The asset information page MUST hide both fields for logged-in accounts whose `user_type` is `3` (代理账号) or `4` (企业账号), regardless of whether the account has `asset_info:view_card_month_usage`.
|
||||
|
||||
#### Scenario: Show both fields when platform user has permission
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 不是 `3` 也不是 `4`
|
||||
- **AND** 用户拥有 `asset_info:view_card_month_usage`
|
||||
- **WHEN** 页面渲染资产信息的卡信息区域
|
||||
- **THEN** 页面 MUST 显示 `本月已用流量`
|
||||
- **AND** 页面 MUST 显示 `运营商周期月内已用流量`
|
||||
|
||||
#### Scenario: Hide both fields when permission is missing
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 不是 `3` 也不是 `4`
|
||||
- **AND** 用户不拥有 `asset_info:view_card_month_usage`
|
||||
- **WHEN** 页面渲染资产信息的卡信息区域
|
||||
- **THEN** 页面 MUST NOT 显示 `本月已用流量`
|
||||
- **AND** 页面 MUST NOT 显示 `运营商周期月内已用流量`
|
||||
|
||||
#### Scenario: Hide both fields for agent accounts
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `3`
|
||||
- **WHEN** 页面渲染资产信息的卡信息区域
|
||||
- **THEN** 页面 MUST NOT 显示 `本月已用流量`
|
||||
- **AND** 页面 MUST NOT 显示 `运营商周期月内已用流量`
|
||||
|
||||
#### Scenario: Hide both fields for enterprise accounts
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `4`
|
||||
- **WHEN** 页面渲染资产信息的卡信息区域
|
||||
- **THEN** 页面 MUST NOT 显示 `本月已用流量`
|
||||
- **AND** 页面 MUST NOT 显示 `运营商周期月内已用流量`
|
||||
@@ -0,0 +1,6 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 在资产信息页卡信息中为“本月已用流量”接入 `asset_info:view_card_month_usage` 权限
|
||||
- [x] 1.2 在资产信息页卡信息中为“运营商周期月内已用流量”接入同一个 `asset_info:view_card_month_usage` 权限
|
||||
- [x] 1.3 确保 `user_type` 为 `3` 代理账号或 `4` 企业账号时隐藏上述两个字段
|
||||
- [x] 1.4 完成 OpenSpec 严格校验
|
||||
@@ -0,0 +1,28 @@
|
||||
# Change: 资产信息页全页面响应式适配
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页从资产查询、基础信息、当前生效套餐、套餐列表、钱包流水到操作审计日志包含大量描述项、操作按钮、筛选器和表格。当前小屏幕下存在固定宽度输入框、横向统计项和卡片头部内容挤压的问题，导致页面显示混乱。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 对资产信息页从搜索框到最底部操作审计日志进行响应式适配。
|
||||
- 小屏幕下搜索输入、查询、同步、返回上次搜索等操作应换行或纵向排列，避免横向溢出。
|
||||
- 基础信息、设备实时信息和当前生效套餐描述项应根据屏幕宽度减少列数。
|
||||
- 当前生效套餐的真/虚流量统计应在小屏下纵向堆叠，并保持进度条和百分比可读。
|
||||
- 套餐列表、钱包流水、操作审计日志等表格区域应在小屏下使用容器横向滚动承载表格，而不是撑破页面。
|
||||
- 钱包和操作审计日志的筛选器、分页器、卡片头部操作应在窄屏下换行并占满可用宽度。
|
||||
- 不改变现有接口、权限、业务数据和操作行为。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-information-responsive-layout`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/index.vue`
|
||||
- `src/views/asset-management/asset-information/components/AssetSearchCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/BasicInfoCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/CurrentPackageCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/PackageListCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/WalletTransactionCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/OperationLogsCard.vue`
|
||||
@@ -0,0 +1,49 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Asset Information Responsive Layout
|
||||
|
||||
The asset information page SHALL provide responsive layouts from the asset search area through the bottom operation audit log area so the page remains readable and operable on desktop, tablet, and mobile-width screens.
|
||||
|
||||
The responsive layout MUST NOT change existing API calls, permission checks, emitted events, business calculations, or displayed data semantics.
|
||||
|
||||
#### Scenario: Search area fits small screens
|
||||
|
||||
- **GIVEN** 用户在小屏幕设备上打开资产信息页
|
||||
- **WHEN** 页面渲染资产查询区域
|
||||
- **THEN** 搜索输入框 MUST NOT use a fixed width that exceeds the viewport
|
||||
- **AND** 查询、同步、返回上次搜索等按钮 MUST wrap or stack without causing page-level horizontal overflow
|
||||
- **AND** ICCID 放大提示 MUST fit within the viewport width
|
||||
|
||||
#### Scenario: Information cards reduce columns on narrow screens
|
||||
|
||||
- **GIVEN** 用户在平板或手机宽度打开资产信息页
|
||||
- **WHEN** 页面渲染基础信息、设备实时信息或当前生效套餐详情
|
||||
- **THEN** 描述项列数 MUST reduce according to available width
|
||||
- **AND** long identifiers or status text MUST wrap or truncate within their container instead of pushing the page wider
|
||||
|
||||
#### Scenario: Flow usage sections remain readable
|
||||
|
||||
- **GIVEN** 用户在小屏幕设备上查看当前生效套餐
|
||||
- **WHEN** 页面渲染真流量或虚流量使用区域
|
||||
- **THEN** flow statistic sections MUST stack vertically when horizontal space is insufficient
|
||||
- **AND** progress bars and percentages MUST remain visible and aligned within the card
|
||||
|
||||
#### Scenario: Tables scroll within their card on small screens
|
||||
|
||||
- **GIVEN** 用户在小屏幕设备上查看套餐列表、钱包流水或操作审计日志
|
||||
- **WHEN** table columns exceed the available content width
|
||||
- **THEN** the table container MUST provide horizontal scrolling
|
||||
- **AND** the overall page MUST NOT be widened by the table
|
||||
|
||||
#### Scenario: Filters and pagination adapt to narrow screens
|
||||
|
||||
- **GIVEN** 用户在小屏幕设备上查看钱包流水或操作审计日志
|
||||
- **WHEN** 页面渲染筛选器或分页器
|
||||
- **THEN** filter controls MUST wrap or stack within the card
|
||||
- **AND** pagination MUST remain reachable without overlapping adjacent content
|
||||
|
||||
#### Scenario: Desktop layout remains unchanged in behavior
|
||||
|
||||
- **GIVEN** 用户在桌面宽度打开资产信息页
|
||||
- **WHEN** 页面渲染资产信息内容
|
||||
- **THEN** existing business actions, permissions, table operations, and data displays MUST continue to behave as before
|
||||
@@ -0,0 +1,10 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 适配资产查询卡片的输入框、按钮组和放大提示在小屏下的布局
|
||||
- [x] 1.2 适配资产信息页主容器、卡片间距和卡片头部在小屏下的布局
|
||||
- [x] 1.3 适配基础信息与设备实时信息描述项在中小屏下的列数和操作按钮换行
|
||||
- [x] 1.4 适配当前生效套餐流量统计和套餐详情描述项在小屏下的布局
|
||||
- [x] 1.5 适配套餐列表表格、流量列和分页器在小屏下的横向滚动与换行
|
||||
- [x] 1.6 适配钱包流水筛选器、表格和分页器在小屏下的布局
|
||||
- [x] 1.7 适配操作审计日志筛选器、表格和分页器在小屏下的布局
|
||||
- [x] 1.8 完成 OpenSpec 严格校验
|
||||
@@ -0,0 +1,19 @@
|
||||
# Change: 统一资产套餐流量展示文案
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页的当前生效套餐和套餐列表对同一虚流量数据使用了不一致且容易造成误解的展示文案。需要按业务术语统一为更通用的流量用量表述。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 将“当前生效套餐”中虚流量统计区域的标题从“虚流量使用”调整为“流量用量”。
|
||||
- 将“套餐列表”流量字段中虚流量已用值的标签从“已使用虚流量”调整为“已使用流量”。
|
||||
- 保持现有流量字段、数值计算、进度条、可见性权限和接口契约不变。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `asset-package-traffic-display`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/components/CurrentPackageCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/PackageListCard.vue`
|
||||
- Dependencies: `update-asset-package-traffic-threshold-layout` 中定义的套餐流量展示能力
|
||||
@@ -0,0 +1,19 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Asset Package Traffic Terminology
|
||||
|
||||
The asset information page SHALL use the approved traffic terminology while retaining the existing virtual traffic data source and display behavior.
|
||||
|
||||
#### Scenario: Current package displays the traffic usage heading
|
||||
|
||||
- **GIVEN** 当前生效套餐的虚流量统计区域可见
|
||||
- **WHEN** 页面渲染该统计区域
|
||||
- **THEN** 系统 MUST 将区域标题显示为“流量用量”
|
||||
- **AND** 系统 MUST NOT 显示“虚流量使用”作为该区域标题
|
||||
|
||||
#### Scenario: Package list displays the used traffic label
|
||||
|
||||
- **GIVEN** 套餐列表记录的虚流量统计区域可见
|
||||
- **WHEN** 页面渲染该记录的已用流量值
|
||||
- **THEN** 系统 MUST 将字段标签显示为“已使用流量”
|
||||
- **AND** 系统 MUST NOT 显示“已使用虚流量”作为该字段标签
|
||||
@@ -0,0 +1,5 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 将当前生效套餐虚流量统计区域标题更新为“流量用量”。
|
||||
- [x] 1.2 将套餐列表虚流量已用字段标签更新为“已使用流量”。
|
||||
- [x] 1.3 验证文案变更不影响现有流量数值、进度条和权限可见性。
|
||||
@@ -0,0 +1,27 @@
|
||||
# Change: 调整资产套餐真虚流量展示布局
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页“当前生效套餐”和“套餐列表”目前将虚流量停机阈值及其断点标记放在虚流量使用区块，而真流量剩余未直接关联停机阈值。业务需要让停机阈值和断点与真流量剩余在同一区域展示，同时使虚流量区块完整呈现其基于真流量总量计算的总量和剩余。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在“当前生效套餐”和“套餐列表”的管理员/平台双流量视图中，将“虚流量停机阈值”展示项移至“真流量剩余”之后，继续显示现有的 `virtual_total_mb` 值。
|
||||
- 将虚流量停机阈值对应的断点标记从虚流量进度条移至真流量进度条；断点位置继续按 `virtual_total_mb / real_total_mb` 计算。
|
||||
- 在“虚流量使用”区块的“已使用”后新增：
|
||||
- “总量”：显示真流量总量 `real_total_mb`。
|
||||
- “剩余”：按 `real_total_mb - virtual_used_mb` 计算。
|
||||
- 保持真流量和虚流量进度条的现有计算口径、字段来源、权限控制及非管理员单一流量展示不变。
|
||||
- 不修改后端接口、响应字段或数据模型。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-package-traffic-display`
|
||||
- `asset-package-traffic-permissions`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/components/CurrentPackageCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/PackageListCard.vue`
|
||||
- Dependencies:
|
||||
- 继续使用现有套餐流量字段：`real_total_mb`、`real_used_mb`、`virtual_used_mb`、`virtual_total_mb`
|
||||
- 继续使用权限 `asset_info:view_current_package_real_usage` 和 `asset_info:view_current_package_virtual_usage`
|
||||
@@ -0,0 +1,55 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Virtual Traffic Threshold Aligns With Real Traffic Remaining
|
||||
|
||||
For super admins and platform users, the asset information page SHALL display the virtual traffic stop threshold immediately after real traffic remaining in both the `当前生效套餐` card and each applicable `套餐列表` row.
|
||||
|
||||
The displayed stop-threshold value MUST continue to use `virtual_total_mb`. The corresponding breakpoint marker MUST render on the real traffic progress bar and MUST continue to calculate its position as `virtual_total_mb / real_total_mb`.
|
||||
|
||||
#### Scenario: Current package shows threshold and breakpoint with real traffic
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 为 `1` 或 `2`
|
||||
- **AND** 当前套餐可展示真流量和虚流量使用信息
|
||||
- **WHEN** 页面渲染“当前生效套餐”的流量信息
|
||||
- **THEN** 系统 MUST 在真流量剩余后展示虚流量停机阈值
|
||||
- **AND** 停机阈值 MUST 显示 `virtual_total_mb` 的现有格式化值
|
||||
- **AND** 系统 MUST 将停机阈值断点标记渲染在真流量进度条
|
||||
- **AND** 断点位置 MUST 按 `virtual_total_mb / real_total_mb` 计算
|
||||
- **AND** 系统 MUST NOT 在虚流量进度条渲染该断点标记
|
||||
|
||||
#### Scenario: Package list shows threshold and breakpoint with real traffic
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 为 `1` 或 `2`
|
||||
- **AND** 套餐列表中的记录可展示真流量和虚流量使用信息
|
||||
- **WHEN** 页面渲染该记录的流量信息
|
||||
- **THEN** 系统 MUST 在真流量剩余后展示虚流量停机阈值
|
||||
- **AND** 停机阈值 MUST 显示该记录的 `virtual_total_mb` 的现有格式化值
|
||||
- **AND** 系统 MUST 将该记录的停机阈值断点标记渲染在真流量进度条
|
||||
- **AND** 断点位置 MUST 按该记录的 `virtual_total_mb / real_total_mb` 计算
|
||||
- **AND** 系统 MUST NOT 在虚流量进度条渲染该断点标记
|
||||
|
||||
### Requirement: Virtual Traffic Usage Displays Real Total And Remaining
|
||||
|
||||
For super admins and platform users, the `虚流量使用` section on the asset information page SHALL display virtual traffic used, real traffic total, and remaining virtual traffic capacity in that order in both the `当前生效套餐` card and each applicable `套餐列表` row.
|
||||
|
||||
The total MUST use `real_total_mb`. The remaining value MUST be calculated as `real_total_mb - virtual_used_mb`.
|
||||
|
||||
#### Scenario: Current package virtual traffic shows total and remaining
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 为 `1` 或 `2`
|
||||
- **AND** 当前套餐可展示虚流量使用信息
|
||||
- **WHEN** 页面渲染“当前生效套餐”的虚流量使用区块
|
||||
- **THEN** 系统 MUST 在虚流量已使用后展示总量
|
||||
- **AND** 总量 MUST 显示 `real_total_mb` 的现有格式化值
|
||||
- **AND** 系统 MUST 在总量后展示剩余
|
||||
- **AND** 剩余 MUST 显示 `real_total_mb - virtual_used_mb` 的现有格式化值
|
||||
|
||||
#### Scenario: Package list virtual traffic shows total and remaining
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 为 `1` 或 `2`
|
||||
- **AND** 套餐列表中的记录可展示虚流量使用信息
|
||||
- **WHEN** 页面渲染该记录的虚流量使用区块
|
||||
- **THEN** 系统 MUST 在虚流量已使用后展示总量
|
||||
- **AND** 总量 MUST 显示该记录的 `real_total_mb` 的现有格式化值
|
||||
- **AND** 系统 MUST 在总量后展示剩余
|
||||
- **AND** 剩余 MUST 显示 `real_total_mb - virtual_used_mb` 的现有格式化值
|
||||
@@ -0,0 +1,22 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Traffic Threshold And Virtual Statistics Follow Existing Usage Permissions
|
||||
|
||||
The asset information page SHALL apply the existing real and virtual traffic usage permissions to the relocated virtual traffic stop threshold, breakpoint marker, and added virtual traffic statistics.
|
||||
|
||||
#### Scenario: Hidden real traffic usage also hides relocated threshold and breakpoint
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 为 `1` 或 `2`
|
||||
- **AND** 账号缺少 `asset_info:view_current_package_real_usage` 权限
|
||||
- **WHEN** 页面渲染“当前生效套餐”或“套餐列表”的套餐流量信息
|
||||
- **THEN** 系统 MUST NOT 显示真流量统计
|
||||
- **AND** 系统 MUST NOT 显示位于真流量区域的虚流量停机阈值
|
||||
- **AND** 系统 MUST NOT 显示位于真流量进度条的停机阈值断点标记
|
||||
|
||||
#### Scenario: Hidden virtual traffic usage also hides added virtual statistics
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 为 `1` 或 `2`
|
||||
- **AND** 账号缺少 `asset_info:view_current_package_virtual_usage` 权限
|
||||
- **WHEN** 页面渲染“当前生效套餐”或“套餐列表”的套餐流量信息
|
||||
- **THEN** 系统 MUST NOT 显示虚流量使用区块
|
||||
- **AND** 系统 MUST NOT 显示虚流量区块中的已使用、总量或剩余统计
|
||||
@@ -0,0 +1,16 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 调整“当前生效套餐”真流量统计项，在真流量剩余后展示虚流量停机阈值，并保持 `virtual_total_mb` 的现有值格式化规则。
|
||||
- [x] 1.2 将“当前生效套餐”的停机阈值断点标记移至真流量进度条，继续按 `virtual_total_mb / real_total_mb` 定位。
|
||||
- [x] 1.3 调整“当前生效套餐”虚流量统计项，在已使用后展示真流量总量和按 `real_total_mb - virtual_used_mb` 计算的剩余量。
|
||||
- [x] 1.4 对套餐列表的每条管理员/平台套餐记录应用相同的阈值、断点和虚流量统计布局。
|
||||
- [x] 1.5 保持非管理员单一流量展示、现有权限可见性和各进度条百分比计算不变。
|
||||
|
||||
## 2. Verification
|
||||
|
||||
- [x] 2.1 验证“当前生效套餐”中停机阈值显示在真流量剩余后，且其值仍为 `virtual_total_mb`。
|
||||
- [x] 2.2 验证“当前生效套餐”中断点显示在真流量进度条，且其位置仍按 `virtual_total_mb / real_total_mb` 计算。
|
||||
- [x] 2.3 验证“当前生效套餐”虚流量使用依次显示已使用、总量（`real_total_mb`）和剩余（`real_total_mb - virtual_used_mb`）。
|
||||
- [x] 2.4 验证套餐列表的管理员/平台套餐记录具有与当前生效套餐一致的展示布局和计算结果。
|
||||
- [x] 2.5 验证真流量或虚流量查看权限缺失时，不展示该权限对应的统计项及关联阈值/断点内容。
|
||||
- [x] 2.6 验证非管理员账号继续使用现有单一流量展示，且真流量与虚流量进度百分比不变。
|
||||
@@ -0,0 +1,37 @@
|
||||
# Change: 更新资产解析流量汇总展示
|
||||
|
||||
## Why
|
||||
|
||||
后台“资产信息”页需要展示当前世代下所有套餐的虚流量已用量和剩余量，方便运营人员在查看资产基础信息时快速判断整体流量消耗情况。
|
||||
|
||||
后端通过 `GET /api/admin/assets/resolve/:identifier` 新增可选查询参数控制是否返回汇总字段；前端需要明确请求契约、类型契约和展示位置，避免默认查询缺失汇总数据。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 更新资产解析接口请求契约：
|
||||
- `GET /api/admin/assets/resolve/:identifier` 支持可选 Query 参数 `include_usage_summary: boolean`
|
||||
- 参数含义为是否返回当前世代流量汇总字段 `total_virtual_used_mb` / `total_virtual_remaining_mb`
|
||||
- 后端未传时默认不返回汇总数据；后台“资产信息”页发起解析请求时默认传 `include_usage_summary=true`
|
||||
- 更新资产解析接口响应契约：
|
||||
- 新增 `total_virtual_used_mb?: number | null`，表示所有套餐已用量(MB)，未请求时为 `null`
|
||||
- 新增 `total_virtual_remaining_mb?: number | null`，表示所有套餐剩余量(MB)，未请求时为 `null`
|
||||
- 更新后台“资产信息”基础信息展示：
|
||||
- 卡资产在“运营商状态”字段后新增“所有套餐已用量”和“所有套餐剩余量”
|
||||
- 设备资产在“SN”字段后新增“所有套餐已用量”和“所有套餐剩余量”
|
||||
- 字段值使用上述两个响应字段，并按流量大小格式化展示
|
||||
- 字段为空或未请求时显示稳定占位内容
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-information`
|
||||
- Affected code:
|
||||
- `src/api/modules/asset.ts`
|
||||
- `src/types/api/asset.ts`
|
||||
- `src/views/asset-management/asset-information/types.ts`
|
||||
- `src/views/asset-management/asset-information/composables/useAssetInfo.ts`
|
||||
- `src/views/asset-management/asset-information/components/BasicInfoCard.vue`
|
||||
- Dependencies:
|
||||
- `GET /api/admin/assets/resolve/:identifier` 后端支持 `include_usage_summary` Query 参数及响应字段
|
||||
- Breaking changes:
|
||||
- 无；新增请求参数和响应字段均为可选，前端资产信息页仅主动请求并展示新增数据
|
||||
@@ -0,0 +1,60 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Admin Asset Resolve Usage Summary Contract
|
||||
|
||||
The admin asset information integration SHALL request usage summary data from `GET /api/admin/assets/resolve/:identifier` by default and preserve the returned current-generation virtual usage summary fields.
|
||||
|
||||
#### Scenario: Asset information requests usage summary by default
|
||||
|
||||
- **GIVEN** 用户在后台“资产信息”页查询资产标识符
|
||||
- **WHEN** 前端调用 `GET /api/admin/assets/resolve/:identifier`
|
||||
- **THEN** 请求 Query MUST include `include_usage_summary=true`
|
||||
- **AND** `include_usage_summary` MUST be treated as a boolean query parameter
|
||||
|
||||
#### Scenario: Preserve usage summary fields from resolve response
|
||||
|
||||
- **GIVEN** `GET /api/admin/assets/resolve/:identifier?include_usage_summary=true` 返回 `total_virtual_used_mb` 和 `total_virtual_remaining_mb`
|
||||
- **WHEN** 前端解析资产详情响应
|
||||
- **THEN** 页面状态 MUST preserve `total_virtual_used_mb` as a `number | null` field
|
||||
- **AND** 页面状态 MUST preserve `total_virtual_remaining_mb` as a `number | null` field
|
||||
- **AND** `total_virtual_used_mb` MUST represent 所有套餐已用量(MB)
|
||||
- **AND** `total_virtual_remaining_mb` MUST represent 所有套餐剩余量(MB)
|
||||
|
||||
#### Scenario: Usage summary not requested
|
||||
|
||||
- **GIVEN** a caller invokes `GET /api/admin/assets/resolve/:identifier` without `include_usage_summary=true`
|
||||
- **WHEN** the response is parsed
|
||||
- **THEN** `total_virtual_used_mb` MAY be absent or `null`
|
||||
- **AND** `total_virtual_remaining_mb` MAY be absent or `null`
|
||||
|
||||
### Requirement: Admin Asset Usage Summary Display
|
||||
|
||||
The admin asset information view SHALL display current-generation virtual usage summary fields in both card and device asset information sections using asset-type-specific placement.
|
||||
|
||||
#### Scenario: Show card usage summary after carrier status
|
||||
|
||||
- **GIVEN** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** 当前资产详情状态中存在 `total_virtual_used_mb` 和 `total_virtual_remaining_mb`
|
||||
- **WHEN** 页面渲染“卡信息”区域
|
||||
- **THEN** 页面 MUST keep `运营商状态` visible
|
||||
- **AND** 页面 MUST display `所有套餐已用量` immediately after `运营商状态`, using `total_virtual_used_mb`
|
||||
- **AND** 页面 MUST display `所有套餐剩余量` immediately after `所有套餐已用量`, using `total_virtual_remaining_mb`
|
||||
- **AND** both values MUST be formatted as traffic sizes based on MB values
|
||||
|
||||
#### Scenario: Show device usage summary after SN
|
||||
|
||||
- **GIVEN** 用户正在查看后台“资产信息”中的设备资产详情
|
||||
- **AND** 当前资产详情状态中存在 `total_virtual_used_mb` 和 `total_virtual_remaining_mb`
|
||||
- **WHEN** 页面渲染“设备信息”区域
|
||||
- **THEN** 页面 MUST keep `SN` visible
|
||||
- **AND** 页面 MUST display `所有套餐已用量` immediately after `SN`, using `total_virtual_used_mb`
|
||||
- **AND** 页面 MUST display `所有套餐剩余量` immediately after `所有套餐已用量`, using `total_virtual_remaining_mb`
|
||||
- **AND** both values MUST be formatted as traffic sizes based on MB values
|
||||
|
||||
#### Scenario: Show placeholder when usage summary is unavailable
|
||||
|
||||
- **GIVEN** 用户正在查看后台“资产信息”中的卡资产详情或设备资产详情
|
||||
- **AND** `total_virtual_used_mb` or `total_virtual_remaining_mb` is `null` or absent
|
||||
- **WHEN** 页面渲染对应汇总字段
|
||||
- **THEN** 页面 MUST display `-` for the unavailable field
|
||||
- **AND** 页面 MUST NOT display `0` solely because the field is unavailable
|
||||
19
openspec/changes/update-asset-resolve-usage-summary/tasks.md
Normal file
19
openspec/changes/update-asset-resolve-usage-summary/tasks.md
Normal file
@@ -0,0 +1,19 @@
|
||||
## 1. Contract
|
||||
|
||||
- [x] 1.1 扩展资产解析接口方法，支持传入 `include_usage_summary` Query 参数。
|
||||
- [x] 1.2 扩展资产解析响应类型，新增 `total_virtual_used_mb?: number | null` 和 `total_virtual_remaining_mb?: number | null`。
|
||||
- [x] 1.3 确保后台“资产信息”页调用 `GET /api/admin/assets/resolve/:identifier` 时默认传 `include_usage_summary=true`。
|
||||
|
||||
## 2. State And Display
|
||||
|
||||
- [x] 2.1 在资产信息页面状态中保留 `total_virtual_used_mb` 和 `total_virtual_remaining_mb`。
|
||||
- [x] 2.2 在卡资产“卡信息”区域的“运营商状态”后新增“所有套餐已用量”和“所有套餐剩余量”。
|
||||
- [x] 2.3 在设备资产“设备信息”区域的“SN”后新增“所有套餐已用量”和“所有套餐剩余量”。
|
||||
- [x] 2.4 新增字段按流量大小格式化展示；当响应字段为 `null`、`undefined` 或未请求时显示 `-`。
|
||||
|
||||
## 3. Verification
|
||||
|
||||
- [ ] 3.1 验证资产信息页请求解析接口时 URL 包含 `include_usage_summary=true`。
|
||||
- [ ] 3.2 验证解析接口返回两个汇总字段时，卡资产详情在“运营商状态”后正确展示。
|
||||
- [ ] 3.3 验证解析接口返回两个汇总字段时，设备资产详情在“SN”后正确展示。
|
||||
- [ ] 3.4 验证两个汇总字段为 `null` 或缺失时，页面显示 `-` 且不报错。
|
||||
@@ -0,0 +1,44 @@
|
||||
# Change: 更新资产信息账号类型字段可见性与运营商账户展示
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页当前在卡/设备基础信息区域存在两类与最新业务口径不一致的问题：
|
||||
|
||||
- 卡资产“卡信息”中的 `实名认证策略` 仍会对 `user_type=3`（代理账号）和 `user_type=4`（企业账号）显示。
|
||||
- 设备资产“设备信息”中的 `实名认证策略` 和 `制造商` 仍会对 `user_type=3/4` 显示。
|
||||
- 卡资产“运营商账户”当前展示的是 `carrier_name`，而最新要求需要改为展示 `carrier_type`，并按运营商管理中的映射规则转成中文，例如 `CTCC -> 中国电信`。
|
||||
|
||||
如果不统一这些展示规则，不同账号在资产信息页会继续看到不应暴露的字段，同时“运营商账户”的显示口径也会与系统内其他模块不一致。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 更新卡资产“卡信息”区域：
|
||||
- 当当前登录账号 `user_type` 为 `3` 或 `4` 时，隐藏 `实名认证策略` 字段。
|
||||
- 当当前登录账号 `user_type` 为 `3` 或 `4` 时，`运营商账户` 字段改为展示 `carrier_type` 的中文映射值，而不是 `carrier_name`。
|
||||
- 当当前登录账号 `user_type` 不是 `3` 且不是 `4` 时，`运营商账户` 字段继续保持当前 `carrier_name` 展示口径。
|
||||
- 已知运营商类型映射沿用运营商管理口径：`CMCC -> 中国移动`、`CUCC -> 中国联通`、`CTCC -> 中国电信`、`CBN -> 中国广电`。
|
||||
- 当 `carrier_type` 为空时显示 `-`；若返回未知编码，则保留原编码展示，避免吞掉上游信息。
|
||||
- 更新设备资产“设备信息”区域：
|
||||
- 当当前登录账号 `user_type` 为 `3` 或 `4` 时，隐藏 `实名认证策略` 字段。
|
||||
- 当当前登录账号 `user_type` 为 `3` 或 `4` 时，隐藏 `制造商` 字段。
|
||||
- 范围约束：
|
||||
- 本提案仅调整资产信息基础描述区字段展示。
|
||||
- 本提案不改动实名认证策略相关操作按钮的权限和可见性。
|
||||
- 本提案不改动设备详情“绑定卡列表”中的列展示规则，除非后续另行提出变更。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-information`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/components/BasicInfoCard.vue`
|
||||
- `src/views/asset-management/asset-information/composables/useAssetFormatters.ts`
|
||||
- `src/views/asset-management/asset-information/types.ts`
|
||||
- `src/views/asset-management/asset-information/composables/useAssetInfo.ts`
|
||||
- `src/config/constants/carrierTypes.ts`
|
||||
- Dependencies:
|
||||
- 依赖当前登录账号 `user_type` 可从用户状态中稳定读取
|
||||
- 依赖资产详情接口继续返回 `carrier_type`
|
||||
- 运营商类型中文映射应与运营商管理模块保持一致
|
||||
- Breaking changes:
|
||||
- 无外部接口破坏性变更；本次仅调整后台页面展示契约和字段可见性
|
||||
@@ -0,0 +1,123 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Admin Card Asset Carrier Type Contract
|
||||
|
||||
The admin asset information integration SHALL accept and preserve `carrier_type` from `GET /api/admin/assets/resolve/:identifier` for card assets so the card information section can render the carrier account value from the carrier type code.
|
||||
|
||||
#### Scenario: Card asset detail preserves carrier_type from resolve response
|
||||
|
||||
- **GIVEN** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** `GET /api/admin/assets/resolve/:identifier` 返回了 `carrier_type`
|
||||
- **WHEN** 前端解析卡资产详情响应
|
||||
- **THEN** 页面状态 MUST 保留该 `carrier_type` 原始值
|
||||
- **AND** 后续“卡信息”区域的 `运营商账户` 展示 MUST 基于该状态值进行格式化
|
||||
|
||||
#### Scenario: Missing carrier_type does not break card asset detail parsing
|
||||
|
||||
- **GIVEN** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** `GET /api/admin/assets/resolve/:identifier` 未返回 `carrier_type` 或该字段为空
|
||||
- **WHEN** 前端解析卡资产详情响应
|
||||
- **THEN** 页面 MUST 继续保留其他卡资产字段的解析行为
|
||||
- **AND** MUST NOT 因 `carrier_type` 缺失导致“卡信息”区域渲染失败
|
||||
|
||||
### Requirement: Admin Card Asset Carrier Account Display
|
||||
|
||||
The admin asset information view SHALL render the card information field `运营商账户` according to the current logged-in account type.
|
||||
|
||||
For logged-in accounts whose `user_type` is `3` (代理账号) or `4` (企业账号), the field MUST use `carrier_type` and the same carrier-type-to-Chinese mapping used by carrier management.
|
||||
|
||||
Known mappings MUST include `CMCC -> 中国移动`, `CUCC -> 中国联通`, `CTCC -> 中国电信`, and `CBN -> 中国广电`.
|
||||
|
||||
For other logged-in account types, the field MUST keep the existing `carrier_name` display behavior.
|
||||
|
||||
If `carrier_type` is empty or missing, the page MUST display `-`. If `carrier_type` contains an unknown code, the page MUST preserve and display the original code.
|
||||
|
||||
#### Scenario: Show China Telecom label for CTCC in card information for agent or enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `3` 或 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** 当前卡资产详情状态中的 `carrier_type` 为 `CTCC`
|
||||
- **WHEN** 页面渲染“卡信息”区域中的 `运营商账户`
|
||||
- **THEN** 页面 MUST 显示 `中国电信`
|
||||
|
||||
#### Scenario: Show placeholder when carrier_type is empty for agent or enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `3` 或 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** 当前卡资产详情状态中的 `carrier_type` 为空、缺失或仅包含空白字符
|
||||
- **WHEN** 页面渲染“卡信息”区域中的 `运营商账户`
|
||||
- **THEN** 页面 MUST 显示 `-`
|
||||
|
||||
#### Scenario: Preserve unknown carrier_type code for agent or enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `3` 或 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** 当前卡资产详情状态中的 `carrier_type` 为未收录的编码
|
||||
- **WHEN** 页面渲染“卡信息”区域中的 `运营商账户`
|
||||
- **THEN** 页面 MUST 直接显示该原始编码
|
||||
- **AND** MUST NOT 错误映射为其他运营商中文名称
|
||||
|
||||
#### Scenario: Keep carrier_name display for non-agent non-enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 不是 `3` 也不是 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **AND** 当前卡资产详情状态中的 `carrier_name` 为有效值
|
||||
- **WHEN** 页面渲染“卡信息”区域中的 `运营商账户`
|
||||
- **THEN** 页面 MUST 显示该 `carrier_name`
|
||||
|
||||
### Requirement: Admin Card Realname Policy Visibility By Account Type
|
||||
|
||||
The admin asset information view SHALL hide the card information field `实名认证策略` for logged-in accounts whose `user_type` is `3` (代理账号) or `4` (企业账号).
|
||||
|
||||
For other logged-in account types, the page SHALL keep the existing card information field visibility behavior for `实名认证策略`.
|
||||
|
||||
#### Scenario: Hide card realname policy for agent account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `3`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **WHEN** 页面渲染“卡信息”区域
|
||||
- **THEN** 页面 MUST NOT 显示 `实名认证策略` 字段
|
||||
|
||||
#### Scenario: Hide card realname policy for enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **WHEN** 页面渲染“卡信息”区域
|
||||
- **THEN** 页面 MUST NOT 显示 `实名认证策略` 字段
|
||||
|
||||
#### Scenario: Keep card realname policy visible for non-agent non-enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 不是 `3` 也不是 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的卡资产详情
|
||||
- **WHEN** 页面渲染“卡信息”区域
|
||||
- **THEN** 页面 MUST 继续按现有规则渲染 `实名认证策略` 字段
|
||||
|
||||
### Requirement: Admin Device Sensitive Field Visibility By Account Type
|
||||
|
||||
The admin asset information view SHALL hide the device information fields `实名认证策略` and `制造商` for logged-in accounts whose `user_type` is `3` (代理账号) or `4` (企业账号).
|
||||
|
||||
For other logged-in account types, the page SHALL keep the existing device information field visibility behavior for both fields.
|
||||
|
||||
#### Scenario: Hide device realname policy and manufacturer for agent account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `3`
|
||||
- **AND** 用户正在查看后台“资产信息”中的设备资产详情
|
||||
- **WHEN** 页面渲染“设备信息”区域
|
||||
- **THEN** 页面 MUST NOT 显示 `实名认证策略` 字段
|
||||
- **AND** 页面 MUST NOT 显示 `制造商` 字段
|
||||
|
||||
#### Scenario: Hide device realname policy and manufacturer for enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 是 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的设备资产详情
|
||||
- **WHEN** 页面渲染“设备信息”区域
|
||||
- **THEN** 页面 MUST NOT 显示 `实名认证策略` 字段
|
||||
- **AND** 页面 MUST NOT 显示 `制造商` 字段
|
||||
|
||||
#### Scenario: Keep device realname policy and manufacturer visible for non-agent non-enterprise account
|
||||
|
||||
- **GIVEN** 当前登录账号的 `user_type` 不是 `3` 也不是 `4`
|
||||
- **AND** 用户正在查看后台“资产信息”中的设备资产详情
|
||||
- **WHEN** 页面渲染“设备信息”区域
|
||||
- **THEN** 页面 MUST 继续按现有规则渲染 `实名认证策略` 字段
|
||||
- **AND** 页面 MUST 继续按现有规则渲染 `制造商` 字段
|
||||
@@ -0,0 +1,20 @@
|
||||
## 1. Contract And Formatting
|
||||
|
||||
- [x] 1.1 补齐资产信息页面本地类型/状态中的 `carrier_type` 字段，确保卡资产详情可稳定保留该值。
|
||||
- [x] 1.2 复用运营商管理中的运营商类型映射规则，为资产信息页提供 `carrier_type` 到中文文案的格式化能力。
|
||||
|
||||
## 2. UI Visibility
|
||||
|
||||
- [x] 2.1 调整卡资产“卡信息”区域的 `运营商账户` 字段：`user_type=3/4` 展示 `carrier_type` 中文映射，其他账号继续展示原来的 `carrier_name`。
|
||||
- [x] 2.2 当当前登录账号 `user_type` 为 `3` 或 `4` 时，隐藏卡资产“卡信息”区域的 `实名认证策略` 字段。
|
||||
- [x] 2.3 当当前登录账号 `user_type` 为 `3` 或 `4` 时，隐藏设备资产“设备信息”区域的 `实名认证策略` 和 `制造商` 字段。
|
||||
- [x] 2.4 确认本次变更仅影响基础信息描述区，不改动实名认证策略操作按钮和设备绑定卡列表列。
|
||||
|
||||
## 3. Verification
|
||||
|
||||
- [ ] 3.1 验证 `user_type=3/4` 查看卡资产且返回 `carrier_type=CTCC` 时，“运营商账户”显示为 `中国电信`。
|
||||
- [ ] 3.2 验证 `user_type=3/4` 查看卡资产且返回 `carrier_type=CMCC/CUCC/CBN` 时，“运营商账户”分别显示与运营商管理一致的中文文案；空值显示 `-`。
|
||||
- [ ] 3.3 验证 `user_type=3/4` 查看卡资产且返回未知 `carrier_type` 编码时，“运营商账户”保留原编码展示。
|
||||
- [ ] 3.4 验证 `user_type=3` 和 `user_type=4` 查看卡资产时，不显示 `实名认证策略` 字段。
|
||||
- [ ] 3.5 验证 `user_type=3` 和 `user_type=4` 查看设备资产时，不显示 `实名认证策略` 和 `制造商` 字段。
|
||||
- [ ] 3.6 验证其他账号类型查看卡资产时，“运营商账户”继续显示原来的 `carrier_name`；其余上述字段继续按现有规则显示。
|
||||
@@ -0,0 +1,20 @@
|
||||
# Change: 按虚流量启用状态隐藏资产套餐虚流量展示
|
||||
|
||||
## Why
|
||||
|
||||
资产信息页的当前生效套餐和套餐列表已经会展示虚流量使用、停机阈值和百分比。但当接口返回 `enable_virtual_data: false` 时，该套餐并未启用虚流量，上述虚流量相关展示会造成误解。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在资产信息页“当前生效套餐”中，当当前套餐 `enable_virtual_data` 为 `false` 时隐藏“虚流量使用”区块。
|
||||
- 在资产信息页“套餐列表”中，当套餐记录 `enable_virtual_data` 为 `false` 时隐藏“已使用虚流量 / 停机阈值 / 虚流量进度百分比”展示。
|
||||
- 现有权限 `asset_info:view_current_package_virtual_usage` 仍继续生效；只有同时满足拥有权限且 `enable_virtual_data !== false` 时才展示虚流量信息。
|
||||
- 不改变真流量展示和非管理员合并流量摘要的既有逻辑。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-package-traffic-permissions`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/asset-information/components/CurrentPackageCard.vue`
|
||||
- `src/views/asset-management/asset-information/components/PackageListCard.vue`
|
||||
@@ -0,0 +1,52 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Asset Virtual Traffic Enabled Visibility
|
||||
|
||||
The asset information page SHALL hide package virtual-traffic displays when the related package record has `enable_virtual_data` equal to `false`.
|
||||
|
||||
The existing permission `asset_info:view_current_package_virtual_usage` MUST still be required for virtual-traffic displays. A virtual-traffic display MUST be visible only when the user has `asset_info:view_current_package_virtual_usage` and the related package record does not have `enable_virtual_data` equal to `false`.
|
||||
|
||||
#### Scenario: Hide current-package virtual traffic when disabled
|
||||
|
||||
- **GIVEN** 当前生效套餐接口返回 `enable_virtual_data: false`
|
||||
- **AND** 用户拥有 `asset_info:view_current_package_virtual_usage`
|
||||
- **WHEN** 页面渲染资产信息的 `当前生效套餐`
|
||||
- **THEN** 页面 MUST NOT 显示 `虚流量使用`
|
||||
- **AND** 页面 MUST NOT 显示该虚流量区块内的 `已使用`
|
||||
- **AND** 页面 MUST NOT 显示该虚流量区块内的 `停机阈值`
|
||||
- **AND** 页面 MUST NOT 显示该虚流量区块内的进度百分比
|
||||
|
||||
#### Scenario: Show current-package virtual traffic when enabled and permitted
|
||||
|
||||
- **GIVEN** 当前生效套餐接口返回 `enable_virtual_data: true`
|
||||
- **AND** 用户拥有 `asset_info:view_current_package_virtual_usage`
|
||||
- **WHEN** 页面渲染资产信息的 `当前生效套餐`
|
||||
- **THEN** 页面 MUST 显示 `虚流量使用`
|
||||
- **AND** 页面 MUST 显示该虚流量区块内的 `已使用`
|
||||
- **AND** 页面 MUST 显示该虚流量区块内的 `停机阈值`
|
||||
- **AND** 页面 MUST 显示该虚流量区块内的进度百分比
|
||||
|
||||
#### Scenario: Hide package-list virtual traffic when disabled
|
||||
|
||||
- **GIVEN** 套餐列表中某条套餐记录返回 `enable_virtual_data: false`
|
||||
- **AND** 用户拥有 `asset_info:view_current_package_virtual_usage`
|
||||
- **WHEN** 页面渲染该套餐记录的流量列
|
||||
- **THEN** 页面 MUST NOT 显示 `已使用虚流量`
|
||||
- **AND** 页面 MUST NOT 显示 `停机阈值`
|
||||
- **AND** 页面 MUST NOT 显示该套餐记录的虚流量进度百分比
|
||||
|
||||
#### Scenario: Show package-list virtual traffic when enabled and permitted
|
||||
|
||||
- **GIVEN** 套餐列表中某条套餐记录返回 `enable_virtual_data: true`
|
||||
- **AND** 用户拥有 `asset_info:view_current_package_virtual_usage`
|
||||
- **WHEN** 页面渲染该套餐记录的流量列
|
||||
- **THEN** 页面 MUST 显示 `已使用虚流量`
|
||||
- **AND** 页面 MUST 显示 `停机阈值`
|
||||
- **AND** 页面 MUST 显示该套餐记录的虚流量进度百分比
|
||||
|
||||
#### Scenario: Keep hiding virtual traffic without permission
|
||||
|
||||
- **GIVEN** 套餐记录返回 `enable_virtual_data: true`
|
||||
- **AND** 用户不拥有 `asset_info:view_current_package_virtual_usage`
|
||||
- **WHEN** 页面渲染资产信息的套餐流量展示
|
||||
- **THEN** 页面 MUST NOT 显示虚流量相关展示
|
||||
@@ -0,0 +1,6 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 在“当前生效套餐”中按 `enable_virtual_data` 控制虚流量区块显示
|
||||
- [x] 1.2 在“套餐列表”中按每条记录的 `enable_virtual_data` 控制虚流量展示和进度百分比显示
|
||||
- [x] 1.3 确认现有虚流量权限仍参与显示判断
|
||||
- [x] 1.4 完成 OpenSpec 严格校验
|
||||
@@ -5,6 +5,7 @@
|
||||
当前后台设备管理和企业设备授权流程还没有完整接入新的设备激活状态字段，导致运营人员无法按“已激活 / 未激活”筛选设备，也无法在资产详情中直接看到设备激活状态名称。
|
||||
|
||||
最新接口契约补充了以下内容：
|
||||
|
||||
- 设备列表接口新增可选过滤参数 `activation_status`
|
||||
- 设备列表与资产解析相关响应新增 `activation_status_name`
|
||||
- 企业设备授权弹窗中的可选设备列表也需要沿用这套激活状态筛选与展示规则
|
||||
|
||||
@@ -0,0 +1,39 @@
|
||||
# Change: 允许企业账号登录后台管理系统
|
||||
|
||||
## Why
|
||||
|
||||
当前前端登录流程会在登录接口成功返回后，基于 `user_type=4` 对企业账号做前端拦截，并提示“企业账号无法登录后台管理系统，请使用平台/代理账号登录”。这与最新业务要求不一致，导致企业账号即使后端已返回有效 token、菜单和权限，也无法进入后台。
|
||||
|
||||
如果只保留现状，企业账号无法访问后台中已经按权限和菜单控制开放给它们的页面，也会与近期多项针对企业账号后台可见性和资产能力的变更方向相冲突。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 移除前端登录流程中对 `user_type=4` 企业账号的后台登录拦截。
|
||||
- 企业账号登录成功后，前端应与其他账号类型一致地：
|
||||
- 保存 token
|
||||
- 保存用户信息
|
||||
- 保存权限、菜单和按钮数据
|
||||
- 在存在可用后台菜单和权限时，继续进入后台默认首页/重定向目标页
|
||||
- 当登录接口成功但 `menus` 为空或 `permissions` 为空时：
|
||||
- 前端仅提示“当前账号暂无任何权限，请联系管理员分配角色和权限”
|
||||
- 不继续进入后台首页或动态路由注册流程
|
||||
- 不作为这条提示的后续动作调用退出登录接口
|
||||
- 登录成功后的页面访问边界继续由现有菜单、路由权限、按钮权限和后端接口权限共同控制。
|
||||
- 本提案不要求本次同步放开所有企业账号受限接口或页面；仅调整“企业账号能否进入后台”的前端准入逻辑。
|
||||
- 本提案不修改登录接口路径、请求参数或返回结构。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `admin-authentication`
|
||||
- Affected code:
|
||||
- `src/composables/useLogin.ts`
|
||||
- `src/router/guards/beforeEach.ts`
|
||||
- `src/router/guards/permission.ts`
|
||||
- `src/App.vue`
|
||||
- 其他依赖当前登录态、菜单和权限进行页面准入的后台入口逻辑
|
||||
- Dependencies:
|
||||
- 后端登录接口继续允许企业账号返回有效 `access_token`、`user`、`permissions`、`menus`、`buttons`
|
||||
- 企业账号需要至少具备一部分后台菜单或权限，才能进入可访问页面
|
||||
- Breaking changes:
|
||||
- 无外部接口破坏性变更；本次为前端登录准入行为放宽
|
||||
@@ -0,0 +1,70 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Enterprise Account Admin Login Admission
|
||||
|
||||
The admin login flow SHALL allow enterprise accounts whose `user_type` is `4` to sign in to the admin system when the login API returns a successful response with valid authentication data.
|
||||
|
||||
The frontend MUST NOT reject admin login solely because `user_type` equals `4`.
|
||||
|
||||
#### Scenario: Enterprise account is allowed to complete admin login
|
||||
|
||||
- **GIVEN** 用户使用企业账号凭证登录后台管理系统
|
||||
- **AND** 登录接口返回成功状态
|
||||
- **AND** 返回数据包含有效 `access_token`
|
||||
- **AND** 返回数据中的 `user.user_type` 为 `4`
|
||||
- **WHEN** 前端处理登录成功响应
|
||||
- **THEN** 前端 MUST 继续执行后台登录成功流程
|
||||
- **AND** MUST NOT 弹出“企业账号无法登录后台管理系统，请使用平台/代理账号登录”提示
|
||||
|
||||
#### Scenario: Enterprise account login still fails when login API itself fails
|
||||
|
||||
- **GIVEN** 用户使用企业账号凭证登录后台管理系统
|
||||
- **AND** 登录接口返回失败状态，或未返回有效 `access_token`
|
||||
- **WHEN** 前端处理登录响应
|
||||
- **THEN** 前端 MUST 继续按现有登录失败流程处理
|
||||
- **AND** MUST NOT 将“允许企业账号登录后台”解释为绕过登录接口失败
|
||||
|
||||
### Requirement: Enterprise Account Login State Persistence
|
||||
|
||||
The admin login flow SHALL persist enterprise-account login state using the same token, user, permissions, menus, and buttons handling used for other successful admin logins only when the login response provides usable admin-access data.
|
||||
|
||||
#### Scenario: Enterprise account saves auth state after successful login with usable admin access data
|
||||
|
||||
- **GIVEN** 用户使用企业账号成功登录后台管理系统
|
||||
- **AND** 登录返回中包含 `access_token`、`refresh_token`、`user`、`permissions`、`menus`、`buttons`
|
||||
- **AND** `permissions` 非空
|
||||
- **AND** `menus` 非空
|
||||
- **WHEN** 前端写入登录态
|
||||
- **THEN** 前端 MUST 保存 token
|
||||
- **AND** MUST 保存用户信息
|
||||
- **AND** MUST 保存权限、菜单和按钮数据
|
||||
|
||||
#### Scenario: Enterprise account shows no-permission warning without logout follow-up
|
||||
|
||||
- **GIVEN** 用户使用企业账号成功登录后台管理系统
|
||||
- **AND** 登录返回中的 `permissions` 为空，或 `menus` 为空
|
||||
- **WHEN** 前端处理登录成功响应
|
||||
- **THEN** 前端 MUST 继续显示现有“当前账号暂无任何权限，请联系管理员分配角色和权限”提示
|
||||
- **AND** MUST NOT 因为空权限或空菜单回退为企业账号登录拦截
|
||||
- **AND** MUST NOT 继续进入后台首页或动态路由注册流程
|
||||
- **AND** MUST NOT 因这条无权限提示而调用退出登录接口
|
||||
|
||||
### Requirement: Enterprise Account Admin Entry Uses Existing Authorization Boundaries
|
||||
|
||||
Allowing enterprise accounts to sign in to the admin system SHALL NOT by itself grant additional page or API access beyond the existing menu, route-permission, button-permission, and backend authorization boundaries.
|
||||
|
||||
#### Scenario: Enterprise account enters admin and follows existing route registration flow
|
||||
|
||||
- **GIVEN** 用户使用企业账号成功登录后台管理系统
|
||||
- **AND** 登录返回中的 `permissions` 非空
|
||||
- **AND** 登录返回中的 `menus` 非空
|
||||
- **WHEN** 前端进入登录后的路由注册和首页跳转流程
|
||||
- **THEN** 前端 MUST 继续按现有菜单和动态路由注册逻辑处理
|
||||
- **AND** MUST NOT 因 `user_type=4` 在该阶段额外拒绝用户进入后台
|
||||
|
||||
#### Scenario: Enterprise account page access remains permission-controlled
|
||||
|
||||
- **GIVEN** 用户已使用企业账号登录后台管理系统
|
||||
- **WHEN** 用户尝试访问某个后台页面或触发某个后台操作
|
||||
- **THEN** 页面访问和操作可用性 MUST 继续由现有菜单、路由权限、按钮权限和后端接口鉴权决定
|
||||
- **AND** 允许登录后台本身 MUST NOT 被解释为默认拥有全部后台页面和操作权限
|
||||
@@ -0,0 +1,17 @@
|
||||
## 1. Login Flow
|
||||
|
||||
- [x] 1.1 移除登录成功后对 `user_type=4` 企业账号的前端拒绝逻辑和错误提示。
|
||||
- [x] 1.2 确保企业账号在登录成功后与其他账号一样完成 token、用户信息、权限、菜单、按钮的保存流程。
|
||||
- [x] 1.3 当登录成功但 `menus` 或 `permissions` 为空时，仅提示“当前账号暂无任何权限，请联系管理员分配角色和权限”并停止后续登录流程，不调用退出登录接口。
|
||||
|
||||
## 2. Navigation And Access
|
||||
|
||||
- [x] 2.1 确保企业账号在具备可用后台菜单和权限时，继续走现有后台首页跳转和路由注册流程，不因账号类型被额外拦截。
|
||||
- [x] 2.2 确认企业账号后台访问范围仍由现有菜单、路由权限和后端接口权限控制，而不是在登录阶段一刀切拒绝。
|
||||
|
||||
## 3. Verification
|
||||
|
||||
- [ ] 3.1 验证企业账号登录成功后不再出现“企业账号无法登录后台管理系统，请使用平台/代理账号登录”提示。
|
||||
- [ ] 3.2 验证企业账号在具备可用后台菜单和权限时，能正常保存登录态并进入后台首页或重定向目标页。
|
||||
- [ ] 3.3 验证企业账号在菜单为空或权限为空时，仅提示“暂无任何权限”，且不会继续调用退出登录接口。
|
||||
- [ ] 3.4 验证平台账号和代理账号登录流程不受影响。
|
||||
@@ -0,0 +1,34 @@
|
||||
## Context
|
||||
|
||||
Enterprise asset authorization currently has two hidden pages launched from enterprise customer rows. The requested workflow moves those operations to the asset lists so users can filter assets by enterprise authorization state and act on the same list they export from.
|
||||
|
||||
## Goals
|
||||
|
||||
- Add enterprise authorization filters to IoT card management and device management.
|
||||
- Add direct card/device enterprise authorization and recall actions beside existing export actions.
|
||||
- Protect each new action with an independent button permission code.
|
||||
- Remove enterprise customer row authorization shortcuts and the replaced “企业卡管理” / “企业设备列表” hidden pages.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Do not change backend endpoint paths.
|
||||
- Do not add new route pages for this workflow.
|
||||
- Do not preserve compatibility routes for the old “企业卡管理” or “企业设备列表” pages unless a product requirement is added later.
|
||||
|
||||
## Decisions
|
||||
|
||||
- New permission codes:
|
||||
- `iot_card:authorize_enterprise` for “授权卡给企业”.
|
||||
- `iot_card:recall_enterprise_authorization` for “回收卡授权”.
|
||||
- `devices:authorize_enterprise` for “授权设备给企业”.
|
||||
- `devices:recall_enterprise_authorization` for “撤销设备授权”.
|
||||
- Authorization and recall dialogs will require a target/source enterprise ID, except recall may prefill or lock it when `authorized_enterprise_id` is present in current filters or a single selected-row enterprise ID can be safely inferred from list response data.
|
||||
- List-mode operations use selected rows. Card operations submit `iccids`; device operations submit `device_nos` derived from available list response identifiers such as `virtual_no`.
|
||||
- Filter-mode operations submit only non-empty filter fields supported by `docs/授权、回收.md`.
|
||||
- The `shop_id` filter in “授权卡给企业” and “授权设备给企业” dialogs uses the same lazy `ElCascader` tree pattern as the add-shop dialog’s “上级店铺” field: `ShopService.getShopsCascade({ parent_id })`, `checkStrictly: true`, and submit the last selected path node as `shop_id`.
|
||||
- Old hidden pages are deleted rather than kept as redirects because the list-page authorization workflow replaces “企业卡管理” and “企业设备列表”.
|
||||
|
||||
## Risks
|
||||
|
||||
- The list response field names for enterprise authorization metadata may vary. Implementation should read current API response types and use returned fields when available; if a required source enterprise cannot be inferred, require explicit enterprise selection in the recall dialog.
|
||||
- Existing `add-enterprise-device-authorization` OpenSpec change overlaps conceptually but proposes a separate enterprise-device page. This change supersedes that approach for the current product direction.
|
||||
@@ -0,0 +1,38 @@
|
||||
# Change: Move Enterprise Asset Authorization To Asset Lists
|
||||
|
||||
## Why
|
||||
|
||||
企业卡授权和设备授权当前从企业客户详情入口进入独立页面，操作路径长且与资产实际筛选、导出、批量操作割裂。IoT 卡管理和设备管理列表需要直接支持按企业授权状态过滤，并在列表页完成企业授权和授权回收。
|
||||
|
||||
## What Changes
|
||||
|
||||
- IoT 卡管理新增 `authorized_enterprise_id` 和 `is_authorized_to_enterprise` 查询过滤。
|
||||
- IoT 卡管理在导出按钮左侧新增“授权卡给企业”和“回收卡授权”按钮，并为两个按钮添加独立权限编码。
|
||||
- 设备管理新增 `authorized_enterprise_id` 和 `is_authorized_to_enterprise` 查询过滤。
|
||||
- 设备管理在导出按钮左侧新增“授权设备给企业”和“撤销设备授权”按钮，并为两个按钮添加独立权限编码。
|
||||
- 新列表按钮复用 `docs/授权、回收.md` 中的授权/回收接口，支持列表选择和筛选条件批量操作。
|
||||
- 企业客户管理移除“卡授权”和“设备授权”操作入口。
|
||||
- 删除已被替代的“企业卡管理”和“企业设备列表”两个旧页面，以及对应隐藏路由和路由别名。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `iot-card-management`, `device-management`, `enterprise-customer-management`
|
||||
- Affected code:
|
||||
- `src/views/asset-management/iot-card-management/index.vue`
|
||||
- `src/views/asset-management/device-list/index.vue`
|
||||
- `src/views/account-management/enterprise-customer/index.vue`
|
||||
- `src/api/modules/enterprise.ts`
|
||||
- `src/types/api/card.ts`
|
||||
- `src/types/api/device.ts`
|
||||
- `src/types/api/enterpriseCard.ts`
|
||||
- `src/types/api/enterpriseDevice.ts`
|
||||
- `src/router/routesAlias.ts`
|
||||
- `src/router/routes/asyncRoutes.ts`
|
||||
- `src/views/asset-management/enterprise-cards/index.vue`（删除）
|
||||
- `src/views/asset-management/enterprise-devices/index.vue`（删除）
|
||||
|
||||
## Dependencies
|
||||
|
||||
- Backend list APIs accept `authorized_enterprise_id` and `is_authorized_to_enterprise` as query parameters.
|
||||
- Backend authorization APIs are described in `docs/授权、回收.md`.
|
||||
- Existing enterprise list/search API can provide target enterprise options for the new dialogs.
|
||||
@@ -0,0 +1,83 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Device Enterprise Authorization Filters
|
||||
|
||||
The device management page SHALL support filtering devices by effective enterprise authorization.
|
||||
|
||||
#### Scenario: Filter devices by authorized enterprise ID
|
||||
|
||||
- **GIVEN** 用户在设备管理搜索栏选择或输入企业 ID
|
||||
- **WHEN** 用户执行搜索
|
||||
- **THEN** 系统 MUST send `authorized_enterprise_id` to the device list API
|
||||
- **AND** the list MUST only show devices currently authorized to that enterprise according to the backend response
|
||||
|
||||
#### Scenario: Filter devices by enterprise authorization status
|
||||
|
||||
- **GIVEN** 用户在设备管理搜索栏选择企业授权状态
|
||||
- **WHEN** 用户选择“已授权”并搜索
|
||||
- **THEN** 系统 MUST send `is_authorized_to_enterprise=true`
|
||||
- **WHEN** 用户选择“未授权”并搜索
|
||||
- **THEN** 系统 MUST send `is_authorized_to_enterprise=false`
|
||||
- **AND** clearing the filter MUST omit `is_authorized_to_enterprise` from the request
|
||||
|
||||
### Requirement: Device Enterprise Authorization Actions
|
||||
|
||||
The device management page SHALL provide enterprise device authorization actions directly in the table header before the export button.
|
||||
|
||||
#### Scenario: Show permission-controlled device authorization buttons
|
||||
|
||||
- **GIVEN** 用户访问设备管理页面
|
||||
- **WHEN** the table header renders
|
||||
- **THEN** the “授权设备给企业” button MUST appear to the left of the “导出” button only when the user has permission `devices:authorize_enterprise`
|
||||
- **AND** the “撤销设备授权” button MUST appear to the left of the “导出” button only when the user has permission `devices:recall_enterprise_authorization`
|
||||
|
||||
#### Scenario: Authorize selected devices to an enterprise
|
||||
|
||||
- **GIVEN** 用户在设备管理列表选中了设备
|
||||
- **WHEN** 用户点击“授权设备给企业”并选择目标企业
|
||||
- **AND** 用户选择 `list` 选取方式
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/allocate-devices`
|
||||
- **AND** the request body MUST include `selection_type: 'list'`
|
||||
- **AND** the request body MUST include selected row device identifiers as `device_nos`
|
||||
- **AND** identifiers MUST come from list response fields such as `virtual_no` when available
|
||||
- **AND** the UI MUST display success count, fail count, authorized devices, and failed item reasons from the response
|
||||
- **AND** the device list MUST refresh after any successful authorization
|
||||
|
||||
#### Scenario: Authorize devices by filters
|
||||
|
||||
- **GIVEN** 用户打开“授权设备给企业” dialog
|
||||
- **WHEN** 用户选择 `filter` 选取方式并确认
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/allocate-devices`
|
||||
- **AND** the request body MUST include `selection_type: 'filter'`
|
||||
- **AND** filter fields MUST be populated from the dialog filter form or current list filters when applicable, including available values such as `batch_no`, `shop_id`, and `virtual_no`
|
||||
- **AND** empty filter fields MUST be omitted
|
||||
|
||||
#### Scenario: Authorize devices filter selects shop from cascade tree
|
||||
|
||||
- **GIVEN** 用户在“授权设备给企业” dialog 中选择 `filter` 选取方式
|
||||
- **WHEN** the shop filter field renders
|
||||
- **THEN** the field MUST use the same lazy cascade tree pattern as the “上级店铺” field in the add-shop dialog
|
||||
- **AND** it MUST load children through `ShopService.getShopsCascade({ parent_id })`
|
||||
- **AND** it MUST allow selecting any level with `checkStrictly: true`
|
||||
- **AND** when submitted, the request MUST use the last selected cascade node ID as `shop_id`
|
||||
- **AND** clearing the cascade field MUST omit `shop_id`
|
||||
|
||||
#### Scenario: Recall selected device authorization
|
||||
|
||||
- **GIVEN** 用户在设备管理列表选中了 currently enterprise-authorized devices
|
||||
- **WHEN** 用户点击“撤销设备授权”
|
||||
- **THEN** the UI MUST require a source enterprise ID unless it can safely infer one from `authorized_enterprise_id` or selected row data returned by the list API
|
||||
- **WHEN** 用户 confirms `list` recall
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/recall-devices`
|
||||
- **AND** the request body MUST include `selection_type: 'list'` and selected row device identifiers as `device_nos`
|
||||
- **AND** the UI MUST display success count, fail count, and failed item reasons
|
||||
- **AND** the device list MUST refresh after any successful recall
|
||||
|
||||
#### Scenario: Recall device authorization by filters
|
||||
|
||||
- **GIVEN** 用户打开“撤销设备授权” dialog
|
||||
- **WHEN** 用户选择 `filter` selection mode and confirms
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/recall-devices`
|
||||
- **AND** the request body MUST include `selection_type: 'filter'`
|
||||
- **AND** filter fields MUST follow the contract in `docs/授权、回收.md`, including available values such as `batch_no` and `virtual_no`
|
||||
- **AND** empty filter fields MUST be omitted
|
||||
@@ -0,0 +1,22 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Enterprise Customer Asset Authorization Entry Removal
|
||||
|
||||
The enterprise customer management page SHALL NOT provide enterprise card or device authorization entry points, and the replaced “企业卡管理” and “企业设备列表” pages SHALL be removed because these operations move to the IoT card management and device management list pages.
|
||||
|
||||
#### Scenario: Enterprise customer action column no longer shows asset authorization
|
||||
|
||||
- **GIVEN** 用户访问企业客户管理页面
|
||||
- **WHEN** the action column renders for an enterprise customer row
|
||||
- **THEN** the UI MUST NOT show “卡授权”
|
||||
- **AND** the UI MUST NOT show “设备授权”
|
||||
|
||||
#### Scenario: Replaced enterprise asset authorization pages are removed
|
||||
|
||||
- **GIVEN** the application routes are registered
|
||||
- **WHEN** route configuration is loaded
|
||||
- **THEN** `/asset-management/enterprise-cards` MUST NOT be registered
|
||||
- **AND** `/asset-management/enterprise-devices` MUST NOT be registered
|
||||
- **AND** route aliases for `EnterpriseCards` and `EnterpriseDevices` MUST NOT remain
|
||||
- **AND** `src/views/asset-management/enterprise-cards/index.vue` MUST be deleted
|
||||
- **AND** `src/views/asset-management/enterprise-devices/index.vue` MUST be deleted
|
||||
@@ -0,0 +1,88 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: IoT Card Enterprise Authorization Filters
|
||||
|
||||
The IoT card management page SHALL support filtering standalone cards by effective enterprise authorization.
|
||||
|
||||
#### Scenario: Filter cards by authorized enterprise ID
|
||||
|
||||
- **GIVEN** 用户在 IoT 卡管理搜索栏选择或输入企业 ID
|
||||
- **WHEN** 用户执行搜索
|
||||
- **THEN** 系统 MUST send `authorized_enterprise_id` to the IoT card list API
|
||||
- **AND** the list MUST only show cards currently authorized to that enterprise according to the backend response
|
||||
|
||||
#### Scenario: Filter cards by enterprise authorization status
|
||||
|
||||
- **GIVEN** 用户在 IoT 卡管理搜索栏选择企业授权状态
|
||||
- **WHEN** 用户选择“已授权”并搜索
|
||||
- **THEN** 系统 MUST send `is_authorized_to_enterprise=true`
|
||||
- **WHEN** 用户选择“未授权”并搜索
|
||||
- **THEN** 系统 MUST send `is_authorized_to_enterprise=false`
|
||||
- **AND** clearing the filter MUST omit `is_authorized_to_enterprise` from the request
|
||||
|
||||
### Requirement: IoT Card Enterprise Authorization Actions
|
||||
|
||||
The IoT card management page SHALL provide enterprise card authorization actions directly in the table header before the export button.
|
||||
|
||||
#### Scenario: Show permission-controlled card authorization buttons
|
||||
|
||||
- **GIVEN** 用户访问 IoT 卡管理页面
|
||||
- **WHEN** the table header renders
|
||||
- **THEN** the “授权卡给企业” button MUST appear to the left of the “导出” button only when the user has permission `iot_card:authorize_enterprise`
|
||||
- **AND** the “回收卡授权” button MUST appear to the left of the “导出” button only when the user has permission `iot_card:recall_enterprise_authorization`
|
||||
|
||||
#### Scenario: Authorize selected cards to an enterprise
|
||||
|
||||
- **GIVEN** 用户在 IoT 卡管理列表选中了卡
|
||||
- **WHEN** 用户点击“授权卡给企业”并选择目标企业
|
||||
- **AND** 用户选择 `list` 选取方式
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/allocate-cards`
|
||||
- **AND** the request body MUST include `selection_type: 'list'`
|
||||
- **AND** the request body MUST include selected row ICCIDs as `iccids`
|
||||
- **AND** the UI MUST display success count, fail count, and failed item reasons from the response
|
||||
- **AND** the card list MUST refresh after any successful authorization
|
||||
|
||||
#### Scenario: Authorize cards by range
|
||||
|
||||
- **GIVEN** 用户打开“授权卡给企业” dialog
|
||||
- **WHEN** 用户选择 `range` 选取方式并填写起始和结束 ICCID
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/allocate-cards`
|
||||
- **AND** the request body MUST include `selection_type: 'range'`, `iccid_start`, `iccid_end`, and optional `remark`
|
||||
|
||||
#### Scenario: Authorize cards by filters
|
||||
|
||||
- **GIVEN** 用户打开“授权卡给企业” dialog
|
||||
- **WHEN** 用户选择 `filter` 选取方式并确认
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/allocate-cards`
|
||||
- **AND** the request body MUST include `selection_type: 'filter'`
|
||||
- **AND** filter fields MUST be populated from the dialog filter form or current list filters when applicable, including available values such as `carrier_id`, `shop_id`, `shop_ids`, `batch_no`, and `iccid`
|
||||
- **AND** empty filter fields MUST be omitted
|
||||
|
||||
#### Scenario: Authorize cards filter selects shop from cascade tree
|
||||
|
||||
- **GIVEN** 用户在“授权卡给企业” dialog 中选择 `filter` 选取方式
|
||||
- **WHEN** the shop filter field renders
|
||||
- **THEN** the field MUST use the same lazy cascade tree pattern as the “上级店铺” field in the add-shop dialog
|
||||
- **AND** it MUST load children through `ShopService.getShopsCascade({ parent_id })`
|
||||
- **AND** it MUST allow selecting any level with `checkStrictly: true`
|
||||
- **AND** when submitted, the request MUST use the last selected cascade node ID as `shop_id`
|
||||
- **AND** clearing the cascade field MUST omit `shop_id`
|
||||
|
||||
#### Scenario: Recall selected card authorization
|
||||
|
||||
- **GIVEN** 用户在 IoT 卡管理列表选中了 currently enterprise-authorized cards
|
||||
- **WHEN** 用户点击“回收卡授权”
|
||||
- **THEN** the UI MUST require a source enterprise ID unless it can safely infer one from `authorized_enterprise_id` or selected row data returned by the list API
|
||||
- **WHEN** 用户 confirms `list` recall
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/recall-cards`
|
||||
- **AND** the request body MUST include `selection_type: 'list'` and selected row ICCIDs as `iccids`
|
||||
- **AND** the UI MUST display success count, fail count, failed item reasons, and any `recalled_devices`
|
||||
- **AND** the card list MUST refresh after any successful recall
|
||||
|
||||
#### Scenario: Recall card authorization by range or filters
|
||||
|
||||
- **GIVEN** 用户打开“回收卡授权” dialog
|
||||
- **WHEN** 用户选择 `range` or `filter` selection mode and confirms
|
||||
- **THEN** 系统 MUST call `POST /api/admin/enterprises/{id}/recall-cards`
|
||||
- **AND** the request body MUST match the selected mode using the contract in `docs/授权、回收.md`
|
||||
- **AND** empty filter fields MUST be omitted
|
||||
@@ -0,0 +1,46 @@
|
||||
## 1. API And Types
|
||||
|
||||
- [x] 1.1 Extend IoT card list query params with `authorized_enterprise_id?: number` and `is_authorized_to_enterprise?: boolean | null`.
|
||||
- [x] 1.2 Extend device list query params with `authorized_enterprise_id?: number` and `is_authorized_to_enterprise?: boolean | null`.
|
||||
- [x] 1.3 Align enterprise card authorization request types with `selection_type: 'list' | 'range' | 'filter'`, list/range/filter fields, and optional `remark`.
|
||||
- [x] 1.4 Align enterprise device authorization request types with `selection_type: 'list' | 'filter'`, list/filter fields, and optional `remark`.
|
||||
- [x] 1.5 Keep using `EnterpriseService.allocateCards`, `recallCards`, `allocateDevices`, and `recallDevices`; update method types only if needed.
|
||||
|
||||
## 2. IoT Card Management
|
||||
|
||||
- [x] 2.1 Add enterprise authorization filters to the IoT card search form and request payload.
|
||||
- [x] 2.2 Add “授权卡给企业” before the export button with permission `iot_card:authorize_enterprise`.
|
||||
- [x] 2.3 Add “回收卡授权” before the export button with permission `iot_card:recall_enterprise_authorization`.
|
||||
- [x] 2.4 Implement card authorization dialog with target enterprise selection, selection mode, list/range/filter inputs, optional remark, validation, submit, loading state, and result display.
|
||||
- [x] 2.4.1 Update the card authorization dialog shop filter to use the same lazy shop cascade tree as the add-shop dialog “上级店铺” field, and submit the last selected node as `shop_id`.
|
||||
- [x] 2.5 Implement card recall dialog with target/source enterprise resolution, selection mode, list/range/filter inputs, optional remark, validation, submit, loading state, and result display.
|
||||
- [x] 2.6 Refresh the IoT card list after successful authorization or recall.
|
||||
|
||||
## 3. Device Management
|
||||
|
||||
- [x] 3.1 Add enterprise authorization filters to the device search form and request payload.
|
||||
- [x] 3.2 Add “授权设备给企业” before the export button with permission `devices:authorize_enterprise`.
|
||||
- [x] 3.3 Add “撤销设备授权” before the export button with permission `devices:recall_enterprise_authorization`.
|
||||
- [x] 3.4 Implement device authorization dialog with target enterprise selection, selection mode, list/filter inputs, optional remark, validation, submit, loading state, and result display.
|
||||
- [x] 3.4.1 Update the device authorization dialog shop filter to use the same lazy shop cascade tree as the add-shop dialog “上级店铺” field, and submit the last selected node as `shop_id`.
|
||||
- [x] 3.5 Implement device recall dialog with target/source enterprise resolution, selection mode, list/filter inputs, validation, submit, loading state, and result display.
|
||||
- [x] 3.6 Refresh the device list after successful authorization or recall.
|
||||
|
||||
## 4. Remove Replaced Enterprise Authorization Pages
|
||||
|
||||
- [x] 4.1 Remove “卡授权” and “设备授权” operations from the enterprise customer action column.
|
||||
- [x] 4.2 Remove navigation logic to enterprise card/device authorization pages.
|
||||
- [x] 4.3 Remove hidden routes for `/asset-management/enterprise-cards` and `/asset-management/enterprise-devices`.
|
||||
- [x] 4.4 Remove `RoutesAlias.EnterpriseCards` and `RoutesAlias.EnterpriseDevices`.
|
||||
- [x] 4.5 Delete the replaced “企业卡管理” page file `src/views/asset-management/enterprise-cards/index.vue`.
|
||||
- [x] 4.6 Delete the replaced “企业设备列表” page file `src/views/asset-management/enterprise-devices/index.vue`.
|
||||
- [x] 4.7 Verify no imports, route aliases, menu entries, or navigation calls reference the deleted pages.
|
||||
|
||||
## 5. Validation
|
||||
|
||||
- [x] 5.1 Verify IoT card list filters send correct query parameters and reset correctly.
|
||||
- [x] 5.2 Verify device list filters send correct query parameters and reset correctly.
|
||||
- [x] 5.3 Verify all four new buttons obey their permission codes.
|
||||
- [x] 5.4 Verify list/range/filter authorization and recall flows against API contracts from `docs/授权、回收.md`.
|
||||
- [x] 5.5 Run targeted ESLint for modified files.
|
||||
- [ ] 5.6 Run `openspec validate update-enterprise-asset-authorization-entry --strict` when the OpenSpec CLI is available.
|
||||
139
openspec/changes/update-exchange-flow-direct-type/design.md
Normal file
139
openspec/changes/update-exchange-flow-direct-type/design.md
Normal file
@@ -0,0 +1,139 @@
|
||||
## Context
|
||||
|
||||
现有换货管理系统仅支持物流换货流程，包含：创建 → 待填写信息 → 待发货 → 已发货 → 已完成 五个阶段。部分场景下（如现场换货、远程换货等），不需要物流环节，直接完成换货即可。
|
||||
|
||||
后端已实现直接换货类型的数据库字段和 API 接口升级，前端需要适配新的接口规范和 UI 交互。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
### Goals
|
||||
|
||||
- 支持创建直接换货单，自动完成换货流程
|
||||
- 适配后端新增的 flow_type、shipped_at、completed_at 字段
|
||||
- 根据流程类型动态控制 UI 展示和操作权限
|
||||
- 保持向后兼容，历史数据正常展示
|
||||
|
||||
### Non-Goals
|
||||
|
||||
- 不涉及客户端换货接口改造
|
||||
- 不修改换货单状态定义
|
||||
- 不改变物流换货的原有流程逻辑
|
||||
|
||||
## Decisions
|
||||
|
||||
### 1. 流程类型枚举定义
|
||||
|
||||
```typescript
|
||||
export enum ExchangeFlowType {
|
||||
SHIPPING = 'shipping', // 物流换货
|
||||
DIRECT = 'direct' // 直接换货
|
||||
}
|
||||
|
||||
export const EXCHANGE_FLOW_TYPE_MAP = {
|
||||
[ExchangeFlowType.SHIPPING]: '物流换货',
|
||||
[ExchangeFlowType.DIRECT]: '直接换货'
|
||||
}
|
||||
```
|
||||
|
||||
**Rationale**: 使用枚举统一管理流程类型，避免硬编码字符串，方便维护和扩展。
|
||||
|
||||
### 2. 创建表单的条件渲染
|
||||
|
||||
使用 `v-if` 根据选中的 flow_type 动态显示字段：
|
||||
|
||||
- flow_type = 'direct' 时，显示"新资产标识符"和"是否迁移数据"
|
||||
- flow_type = 'shipping' 时，隐藏这些字段
|
||||
|
||||
**Rationale**: 符合 Element Plus 表单最佳实践，避免不必要的字段提交。
|
||||
|
||||
**Alternatives considered**:
|
||||
|
||||
- 使用 `v-show` 隐藏：会导致隐藏字段仍参与表单验证
|
||||
- 使用动态表单项：增加复杂度，不够直观
|
||||
|
||||
### 3. 详情页按钮权限控制
|
||||
|
||||
在详情页组件中定义计算属性：
|
||||
|
||||
```typescript
|
||||
const canShip = computed(
|
||||
() => exchange.value.flow_type === 'shipping' && exchange.value.status === 2
|
||||
)
|
||||
|
||||
const canComplete = computed(
|
||||
() => exchange.value.flow_type === 'shipping' && exchange.value.status === 3
|
||||
)
|
||||
|
||||
const canCancel = computed(
|
||||
() => exchange.value.flow_type === 'shipping' && [1, 2].includes(exchange.value.status)
|
||||
)
|
||||
```
|
||||
|
||||
**Rationale**: 将权限逻辑集中在计算属性中，模板中直接使用 `v-if`，代码清晰且易于测试。
|
||||
|
||||
### 4. 信息区块隐藏策略
|
||||
|
||||
对于 direct 类型，收货信息和物流信息区块采用以下策略：
|
||||
|
||||
- **选择方案**: 使用 `v-if="exchange.flow_type === 'shipping'"` 完全隐藏
|
||||
- **原因**: direct 类型这些字段为 null，显示空白区块或"不适用"会造成页面冗余
|
||||
|
||||
**Alternatives considered**:
|
||||
|
||||
- 显示"不适用"占位：增加不必要的视觉噪音
|
||||
- 显示空区块：用户体验不佳
|
||||
|
||||
### 5. API 错误处理
|
||||
|
||||
后端对不合法操作返回 400 错误，前端需要：
|
||||
|
||||
1. 在操作按钮级别根据 flow_type 和 status 做前置检查（优先）
|
||||
2. 对后端返回的错误消息直接展示（兜底）
|
||||
|
||||
**Rationale**: 前置检查提供更好的用户体验，后端错误处理作为安全兜底。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
### Risk: 历史数据 flow_type 为空
|
||||
|
||||
**Mitigation**: 后端承诺 flow_type 为空时等同于 'shipping'，前端在渲染时做兼容处理：
|
||||
|
||||
```typescript
|
||||
const flowType = exchange.flow_type || 'shipping'
|
||||
```
|
||||
|
||||
### Trade-off: UI 复杂度增加
|
||||
|
||||
引入流程类型后，详情页的条件渲染逻辑增多。
|
||||
|
||||
**Mitigation**:
|
||||
|
||||
- 使用计算属性封装权限判断逻辑
|
||||
- 添加单元测试覆盖不同流程类型的渲染场景
|
||||
|
||||
## Migration Plan
|
||||
|
||||
### 阶段 1: API 类型升级（无破坏性）
|
||||
|
||||
- 更新 TypeScript 接口定义
|
||||
- 向后兼容，不影响现有调用
|
||||
|
||||
### 阶段 2: UI 适配（向后兼容）
|
||||
|
||||
- 列表页新增流程类型列和筛选
|
||||
- 详情页新增时间戳展示
|
||||
- 历史数据按 shipping 处理，正常显示
|
||||
|
||||
### 阶段 3: 创建功能升级（新增能力）
|
||||
|
||||
- 新增流程类型选择
|
||||
- 支持创建 direct 类型换货单
|
||||
|
||||
### 阶段 4: 测试与发布
|
||||
|
||||
- 功能测试、回归测试
|
||||
- 灰度发布，监控错误
|
||||
|
||||
## Open Questions
|
||||
|
||||
无
|
||||
@@ -0,0 +1,27 @@
|
||||
# Change: 换货流程升级 - 新增直接换货类型
|
||||
|
||||
## Why
|
||||
|
||||
现有换货流程仅支持物流换货（shipping），需要填写收货信息、发货、确认完成等多个步骤，流程较长。部分场景下需要支持直接换货（direct），即创建后立即完成，无需物流环节，提升换货效率。
|
||||
|
||||
## What Changes
|
||||
|
||||
- **新增** 换货流程类型（flow_type）字段，支持 `shipping`（物流换货）和 `direct`（直接换货）两种类型
|
||||
- **新增** 发货时间（shipped_at）和完成时间（completed_at）字段，用于记录换货流程关键时间节点
|
||||
- **修改** 创建换货单接口，支持选择流程类型和直接换货参数
|
||||
- **修改** 换货单列表接口，新增流程类型筛选和资产标识符模糊查询
|
||||
- **修改** 换货单详情接口，返回流程类型和时间戳信息
|
||||
- **修改** 发货、确认完成、取消换货接口，增加流程类型限制逻辑
|
||||
- **BREAKING** direct 类型换货单不支持发货、确认完成和取消操作
|
||||
- **BREAKING** 取消换货仅支持 shipping 流程且状态为待填写信息或待发货时
|
||||
|
||||
## Impact
|
||||
|
||||
- **Affected specs**: exchange-management（新建）
|
||||
- **Affected code**:
|
||||
- `src/api/modules/exchange.ts` - API 类型定义和接口调用
|
||||
- 换货单列表页面 - 新增流程类型列和筛选项
|
||||
- 换货单详情页面 - 根据流程类型控制按钮和信息区块显示
|
||||
- 创建换货单弹窗 - 新增流程类型选择和相关字段
|
||||
- **Database**: `tb_exchange_order` 表新增 `flow_type`、`shipped_at`、`completed_at` 字段
|
||||
- **API compatibility**: 向后兼容，历史数据 flow_type 为空时视为 shipping
|
||||
@@ -0,0 +1,199 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 换货流程类型支持
|
||||
|
||||
系统 SHALL 支持两种换货流程类型：物流换货（shipping）和直接换货（direct），用于满足不同场景下的换货需求。
|
||||
|
||||
#### Scenario: 创建物流换货单
|
||||
|
||||
- **WHEN** 用户选择"物流换货"类型创建换货单
|
||||
- **THEN** 换货单状态为"待填写信息"（status=1），flow_type 为 "shipping"
|
||||
- **AND** 需要后续填写收货信息、发货、确认完成等步骤
|
||||
|
||||
#### Scenario: 创建直接换货单
|
||||
|
||||
- **WHEN** 用户选择"直接换货"类型并填写新资产标识符创建换货单
|
||||
- **THEN** 换货单状态为"已完成"（status=4），flow_type 为 "direct"
|
||||
- **AND** completed_at 字段记录当前时间
|
||||
- **AND** 无需填写收货信息和发货流程
|
||||
|
||||
#### Scenario: 历史数据兼容
|
||||
|
||||
- **WHEN** 读取 flow_type 为空的历史换货单
|
||||
- **THEN** 系统应将其视为"物流换货"（shipping）类型
|
||||
- **AND** 按照物流换货流程展示和处理
|
||||
|
||||
### Requirement: 换货时间戳记录
|
||||
|
||||
系统 SHALL 记录换货流程中的关键时间节点，包括发货时间（shipped_at）和完成时间（completed_at）。
|
||||
|
||||
#### Scenario: 物流换货发货时间记录
|
||||
|
||||
- **WHEN** 物流换货单执行发货操作
|
||||
- **THEN** shipped_at 字段记录发货时间
|
||||
- **AND** 换货单状态变更为"已发货"（status=3）
|
||||
|
||||
#### Scenario: 物流换货完成时间记录
|
||||
|
||||
- **WHEN** 物流换货单确认完成
|
||||
- **THEN** completed_at 字段记录完成时间
|
||||
- **AND** 换货单状态变更为"已完成"（status=4）
|
||||
|
||||
#### Scenario: 直接换货完成时间记录
|
||||
|
||||
- **WHEN** 创建直接换货单
|
||||
- **THEN** completed_at 字段立即记录创建时间
|
||||
- **AND** shipped_at 字段为 null（无发货环节）
|
||||
|
||||
### Requirement: 创建换货单流程类型选择
|
||||
|
||||
用户在创建换货单时 SHALL 能够选择换货流程类型，并根据选择的类型填写相应的必填字段。
|
||||
|
||||
#### Scenario: 选择直接换货时必填新资产标识符
|
||||
|
||||
- **WHEN** 用户选择"直接换货"类型
|
||||
- **THEN** 表单必须显示"新资产标识符"输入框（必填）
|
||||
- **AND** 必须显示"是否迁移数据"开关（可选，默认 false）
|
||||
|
||||
#### Scenario: 选择物流换货时隐藏直接换货字段
|
||||
|
||||
- **WHEN** 用户选择"物流换货"类型
|
||||
- **THEN** 表单不显示"新资产标识符"和"是否迁移数据"字段
|
||||
- **AND** 仅需填写换货原因、旧资产类型和旧资产标识符
|
||||
|
||||
#### Scenario: 提交直接换货单参数
|
||||
|
||||
- **WHEN** 用户提交直接换货单
|
||||
- **THEN** 请求参数 MUST 包含 flow_type="direct"、new_identifier 和 migrate_data
|
||||
- **AND** 后端返回状态为"已完成"的换货单
|
||||
|
||||
### Requirement: 换货单列表流程类型筛选
|
||||
|
||||
用户在换货单列表页 SHALL 能够按流程类型筛选换货单，并查看流程类型信息。
|
||||
|
||||
#### Scenario: 显示流程类型列
|
||||
|
||||
- **WHEN** 用户查看换货单列表
|
||||
- **THEN** 列表 MUST 显示"流程类型"列
|
||||
- **AND** 该列显示"物流换货"或"直接换货"
|
||||
|
||||
#### Scenario: 按流程类型筛选
|
||||
|
||||
- **WHEN** 用户在筛选区选择流程类型（全部/物流换货/直接换货）
|
||||
- **THEN** 列表仅显示选中类型的换货单
|
||||
- **AND** 查询参数 flow_type 传递对应值（shipping/direct）
|
||||
|
||||
#### Scenario: 资产标识符模糊查询
|
||||
|
||||
- **WHEN** 用户输入资产标识符进行搜索
|
||||
- **THEN** 系统同时匹配旧资产标识符和新资产标识符
|
||||
- **AND** 返回所有匹配的换货单
|
||||
|
||||
### Requirement: 换货单详情流程类型展示
|
||||
|
||||
换货单详情页 SHALL 根据流程类型动态展示相关信息和时间戳。
|
||||
|
||||
#### Scenario: 显示流程类型和时间戳
|
||||
|
||||
- **WHEN** 用户查看换货单详情
|
||||
- **THEN** 详情页 MUST 显示"流程类型"字段（物流换货/直接换货）
|
||||
- **AND** 对于物流换货，显示"发货时间"（shipped_at，已发货后有值）
|
||||
- **AND** 对于所有已完成的换货单，显示"完成时间"（completed_at）
|
||||
|
||||
#### Scenario: 直接换货隐藏收货和物流信息
|
||||
|
||||
- **WHEN** 用户查看直接换货单详情
|
||||
- **THEN** 详情页不显示"收货信息"区块
|
||||
- **AND** 详情页不显示"物流信息"区块
|
||||
|
||||
#### Scenario: 物流换货正常显示所有信息
|
||||
|
||||
- **WHEN** 用户查看物流换货单详情
|
||||
- **THEN** 详情页显示"收货信息"区块（填写后有值）
|
||||
- **AND** 详情页显示"物流信息"区块（发货后有值）
|
||||
|
||||
## MODIFIED Requirements
|
||||
|
||||
### Requirement: 换货单发货操作限制
|
||||
|
||||
系统 SHALL 仅允许物流换货单执行发货操作，直接换货单不支持发货。
|
||||
|
||||
**原有行为**: 所有状态为"待发货"的换货单均可执行发货操作。
|
||||
|
||||
**新行为**: 仅 flow_type="shipping" 且 status=2（待发货）的换货单可执行发货操作。
|
||||
|
||||
#### Scenario: 物流换货单可以发货
|
||||
|
||||
- **WHEN** 换货单 flow_type="shipping" 且 status=2
|
||||
- **THEN** 详情页显示"发货"按钮
|
||||
- **AND** 用户可以填写快递公司、快递单号等信息并提交
|
||||
|
||||
#### Scenario: 直接换货单不可发货
|
||||
|
||||
- **WHEN** 换货单 flow_type="direct"
|
||||
- **THEN** 详情页不显示"发货"按钮
|
||||
- **AND** 如果前端误调用发货接口，后端返回 400 错误："流程类型不支持该操作"
|
||||
|
||||
#### Scenario: 前端阻止不合法发货操作
|
||||
|
||||
- **WHEN** 详情页加载换货单数据
|
||||
- **THEN** 前端根据 flow_type 和 status 判断是否显示"发货"按钮
|
||||
- **AND** 仅在 flow_type="shipping" 且 status=2 时显示
|
||||
|
||||
### Requirement: 换货单确认完成操作限制
|
||||
|
||||
系统 SHALL 仅允许物流换货单在已发货状态下执行确认完成操作，直接换货单自动完成。
|
||||
|
||||
**原有行为**: 状态为"已发货"的换货单可执行确认完成操作。
|
||||
|
||||
**新行为**: 仅 flow_type="shipping" 且 status=3（已发货）的换货单可执行确认完成操作。
|
||||
|
||||
#### Scenario: 物流换货单可以确认完成
|
||||
|
||||
- **WHEN** 换货单 flow_type="shipping" 且 status=3
|
||||
- **THEN** 详情页显示"确认完成"按钮
|
||||
- **AND** 用户点击后换货单状态变更为"已完成"
|
||||
|
||||
#### Scenario: 直接换货单不可确认完成
|
||||
|
||||
- **WHEN** 换货单 flow_type="direct"
|
||||
- **THEN** 详情页不显示"确认完成"按钮
|
||||
- **AND** 如果前端误调用完成接口，后端返回 400 错误
|
||||
|
||||
#### Scenario: 前端阻止不合法完成操作
|
||||
|
||||
- **WHEN** 详情页加载换货单数据
|
||||
- **THEN** 前端根据 flow_type 和 status 判断是否显示"确认完成"按钮
|
||||
- **AND** 仅在 flow_type="shipping" 且 status=3 时显示
|
||||
|
||||
### Requirement: 换货单取消操作限制
|
||||
|
||||
系统 SHALL 仅允许物流换货单在待填写信息或待发货状态下取消，直接换货单和已发货的物流换货单不可取消。
|
||||
|
||||
**原有行为**: 状态为"待填写信息"或"待发货"的换货单可取消。
|
||||
|
||||
**新行为**: 仅 flow_type="shipping" 且 status IN (1, 2) 的换货单可取消。
|
||||
|
||||
#### Scenario: 物流换货单待发货前可取消
|
||||
|
||||
- **WHEN** 换货单 flow_type="shipping" 且 status=1 或 status=2
|
||||
- **THEN** 详情页显示"取消"按钮
|
||||
- **AND** 用户可以取消换货单
|
||||
|
||||
#### Scenario: 物流换货单已发货后不可取消
|
||||
|
||||
- **WHEN** 换货单 flow_type="shipping" 且 status=3
|
||||
- **THEN** 详情页不显示"取消"按钮
|
||||
- **AND** 如果前端误调用取消接口，后端返回错误
|
||||
|
||||
#### Scenario: 直接换货单不可取消
|
||||
|
||||
- **WHEN** 换货单 flow_type="direct"
|
||||
- **THEN** 详情页不显示"取消"按钮
|
||||
- **AND** 如果前端误调用取消接口，后端返回 400 错误："流程类型不支持该操作"
|
||||
|
||||
#### Scenario: 前端阻止不合法取消操作
|
||||
|
||||
- **WHEN** 详情页加载换货单数据
|
||||
- **THEN** 前端根据 flow_type 和 status 判断是否显示"取消"按钮
|
||||
- **AND** 仅在 flow_type="shipping" 且 status IN (1, 2) 时显示
|
||||
55
openspec/changes/update-exchange-flow-direct-type/tasks.md
Normal file
55
openspec/changes/update-exchange-flow-direct-type/tasks.md
Normal file
@@ -0,0 +1,55 @@
|
||||
## 1. API 类型定义更新
|
||||
|
||||
- [x] 1.1 更新 `ExchangeQueryParams` 接口，新增 `flow_type` 和 `identifier` 查询参数
|
||||
- [x] 1.2 更新 `CreateExchangeRequest` 接口，新增 `flow_type`、`new_identifier`、`migrate_data` 字段
|
||||
- [x] 1.3 更新 `ExchangeResponse` 接口，新增 `flow_type`、`flow_type_name`、`shipped_at`、`completed_at` 字段
|
||||
|
||||
## 2. 创建换货单功能
|
||||
|
||||
- [x] 2.1 更新创建换货单弹窗，新增流程类型选择器（单选：物流换货/直接换货）
|
||||
- [x] 2.2 实现流程类型切换逻辑，direct 时显示新资产标识符和数据迁移开关
|
||||
- [x] 2.3 更新表单验证规则，direct 时 new_identifier 必填
|
||||
- [x] 2.4 更新 API 调用，传递完整的创建参数
|
||||
|
||||
## 3. 换货单列表功能
|
||||
|
||||
- [x] 3.1 新增流程类型列，显示"物流换货"或"直接换货"
|
||||
- [x] 3.2 新增流程类型筛选下拉框（全部/物流换货/直接换货）
|
||||
- [x] 3.3 更新资产标识符搜索为模糊查询（同时匹配旧资产和新资产）
|
||||
- [x] 3.4 更新列表查询参数，支持 flow_type 和 identifier 筛选
|
||||
|
||||
## 4. 换货单详情功能
|
||||
|
||||
- [x] 4.1 新增流程类型展示字段（flow_type_name）
|
||||
- [x] 4.2 新增发货时间（shipped_at）和完成时间（completed_at）展示
|
||||
- [x] 4.3 根据 flow_type 控制操作按钮显示：
|
||||
- direct 类型隐藏"发货"、"确认完成"、"取消"按钮
|
||||
- shipping + status=1 仅显示"取消"
|
||||
- shipping + status=2 显示"发货"和"取消"
|
||||
- shipping + status=3 仅显示"确认完成"
|
||||
- [x] 4.4 根据 flow_type 控制信息区块显示：
|
||||
- direct 类型隐藏或标记"不适用"收货信息和物流信息区块
|
||||
|
||||
## 5. 发货功能
|
||||
|
||||
- [x] 5.1 在发货前检查 flow_type，仅允许 shipping 类型
|
||||
- [x] 5.2 对 direct 类型返回的 400 错误进行友好提示
|
||||
|
||||
## 6. 确认完成功能
|
||||
|
||||
- [x] 6.1 在确认完成前检查 flow_type，仅允许 shipping 且 status=3
|
||||
- [x] 6.2 对 direct 类型返回的错误进行友好提示
|
||||
|
||||
## 7. 取消换货功能
|
||||
|
||||
- [x] 7.1 在取消前检查 flow_type 和 status，仅允许 shipping 且 status 为 1 或 2
|
||||
- [x] 7.2 对不符合条件的操作返回友好提示
|
||||
|
||||
## 8. 测试与验证
|
||||
|
||||
- [ ] 8.1 测试创建物流换货单，验证原有流程正常
|
||||
- [ ] 8.2 测试创建直接换货单，验证自动完成逻辑
|
||||
- [ ] 8.3 测试列表筛选，验证 flow_type 和 identifier 查询正确
|
||||
- [ ] 8.4 测试详情页按钮和区块显示，验证不同流程类型的 UI 差异
|
||||
- [ ] 8.5 测试操作限制，验证 direct 类型不可发货、完成、取消
|
||||
- [ ] 8.6 测试历史数据兼容性，验证 flow_type 为空时视为 shipping
|
||||
67
openspec/changes/update-export-task-scene-pages/design.md
Normal file
67
openspec/changes/update-export-task-scene-pages/design.md
Normal file
@@ -0,0 +1,67 @@
|
||||
## Context
|
||||
|
||||
导出任务能力已经具备统一 API、通用列表页面、详情页面和创建弹窗。现有列表页面通过 `scene` 搜索项区分设备、IOT 卡和订单任务，但新的产品方案要求用三个固定场景页面替代该筛选方式，并让三个页面按钮权限相互独立。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: 在导出管理下提供“导出设备”“导出IOT卡”“导出订单”三个页面。
|
||||
- Goals: 三个页面固定传入各自 `scene`，去掉页面中的“导出场景”筛选。
|
||||
- Goals: 三个页面及其按钮/操作使用场景级独立权限编码。
|
||||
- Goals: 尽量复用现有导出任务列表和详情实现，避免复制三份完整页面逻辑。
|
||||
- Non-Goals: 不新增导出任务后端 API。
|
||||
- Non-Goals: 不改变创建导出任务的 `scene` 值和 `query` 快照语义。
|
||||
- Non-Goals: 不调整导出任务状态流转、文件生成或下载地址生成逻辑。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 使用一个可复用导出任务列表实现，通过路由配置或组件 props 注入固定场景、页面标题和权限映射。
|
||||
- Rationale: 三个页面除固定 `scene` 和权限外，分页、状态筛选、时间筛选、下载、取消逻辑一致，复用可以减少重复代码和后续维护成本。
|
||||
|
||||
- Decision: 页面查询参数由页面固定注入 `scene`，不从搜索表单读取“导出场景”。
|
||||
- Rationale: 页面已经按场景拆分，继续暴露场景筛选会造成入口语义冲突，也可能让用户在“导出设备”页面查到 IOT 卡或订单任务。
|
||||
|
||||
- Decision: 权限编码按场景和操作拆分，默认建议如下。
|
||||
- Rationale: 用户明确要求三个界面的按钮权限编码不同；列表访问、详情、下载、取消均需要避免跨场景复用。
|
||||
|
||||
| 场景 | 页面访问 | 详情 | 下载 | 取消 |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| 导出设备 | `export_task:device:list` | `export_task:device:detail` | `export_task:device:download` | `export_task:device:cancel` |
|
||||
| 导出IOT卡 | `export_task:iot_card:list` | `export_task:iot_card:detail` | `export_task:iot_card:download` | `export_task:iot_card:cancel` |
|
||||
| 导出订单 | `export_task:order:list` | `export_task:order:detail` | `export_task:order:download` | `export_task:order:cancel` |
|
||||
|
||||
- Decision: 业务列表创建导出任务按钮继续使用来源业务权限，默认建议如下。
|
||||
- Rationale: 创建导出任务属于来源业务列表能力，不应因为拥有某个导出任务管理页面权限就获得业务列表导出入口。
|
||||
|
||||
| 入口 | 创建导出任务权限 | scene |
|
||||
| --- | --- | --- |
|
||||
| 设备管理 | `devices:export` | `device` |
|
||||
| IOT 卡管理 | `iot_card:export` | `iot_card` |
|
||||
| 订单列表 | `orders:export` | `order` |
|
||||
|
||||
- Decision: 详情页可继续复用同一组件，但必须根据任务场景或来源页面使用对应场景的详情、下载、取消权限。
|
||||
- Rationale: 详情页面本身也包含下载和取消按钮，若继续使用通用权限会绕过三个列表页面的按钮隔离要求。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- Risk: 后端或权限配置已经发放了通用 `export_task:*` 权限，切换为场景级权限后用户可能暂时看不到页面或按钮。
|
||||
- Mitigation: 实施时同步更新权限种子/菜单配置，并在上线前完成角色权限迁移或重新授权。
|
||||
|
||||
- Risk: 订单导出场景提案正在独立推进，可能继续给旧“导出列表”增加订单筛选。
|
||||
- Mitigation: 实施本变更前先合并范围，保留 `scene=order` 和订单创建入口，移除旧列表中的订单场景筛选实现。
|
||||
|
||||
- Risk: 详情页直接通过 URL 打开时缺少来源页面上下文。
|
||||
- Mitigation: 详情页读取任务详情后按返回的 `scene` 计算对应权限，缺少该场景详情权限时展示无权限提示并阻止后续按钮操作。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 增加三条导出任务列表路由和菜单项，删除或隐藏旧通用“导出列表”入口。
|
||||
2. 将导出任务列表改造成固定场景列表，移除“导出场景”搜索项和冗余场景列。
|
||||
3. 为三页分别注入固定 `scene`、标题和场景级权限映射。
|
||||
4. 调整导出任务详情页和行操作的权限判断，改用任务场景对应权限。
|
||||
5. 同步订单导出入口，确保订单导出任务进入“导出订单”页面查看。
|
||||
6. 更新后端/菜单权限配置并完成角色授权迁移。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 最终权限编码是否采用本设计建议，还是需要对齐后端已有权限命名规范。
|
||||
- 旧通用导出列表路由是否直接移除，还是短期隐藏并重定向到用户有权限的第一个场景页面。
|
||||
39
openspec/changes/update-export-task-scene-pages/proposal.md
Normal file
39
openspec/changes/update-export-task-scene-pages/proposal.md
Normal file
@@ -0,0 +1,39 @@
|
||||
# Change: 拆分导出任务列表为固定场景页面
|
||||
|
||||
## Why
|
||||
|
||||
当前导出管理只有一个“导出列表”页面，需要用户通过“导出场景”筛选设备、IOT 卡和订单导出任务。产品希望把该页面拆成三个固定场景页面，入口更直接，并且三个页面及页面按钮使用不同权限编码。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 将导出管理下的单个“导出列表”替换为三个页面：
|
||||
- 导出设备
|
||||
- 导出IOT卡
|
||||
- 导出订单
|
||||
- 三个页面分别固定查询 `scene=device`、`scene=iot_card`、`scene=order`，页面内不再展示或提交用户可选的“导出场景”筛选项。
|
||||
- 导出列表中的“场景”列可移除或默认不展示，因为页面本身已经代表固定场景。
|
||||
- 三个页面的菜单访问、详情、下载、取消等按钮/操作均使用场景级独立权限编码，不再复用同一组通用导出任务按钮权限。
|
||||
- 业务列表发起导出的按钮权限继续按来源业务隔离：设备导出、IOT 卡导出、订单导出使用不同权限编码。
|
||||
- 订单导出任务仍使用 `scene=order`，并与现有订单导出场景提案合并实施或调整其导出列表筛选相关内容。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `export-task-management`
|
||||
- Affected code:
|
||||
- `src/router/routesAlias.ts`
|
||||
- `src/router/routes/asyncRoutes.ts`
|
||||
- `src/views/asset-management/export-task-management/export-task-list/index.vue`
|
||||
- `src/views/asset-management/export-task-management/export-task-detail/index.vue`
|
||||
- `src/types/api/exportTask.ts`
|
||||
- `src/components/business/ExportTaskCreateDialog.vue`
|
||||
- `src/views/asset-management/device-list/index.vue`
|
||||
- `src/views/asset-management/iot-card-management/index.vue`
|
||||
- `src/views/order-management/order-list/index.vue`
|
||||
- 菜单、权限和国际化文案配置
|
||||
- Dependencies:
|
||||
- 后端导出任务列表接口继续支持 `scene=device`、`scene=iot_card`、`scene=order` 过滤。
|
||||
- 后端/权限配置需要提供三套场景级导出任务权限编码。
|
||||
- 现有 `add-order-export-scene` 提案与本提案存在重叠：其“在导出列表场景筛选中新增订单”应被本提案的三个固定页面方案替代。
|
||||
- Breaking changes:
|
||||
- 原通用“导出列表”菜单入口和 `export_task:list/detail/download/cancel` 这组通用页面操作权限将被场景级页面/按钮权限取代。
|
||||
@@ -0,0 +1,111 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Scene-Specific Export Task Pages
|
||||
|
||||
The admin frontend SHALL replace the single generic export task list entry with three scene-specific export task pages: 导出设备, 导出IOT卡, and 导出订单.
|
||||
|
||||
#### Scenario: Render scene-specific export task navigation
|
||||
|
||||
- **GIVEN** 用户打开资产管理下的导出管理菜单
|
||||
- **WHEN** 系统渲染导出任务导航
|
||||
- **THEN** 系统 MUST provide separate entries for 导出设备, 导出IOT卡, and 导出订单
|
||||
- **AND** 系统 MUST NOT expose the old generic 导出列表 menu entry as the primary navigation entry
|
||||
|
||||
#### Scenario: Query device export tasks
|
||||
|
||||
- **GIVEN** 用户打开导出设备页面
|
||||
- **WHEN** 页面查询导出任务列表
|
||||
- **THEN** 系统 MUST call `GET /api/admin/export-tasks` with `scene=device`
|
||||
- **AND** 用户 MUST NOT be able to change this page to query `iot_card` or `order` tasks through a scene selector
|
||||
|
||||
#### Scenario: Query IOT card export tasks
|
||||
|
||||
- **GIVEN** 用户打开导出IOT卡页面
|
||||
- **WHEN** 页面查询导出任务列表
|
||||
- **THEN** 系统 MUST call `GET /api/admin/export-tasks` with `scene=iot_card`
|
||||
- **AND** 用户 MUST NOT be able to change this page to query `device` or `order` tasks through a scene selector
|
||||
|
||||
#### Scenario: Query order export tasks
|
||||
|
||||
- **GIVEN** 用户打开导出订单页面
|
||||
- **WHEN** 页面查询导出任务列表
|
||||
- **THEN** 系统 MUST call `GET /api/admin/export-tasks` with `scene=order`
|
||||
- **AND** 用户 MUST NOT be able to change this page to query `device` or `iot_card` tasks through a scene selector
|
||||
|
||||
### Requirement: Remove Export Scene Filtering From Scene Pages
|
||||
|
||||
Scene-specific export task pages SHALL remove user-facing export scene filtering because each page has exactly one fixed scene.
|
||||
|
||||
#### Scenario: Hide scene search field
|
||||
|
||||
- **GIVEN** 用户打开任一导出任务场景页面
|
||||
- **WHEN** 页面渲染搜索表单
|
||||
- **THEN** 页面 MUST NOT display a 导出场景 search item
|
||||
- **AND** reset and search actions MUST keep the page's fixed `scene` unchanged
|
||||
|
||||
#### Scenario: Avoid redundant scene column
|
||||
|
||||
- **GIVEN** 用户打开任一导出任务场景页面
|
||||
- **WHEN** 页面渲染任务表格
|
||||
- **THEN** 页面 SHOULD remove or hide the 场景 column by default
|
||||
- **AND** 页面 MUST continue to display task number, status, progress, format, row counts, shard progress, error message, and created time
|
||||
|
||||
### Requirement: Scene-Specific Export Task Permissions
|
||||
|
||||
The admin frontend MUST gate each export task page and page action with scene-specific permission codes so that device, IOT card, and order export task permissions are independent.
|
||||
|
||||
#### Scenario: Gate scene pages independently
|
||||
|
||||
- **GIVEN** 用户 only has `export_task:device:list`
|
||||
- **WHEN** 系统渲染导出管理菜单
|
||||
- **THEN** 系统 MUST show 导出设备
|
||||
- **AND** 系统 MUST NOT show 导出IOT卡 or 导出订单 unless the user also has `export_task:iot_card:list` or `export_task:order:list`
|
||||
|
||||
#### Scenario: Gate device export task actions independently
|
||||
|
||||
- **GIVEN** 用户打开导出设备页面
|
||||
- **WHEN** 页面渲染详情、下载 or 取消操作
|
||||
- **THEN** 系统 MUST use `export_task:device:detail`, `export_task:device:download`, and `export_task:device:cancel` respectively
|
||||
- **AND** 系统 MUST NOT treat IOT card or order export task action permissions as sufficient for device actions
|
||||
|
||||
#### Scenario: Gate IOT card export task actions independently
|
||||
|
||||
- **GIVEN** 用户打开导出IOT卡页面
|
||||
- **WHEN** 页面渲染详情、下载 or 取消操作
|
||||
- **THEN** 系统 MUST use `export_task:iot_card:detail`, `export_task:iot_card:download`, and `export_task:iot_card:cancel` respectively
|
||||
- **AND** 系统 MUST NOT treat device or order export task action permissions as sufficient for IOT card actions
|
||||
|
||||
#### Scenario: Gate order export task actions independently
|
||||
|
||||
- **GIVEN** 用户打开导出订单页面
|
||||
- **WHEN** 页面渲染详情、下载 or 取消操作
|
||||
- **THEN** 系统 MUST use `export_task:order:detail`, `export_task:order:download`, and `export_task:order:cancel` respectively
|
||||
- **AND** 系统 MUST NOT treat device or IOT card export task action permissions as sufficient for order actions
|
||||
|
||||
#### Scenario: Keep business export buttons independent
|
||||
|
||||
- **GIVEN** 用户分别访问设备管理、IOT 卡管理 and 订单列表
|
||||
- **WHEN** 页面渲染创建导出任务按钮
|
||||
- **THEN** 设备管理 MUST use `devices:export`
|
||||
- **AND** IOT 卡管理 MUST use `iot_card:export`
|
||||
- **AND** 订单列表 MUST use `orders:export`
|
||||
- **AND** possessing one of these permissions MUST NOT reveal or enable the other two export buttons
|
||||
|
||||
### Requirement: Scene-Aware Export Task Detail Permissions
|
||||
|
||||
The export task detail page SHALL apply detail, download, and cancel permissions according to the task's scene.
|
||||
|
||||
#### Scenario: Enforce scene permissions on direct detail access
|
||||
|
||||
- **GIVEN** 用户直接打开某个导出任务详情 URL
|
||||
- **WHEN** 系统加载任务详情 and reads the returned `scene`
|
||||
- **THEN** 系统 MUST require the matching scene detail permission before showing the detail content
|
||||
- **AND** 系统 MUST use the matching scene download and cancel permissions before showing detail-page buttons
|
||||
|
||||
#### Scenario: Prevent cross-scene action leakage
|
||||
|
||||
- **GIVEN** 用户 has only order export task download permission
|
||||
- **AND** 用户打开 a completed device export task detail
|
||||
- **WHEN** 页面渲染详情操作区
|
||||
- **THEN** 页面 MUST NOT show the device task download button
|
||||
- **AND** 页面 MUST NOT allow downloading that device task through the order download permission
|
||||
46
openspec/changes/update-export-task-scene-pages/tasks.md
Normal file
46
openspec/changes/update-export-task-scene-pages/tasks.md
Normal file
@@ -0,0 +1,46 @@
|
||||
## 1. Proposal Review
|
||||
|
||||
- [x] 1.1 确认三个页面名称为“导出设备”“导出IOT卡”“导出订单”。
|
||||
- [x] 1.2 确认固定场景值分别为 `device`、`iot_card`、`order`。
|
||||
- [x] 1.3 确认三套页面和按钮权限编码，或按后端权限命名规范替换设计中的默认建议。
|
||||
- [x] 1.4 确认本提案与 `add-order-export-scene` 合并实施，订单场景不再通过旧导出场景筛选进入。
|
||||
|
||||
## 2. Routing And Menu
|
||||
|
||||
- [x] 2.1 新增三条导出任务列表路由别名和路由记录。
|
||||
- [x] 2.2 在导出管理菜单下新增“导出设备”“导出IOT卡”“导出订单”。
|
||||
- [x] 2.3 删除或隐藏旧“导出列表”菜单入口。
|
||||
- [x] 2.4 为三条路由分别配置独立页面访问权限。
|
||||
- [x] 2.5 更新菜单国际化文案和权限配置。
|
||||
|
||||
## 3. Export Task List Pages
|
||||
|
||||
- [x] 3.1 将现有导出任务列表改造成可复用固定场景列表，支持传入页面标题、固定 `scene` 和权限映射。
|
||||
- [x] 3.2 移除搜索表单中的“导出场景”筛选项。
|
||||
- [x] 3.3 列表查询始终携带当前页面固定 `scene`。
|
||||
- [x] 3.4 移除或默认隐藏列表中的“场景”列。
|
||||
- [x] 3.5 保留任务状态、创建时间、分页、刷新等现有列表能力。
|
||||
|
||||
## 4. Scene-Specific Actions
|
||||
|
||||
- [x] 4.1 详情入口按当前页面场景检查对应 `detail` 权限。
|
||||
- [x] 4.2 下载按钮按当前页面场景检查对应 `download` 权限。
|
||||
- [x] 4.3 取消按钮按当前页面场景检查对应 `cancel` 权限。
|
||||
- [x] 4.4 导出任务详情页根据任务 `scene` 使用对应详情、下载、取消权限。
|
||||
- [x] 4.5 验证只有某一场景权限时，不会看到其他场景页面或按钮。
|
||||
|
||||
## 5. Business Export Entrypoints
|
||||
|
||||
- [x] 5.1 设备管理导出按钮继续使用 `devices:export` 并创建 `scene=device` 任务。
|
||||
- [x] 5.2 IOT 卡管理导出按钮继续使用 `iot_card:export` 并创建 `scene=iot_card` 任务。
|
||||
- [x] 5.3 订单列表导出按钮使用 `orders:export` 并创建 `scene=order` 任务。
|
||||
- [x] 5.4 确认三个业务导出按钮权限编码互不复用。
|
||||
|
||||
## 6. Verification
|
||||
|
||||
- [x] 6.1 验证“导出设备”页面请求 `GET /api/admin/export-tasks` 时固定携带 `scene=device`。
|
||||
- [x] 6.2 验证“导出IOT卡”页面请求固定携带 `scene=iot_card`。
|
||||
- [x] 6.3 验证“导出订单”页面请求固定携带 `scene=order`。
|
||||
- [x] 6.4 验证三个页面均不展示“导出场景”筛选项。
|
||||
- [x] 6.5 验证三页详情、下载、取消按钮按各自权限显示和拦截。
|
||||
- [x] 6.6 运行类型检查、lint 和相关页面手动回归。
|
||||
@@ -0,0 +1,15 @@
|
||||
# Change: 创建订单使用套餐建议售价
|
||||
|
||||
## Why
|
||||
|
||||
创建订单弹窗中套餐选项当前展示成本价，容易让运营人员误以为下单金额等同成本价。套餐选项价格应展示套餐 `suggested_retail_price` 建议售价。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 创建订单弹窗的套餐选项展示 `suggested_retail_price`，不再展示 `cost_price`。
|
||||
- 创建订单提交请求仍只提交套餐 ID 等订单字段，不额外提交 `suggested_retail_price`。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `order-management`
|
||||
- Affected code: `src/views/order-management/order-list/index.vue`
|
||||
@@ -0,0 +1,21 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Create Order Suggested Retail Price
|
||||
|
||||
The system SHALL show the selected package `suggested_retail_price` as the package price in the admin order creation dialog.
|
||||
|
||||
#### Scenario: Display package suggested retail price in create order dialog
|
||||
|
||||
- **GIVEN** 用户正在订单管理创建订单弹窗选择套餐
|
||||
- **AND** 套餐返回 `suggested_retail_price` 为 `2000` 分且 `cost_price` 为 `1000` 分
|
||||
- **WHEN** 系统渲染套餐下拉选项
|
||||
- **THEN** 套餐选项 MUST display `¥20.00`
|
||||
- **AND** 套餐选项 MUST NOT display `¥10.00` as the package price
|
||||
|
||||
#### Scenario: Do not submit package price when creating an order
|
||||
|
||||
- **GIVEN** 用户已在创建订单弹窗选择套餐
|
||||
- **AND** 所选套餐的 `suggested_retail_price` 为 `2000` 分
|
||||
- **WHEN** 用户提交创建订单表单
|
||||
- **THEN** 系统 MUST NOT include `suggested_retail_price` in the create-order request payload
|
||||
- **AND** 系统 MUST NOT include the selected package `cost_price` in the create-order request payload
|
||||
@@ -0,0 +1,9 @@
|
||||
## 1. Implementation
|
||||
|
||||
- [x] 1.1 Update create-order package option display to show `suggested_retail_price`.
|
||||
- [x] 1.2 Keep create-order request payload unchanged without submitting `suggested_retail_price`.
|
||||
|
||||
## 2. Verification
|
||||
|
||||
- [x] 2.1 Validate the OpenSpec change with strict mode.
|
||||
- [x] 2.2 Run relevant frontend type/lint verification.
|
||||
@@ -8,7 +8,7 @@
|
||||
|
||||
- 退款详情中直接展示退款凭证图片，点击图片后可放大预览。
|
||||
- 创建退款申请的订单号搜索/选择请求必须增加 `payment_status: 2` 条件。
|
||||
- 退款管理凭证上传支持多张图片，并将所有上传后的文件 key 以英文逗号拼接后放入 `refund_voucher_key` 参数。
|
||||
- 退款管理凭证上传支持多张图片，并按 ADR-0001 将所有上传后的文件 key 以 `string[]` 放入 `refund_voucher_key` 参数。
|
||||
|
||||
## Impact
|
||||
|
||||
@@ -17,4 +17,4 @@
|
||||
- Refund detail voucher display and image preview behavior
|
||||
- Create refund request order selector query params
|
||||
- Refund management voucher upload component and submit payload
|
||||
- Breaking changes: Refund voucher payload field for this flow remains `refund_voucher_key` and supports one or more uploaded image keys separated by English commas.
|
||||
- Breaking changes: Refund voucher payload field for this flow remains `refund_voucher_key`, but new submissions use `string[]`. Legacy single-key strings and comma-separated strings are read-only compatibility inputs for display normalization.
|
||||
|
||||
@@ -75,7 +75,7 @@ The system SHALL allow the requested refund amount in create refund application
|
||||
|
||||
### Requirement: Refund Management Multi Image Voucher Upload
|
||||
|
||||
The system SHALL allow multiple refund voucher images in any browser-recognized image format to be uploaded in refund management and SHALL submit all uploaded file keys in the `refund_voucher_key` parameter as a comma-separated string.
|
||||
The system SHALL allow multiple refund voucher images in any browser-recognized image format to be uploaded in refund management and SHALL submit all uploaded file keys in the `refund_voucher_key` parameter as a `string[]`. The earlier comma-separated-string submission convention is superseded by ADR-0001; legacy single-key strings and comma-separated strings are only normalized when reading existing records for display.
|
||||
|
||||
#### Scenario: Submit multiple uploaded voucher images
|
||||
|
||||
@@ -83,9 +83,9 @@ The system SHALL allow multiple refund voucher images in any browser-recognized
|
||||
- **AND** 用户上传了多张退款凭证图片
|
||||
- **WHEN** 每张图片上传成功并返回文件 key
|
||||
- **AND** 用户提交表单
|
||||
- **THEN** 系统 MUST join the uploaded file keys with English commas
|
||||
- **AND** 系统 MUST put the joined string into `refund_voucher_key`
|
||||
- **AND** `refund_voucher_key` MUST look like `attachments/a.jpg,attachments/b.jpg` when multiple files exist
|
||||
- **THEN** 系统 MUST put the uploaded file keys into `refund_voucher_key` as a `string[]`
|
||||
- **AND** `refund_voucher_key` MUST look like `["attachments/a.jpg", "attachments/b.jpg"]` when multiple files exist
|
||||
- **AND** 系统 MUST NOT submit a comma-separated voucher string for new records
|
||||
|
||||
#### Scenario: Upload any image format refund voucher without frontend size limit
|
||||
|
||||
@@ -99,7 +99,7 @@ The system SHALL allow multiple refund voucher images in any browser-recognized
|
||||
- **GIVEN** 用户正在退款管理中创建或提交退款相关记录
|
||||
- **AND** 用户只上传了一张退款凭证图片
|
||||
- **WHEN** 用户提交表单
|
||||
- **THEN** 系统 MUST put that single file key into `refund_voucher_key` without a trailing comma
|
||||
- **THEN** 系统 MUST put that single file key into `refund_voucher_key` as a one-item `string[]`
|
||||
|
||||
#### Scenario: Block submission without required voucher image
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
- [x] 1.2 Add click-to-preview/enlarge behavior for refund detail voucher images.
|
||||
- [x] 1.3 Add `payment_status: 2` to the order number search/select request used by create refund application.
|
||||
- [x] 1.4 Update refund management voucher upload to allow multiple image uploads.
|
||||
- [x] 1.5 Submit uploaded voucher file keys joined by English commas in `refund_voucher_key`.
|
||||
- [x] 1.5 Submit uploaded voucher file keys as `string[]` in `refund_voucher_key`; do not submit comma-separated strings for new records.
|
||||
- [x] 1.6 Validate that at least one voucher image is uploaded before submission when voucher is required.
|
||||
- [x] 1.7 Verify refund detail display, order selector filtering, and multi-image payload behavior.
|
||||
- [x] 1.8 Allow requested refund amount `0` while blocking negative and over-actual amounts.
|
||||
|
||||
15
pnpm-workspace.yaml
Normal file
15
pnpm-workspace.yaml
Normal file
@@ -0,0 +1,15 @@
|
||||
packages:
|
||||
- .
|
||||
|
||||
allowBuilds:
|
||||
'@parcel/watcher': true
|
||||
core-js: true
|
||||
cwebp-bin: true
|
||||
es5-ext: true
|
||||
esbuild: true
|
||||
gifsicle: true
|
||||
jpegtran-bin: true
|
||||
mozjpeg: true
|
||||
optipng-bin: true
|
||||
pngquant-bin: true
|
||||
vue-demi: true
|
||||
110
scripts/tests/agentRechargeActions.test.mjs
Normal file
110
scripts/tests/agentRechargeActions.test.mjs
Normal file
@@ -0,0 +1,110 @@
|
||||
import test from 'node:test'
|
||||
import assert from 'node:assert/strict'
|
||||
import { mkdtemp, rm, stat } from 'node:fs/promises'
|
||||
import { tmpdir } from 'node:os'
|
||||
import { join } from 'node:path'
|
||||
import { pathToFileURL } from 'node:url'
|
||||
import * as esbuild from 'esbuild'
|
||||
|
||||
async function resolveSrcAlias(path) {
|
||||
const resolvedPath = join(process.cwd(), 'src', path.slice(2))
|
||||
|
||||
try {
|
||||
if ((await stat(resolvedPath)).isDirectory()) {
|
||||
return join(resolvedPath, 'index.ts')
|
||||
}
|
||||
} catch {
|
||||
// Let esbuild report the original resolution failure.
|
||||
}
|
||||
|
||||
return resolvedPath
|
||||
}
|
||||
|
||||
async function importBundledActions() {
|
||||
const tempDir = await mkdtemp(join(tmpdir(), 'agent-recharge-actions-'))
|
||||
const bundlePath = join(tempDir, 'agentRechargeActions.mjs')
|
||||
|
||||
await esbuild.build({
|
||||
entryPoints: ['src/views/finance/agent-recharge/agentRechargeActions.ts'],
|
||||
bundle: true,
|
||||
outfile: bundlePath,
|
||||
format: 'esm',
|
||||
platform: 'node',
|
||||
absWorkingDir: process.cwd(),
|
||||
plugins: [
|
||||
{
|
||||
name: 'alias-src',
|
||||
setup(build) {
|
||||
build.onResolve({ filter: /^@\// }, async (args) => ({
|
||||
path: await resolveSrcAlias(args.path)
|
||||
}))
|
||||
}
|
||||
}
|
||||
]
|
||||
})
|
||||
|
||||
const module = await import(pathToFileURL(bundlePath).href)
|
||||
return {
|
||||
module,
|
||||
cleanup: () => rm(tempDir, { recursive: true, force: true })
|
||||
}
|
||||
}
|
||||
|
||||
test('pending agent recharge exposes reject action for admins with rejection permission', async () => {
|
||||
const { module, cleanup } = await importBundledActions()
|
||||
const { buildAgentRechargeActions } = module
|
||||
const row = {
|
||||
id: 42,
|
||||
status: 1,
|
||||
payment_method: 'wechat',
|
||||
payment_voucher_key: []
|
||||
}
|
||||
const handledRows = []
|
||||
|
||||
try {
|
||||
const actions = buildAgentRechargeActions(row, {
|
||||
hasAuth: (permission) => permission === 'agent_recharge:reject',
|
||||
onViewPaymentVoucher: () => {},
|
||||
onConfirmPayment: () => {},
|
||||
onReject: (recharge) => handledRows.push(recharge)
|
||||
})
|
||||
|
||||
assert.deepEqual(
|
||||
actions.map((action) => action.label),
|
||||
['拒绝']
|
||||
)
|
||||
|
||||
actions[0].handler()
|
||||
|
||||
assert.deepEqual(handledRows, [row])
|
||||
} finally {
|
||||
await cleanup()
|
||||
}
|
||||
})
|
||||
|
||||
test('non-pending agent recharge does not expose reject action', async () => {
|
||||
const { module, cleanup } = await importBundledActions()
|
||||
const { buildAgentRechargeActions } = module
|
||||
const row = {
|
||||
id: 42,
|
||||
status: 2,
|
||||
payment_method: 'wechat',
|
||||
payment_voucher_key: []
|
||||
}
|
||||
|
||||
try {
|
||||
const actions = buildAgentRechargeActions(row, {
|
||||
hasAuth: (permission) => permission === 'agent_recharge:reject',
|
||||
onViewPaymentVoucher: () => {},
|
||||
onConfirmPayment: () => {},
|
||||
onReject: () => {}
|
||||
})
|
||||
|
||||
assert.deepEqual(
|
||||
actions.map((action) => action.label),
|
||||
[]
|
||||
)
|
||||
} finally {
|
||||
await cleanup()
|
||||
}
|
||||
})
|
||||
49
scripts/tests/agentRechargeDisplay.test.mjs
Normal file
49
scripts/tests/agentRechargeDisplay.test.mjs
Normal file
@@ -0,0 +1,49 @@
|
||||
import test from 'node:test'
|
||||
import assert from 'node:assert/strict'
|
||||
import { mkdtemp, rm } from 'node:fs/promises'
|
||||
import { tmpdir } from 'node:os'
|
||||
import { join } from 'node:path'
|
||||
import { pathToFileURL } from 'node:url'
|
||||
import * as esbuild from 'esbuild'
|
||||
|
||||
async function importBundledDisplay() {
|
||||
const tempDir = await mkdtemp(join(tmpdir(), 'agent-recharge-display-'))
|
||||
const bundlePath = join(tempDir, 'agentRechargeDisplay.mjs')
|
||||
|
||||
await esbuild.build({
|
||||
entryPoints: ['src/views/finance/agent-recharge/agentRechargeDisplay.ts'],
|
||||
bundle: true,
|
||||
outfile: bundlePath,
|
||||
format: 'esm',
|
||||
platform: 'node',
|
||||
absWorkingDir: process.cwd()
|
||||
})
|
||||
|
||||
const module = await import(pathToFileURL(bundlePath).href)
|
||||
return {
|
||||
module,
|
||||
cleanup: () => rm(tempDir, { recursive: true, force: true })
|
||||
}
|
||||
}
|
||||
|
||||
test('agent recharge rejection reason display uses backend rejection_reason when present', async () => {
|
||||
const { module, cleanup } = await importBundledDisplay()
|
||||
|
||||
try {
|
||||
assert.equal(module.formatRejectionReason('凭证不清晰'), '凭证不清晰')
|
||||
} finally {
|
||||
await cleanup()
|
||||
}
|
||||
})
|
||||
|
||||
test('agent recharge rejection reason display falls back to dash when absent', async () => {
|
||||
const { module, cleanup } = await importBundledDisplay()
|
||||
|
||||
try {
|
||||
assert.equal(module.formatRejectionReason(''), '-')
|
||||
assert.equal(module.formatRejectionReason(null), '-')
|
||||
assert.equal(module.formatRejectionReason(undefined), '-')
|
||||
} finally {
|
||||
await cleanup()
|
||||
}
|
||||
})
|
||||
69
scripts/tests/agentRechargeService.test.mjs
Normal file
69
scripts/tests/agentRechargeService.test.mjs
Normal file
@@ -0,0 +1,69 @@
|
||||
import test from 'node:test'
|
||||
import assert from 'node:assert/strict'
|
||||
import { mkdtemp, rm, writeFile } from 'node:fs/promises'
|
||||
import { tmpdir } from 'node:os'
|
||||
import { join } from 'node:path'
|
||||
import { pathToFileURL } from 'node:url'
|
||||
import * as esbuild from 'esbuild'
|
||||
|
||||
test('agent recharge rejection posts the rejection reason to the order rejection endpoint', async () => {
|
||||
const calls = []
|
||||
const tempDir = await mkdtemp(join(tmpdir(), 'agent-recharge-service-'))
|
||||
const bundlePath = join(tempDir, 'agentRechargeService.mjs')
|
||||
const httpMockPath = join(tempDir, 'httpMock.mjs')
|
||||
|
||||
await writeFile(
|
||||
httpMockPath,
|
||||
`
|
||||
export const calls = globalThis.__agentRechargeHttpCalls
|
||||
export default {
|
||||
post(options) {
|
||||
calls.push(options)
|
||||
return Promise.resolve({ code: 0, data: undefined })
|
||||
}
|
||||
}
|
||||
`,
|
||||
'utf8'
|
||||
)
|
||||
|
||||
globalThis.__agentRechargeHttpCalls = calls
|
||||
|
||||
try {
|
||||
await esbuild.build({
|
||||
entryPoints: ['src/api/modules/agentRecharge.ts'],
|
||||
bundle: true,
|
||||
outfile: bundlePath,
|
||||
format: 'esm',
|
||||
platform: 'node',
|
||||
absWorkingDir: process.cwd(),
|
||||
plugins: [
|
||||
{
|
||||
name: 'mock-http-boundary',
|
||||
setup(build) {
|
||||
build.onResolve({ filter: /^@\/utils\/http$/ }, () => ({
|
||||
path: httpMockPath
|
||||
}))
|
||||
}
|
||||
}
|
||||
]
|
||||
})
|
||||
|
||||
const { AgentRechargeService } = await import(pathToFileURL(bundlePath).href)
|
||||
|
||||
await AgentRechargeService.rejectAgentRecharge(42, {
|
||||
rejection_reason: '支付凭证不符合要求'
|
||||
})
|
||||
|
||||
assert.deepEqual(calls, [
|
||||
{
|
||||
url: '/api/admin/agent-recharges/42/reject',
|
||||
data: {
|
||||
rejection_reason: '支付凭证不符合要求'
|
||||
}
|
||||
}
|
||||
])
|
||||
} finally {
|
||||
delete globalThis.__agentRechargeHttpCalls
|
||||
await rm(tempDir, { recursive: true, force: true })
|
||||
}
|
||||
})
|
||||
107
skills-lock.json
Normal file
107
skills-lock.json
Normal file
@@ -0,0 +1,107 @@
|
||||
{
|
||||
"version": 1,
|
||||
"skills": {
|
||||
"ask-matt": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/ask-matt/SKILL.md",
|
||||
"computedHash": "f3ac3351e2a242ce2591e4f8475424d58f62db3f5786332b78f330b15312d1e0"
|
||||
},
|
||||
"codebase-design": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/codebase-design/SKILL.md",
|
||||
"computedHash": "2426dc4accf1a85dedfb560edb3a877ec8828b7375ea08c970df2b6c900a2a22"
|
||||
},
|
||||
"diagnosing-bugs": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/diagnosing-bugs/SKILL.md",
|
||||
"computedHash": "1a993ce9b2aaa653ee441c8d7efb7f27de03493c722be6dfb8137bcb8db1bc72"
|
||||
},
|
||||
"domain-modeling": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/domain-modeling/SKILL.md",
|
||||
"computedHash": "67343881f5def98487d56243155716110afbcbf22ec92421c882d532b941cb17"
|
||||
},
|
||||
"grill-me": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/productivity/grill-me/SKILL.md",
|
||||
"computedHash": "f321507f77702a54af1db66549ec1685fc625390d06c57d7949cdcda8eb1b5c7"
|
||||
},
|
||||
"grill-with-docs": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/grill-with-docs/SKILL.md",
|
||||
"computedHash": "e7ef25bbee50cda2eb7b3a8ef541db0a0396dad7d369f7d14fb610671dd1864b"
|
||||
},
|
||||
"grilling": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/productivity/grilling/SKILL.md",
|
||||
"computedHash": "ef685a6fa0bbe73b05bbd8dc1ec97258191587f07c6aa7dbc9006675ceb8f90f"
|
||||
},
|
||||
"handoff": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/productivity/handoff/SKILL.md",
|
||||
"computedHash": "5d0f81e38abe6b984e1feaa731927de5291d040982106ac513cf54ec240e00ec"
|
||||
},
|
||||
"improve-codebase-architecture": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/improve-codebase-architecture/SKILL.md",
|
||||
"computedHash": "8bf292143ca93b00276a0de0fc5f84f2381f4690c5b0d32e99fa283a072f392f"
|
||||
},
|
||||
"prototype": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/prototype/SKILL.md",
|
||||
"computedHash": "40ff56e36bb13b5a9a16903efd6c78a02690ba430e10a8d1a65559100b77f475"
|
||||
},
|
||||
"setup-matt-pocock-skills": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/setup-matt-pocock-skills/SKILL.md",
|
||||
"computedHash": "400da4521ed701c99e8824ae7b71c7859632ee91481b3715890036cf8aec6857"
|
||||
},
|
||||
"tdd": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/tdd/SKILL.md",
|
||||
"computedHash": "d5ca5c8ae0615f343f1cfd71591f4a586046d77b1f36e8d67b8f643bad51043e"
|
||||
},
|
||||
"teach": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/productivity/teach/SKILL.md",
|
||||
"computedHash": "9cd31ea42b40915ea5fd3949ed229b217d1dfad07dd93d9b0db771dcdd6a6c8a"
|
||||
},
|
||||
"to-issues": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/to-issues/SKILL.md",
|
||||
"computedHash": "4e2a11d35f018490d42a79234432f779d7131b9920373ef24cfbc68229bfef6c"
|
||||
},
|
||||
"to-prd": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/to-prd/SKILL.md",
|
||||
"computedHash": "5a733e19d825f22e83de52e68b8840c9fd2fa7501282277a122c1aa28a922059"
|
||||
},
|
||||
"triage": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/engineering/triage/SKILL.md",
|
||||
"computedHash": "b77ea99c2e6e97815b373cc476ad4cc1835d3e736867b764602147be71f6c131"
|
||||
},
|
||||
"writing-great-skills": {
|
||||
"source": "mattpocock/skills",
|
||||
"sourceType": "github",
|
||||
"skillPath": "skills/productivity/writing-great-skills/SKILL.md",
|
||||
"computedHash": "581f78b50b3d81b095de86b5c18a4d9fa932fbe414cc82bd26d627d4da518f07"
|
||||
}
|
||||
}
|
||||
}
|
||||
139
src/App.vue
139
src/App.vue
@@ -16,6 +16,7 @@
|
||||
import { setThemeTransitionClass } from '@/utils'
|
||||
import { checkStorageCompatibility } from '@/utils'
|
||||
import ChunkErrorBoundary from '@/components/core/others/ChunkErrorBoundary.vue'
|
||||
import { ElMessageBox } from 'element-plus'
|
||||
|
||||
const userStore = useUserStore()
|
||||
const { language } = storeToRefs(userStore)
|
||||
@@ -25,6 +26,13 @@
|
||||
en: en
|
||||
}
|
||||
|
||||
const VERSION_CHECK_INTERVAL = 5 * 60 * 1000
|
||||
const VERSION_PROMPT_STORAGE_KEY = 'admin-xm-iot:confirmed-version-update'
|
||||
let versionCheckTimer: number | undefined
|
||||
let currentEntrySignature = ''
|
||||
let upgradePromptVisible = false
|
||||
let removeVisibilityChangeListener: (() => void) | undefined
|
||||
|
||||
onBeforeMount(() => {
|
||||
setThemeTransitionClass(true)
|
||||
})
|
||||
@@ -36,10 +44,19 @@
|
||||
setThemeTransitionClass(false)
|
||||
// 系统升级
|
||||
systemUpgrade()
|
||||
// 检查前端版本更新
|
||||
startVersionUpdateCheck()
|
||||
// 获取用户信息
|
||||
getUserInfo()
|
||||
})
|
||||
|
||||
onBeforeUnmount(() => {
|
||||
if (versionCheckTimer) {
|
||||
window.clearInterval(versionCheckTimer)
|
||||
}
|
||||
removeVisibilityChangeListener?.()
|
||||
})
|
||||
|
||||
// 获取用户信息
|
||||
const getUserInfo = async () => {
|
||||
if (userStore.isLogin && userStore.accessToken) {
|
||||
@@ -55,4 +72,126 @@
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
const getEntrySignature = (html: string) => {
|
||||
const matches = html.match(/(?:src|href)="[^"]*\/assets\/[^""]+\.(?:js|css)"/g)
|
||||
return matches?.sort().join('|') || ''
|
||||
}
|
||||
|
||||
const getLoadedEntrySignature = () => {
|
||||
return Array.from(
|
||||
document.querySelectorAll<HTMLScriptElement | HTMLLinkElement>('script[src],link[href]')
|
||||
)
|
||||
.map((element) => ('src' in element ? element.src : element.href))
|
||||
.filter((url) => /\/assets\/.*\.(js|css)(\?|$)/.test(url))
|
||||
.sort()
|
||||
.join('|')
|
||||
}
|
||||
|
||||
const getStringHash = (value: string) => {
|
||||
let hash = 0
|
||||
|
||||
for (let i = 0; i < value.length; i++) {
|
||||
hash = (hash << 5) - hash + value.charCodeAt(i)
|
||||
hash |= 0
|
||||
}
|
||||
|
||||
return Math.abs(hash).toString(36)
|
||||
}
|
||||
|
||||
const getBrowserFingerprint = () => {
|
||||
return getStringHash(
|
||||
[
|
||||
navigator.userAgent,
|
||||
navigator.language,
|
||||
navigator.platform,
|
||||
Intl.DateTimeFormat().resolvedOptions().timeZone,
|
||||
`${screen.width}x${screen.height}x${screen.colorDepth}`
|
||||
].join('|')
|
||||
)
|
||||
}
|
||||
|
||||
const getConfirmedVersionKey = (signature: string) => {
|
||||
return `${getBrowserFingerprint()}:${getStringHash(signature)}`
|
||||
}
|
||||
|
||||
const getConfirmedVersionUpdate = () => {
|
||||
try {
|
||||
return localStorage.getItem(VERSION_PROMPT_STORAGE_KEY)
|
||||
} catch {
|
||||
return null
|
||||
}
|
||||
}
|
||||
|
||||
const setConfirmedVersionUpdate = (signature: string) => {
|
||||
try {
|
||||
localStorage.setItem(VERSION_PROMPT_STORAGE_KEY, getConfirmedVersionKey(signature))
|
||||
} catch {
|
||||
// localStorage may be unavailable in private mode.
|
||||
}
|
||||
}
|
||||
|
||||
const reloadWithCacheBuster = () => {
|
||||
const url = new URL(window.location.href)
|
||||
url.searchParams.set('_t', Date.now().toString())
|
||||
window.location.replace(url.toString())
|
||||
}
|
||||
|
||||
const checkVersionUpdate = async () => {
|
||||
if (upgradePromptVisible || document.hidden) return
|
||||
|
||||
try {
|
||||
const response = await fetch(import.meta.env.BASE_URL, {
|
||||
cache: 'no-store'
|
||||
})
|
||||
const html = await response.text()
|
||||
const latestSignature = getEntrySignature(html)
|
||||
|
||||
if (!latestSignature) return
|
||||
|
||||
if (!currentEntrySignature) {
|
||||
currentEntrySignature = latestSignature
|
||||
return
|
||||
}
|
||||
|
||||
if (currentEntrySignature !== latestSignature) {
|
||||
if (getConfirmedVersionUpdate() === getConfirmedVersionKey(latestSignature)) {
|
||||
currentEntrySignature = latestSignature
|
||||
return
|
||||
}
|
||||
|
||||
upgradePromptVisible = true
|
||||
await ElMessageBox.alert('系统已发布新版本，请刷新页面后继续使用。', '发现新版本', {
|
||||
confirmButtonText: '立即更新',
|
||||
type: 'warning',
|
||||
closeOnClickModal: false,
|
||||
closeOnPressEscape: false
|
||||
})
|
||||
setConfirmedVersionUpdate(latestSignature)
|
||||
currentEntrySignature = latestSignature
|
||||
reloadWithCacheBuster()
|
||||
}
|
||||
} catch (error) {
|
||||
console.warn('检查版本更新失败:', error)
|
||||
} finally {
|
||||
upgradePromptVisible = false
|
||||
}
|
||||
}
|
||||
|
||||
const startVersionUpdateCheck = () => {
|
||||
if (import.meta.env.DEV) return
|
||||
|
||||
currentEntrySignature = getLoadedEntrySignature()
|
||||
checkVersionUpdate()
|
||||
versionCheckTimer = window.setInterval(checkVersionUpdate, VERSION_CHECK_INTERVAL)
|
||||
const handleVisibilityChange = () => {
|
||||
if (!document.hidden) {
|
||||
checkVersionUpdate()
|
||||
}
|
||||
}
|
||||
document.addEventListener('visibilitychange', handleVisibilityChange)
|
||||
removeVisibilityChangeListener = () => {
|
||||
document.removeEventListener('visibilitychange', handleVisibilityChange)
|
||||
}
|
||||
}
|
||||
</script>
|
||||
|
||||
@@ -1,45 +0,0 @@
|
||||
import request from '@/utils/http'
|
||||
import { PaginationResponse, BaseResponse } from '@/types/api'
|
||||
import { ArticleType, ArticleCategoryType, ArticleQueryParams } from '@/api/modules'
|
||||
|
||||
// 文章
|
||||
export class ArticleService {
|
||||
// 获取文章列表
|
||||
static getArticleList(params: ArticleQueryParams) {
|
||||
const { page, size, searchVal, year } = params
|
||||
return request.get<PaginationResponse<ArticleType>>({
|
||||
url: `/api/articles/${page}/${size}?title=${searchVal}&year=${year}`
|
||||
})
|
||||
}
|
||||
|
||||
// 获取文章类型
|
||||
static getArticleTypes(params: object) {
|
||||
return request.get<BaseResponse<ArticleCategoryType[]>>({
|
||||
url: '/api/articles/types',
|
||||
params
|
||||
})
|
||||
}
|
||||
|
||||
// 获取文章详情
|
||||
static getArticleDetail(id: number) {
|
||||
return request.get<BaseResponse<ArticleType>>({
|
||||
url: `/api/articles/${id}`
|
||||
})
|
||||
}
|
||||
|
||||
// 新增文章
|
||||
static addArticle(params: any) {
|
||||
return request.post<BaseResponse>({
|
||||
url: '/api/articles/',
|
||||
data: params
|
||||
})
|
||||
}
|
||||
|
||||
// 编辑文章
|
||||
static editArticle(id: number, params: any) {
|
||||
return request.put<BaseResponse>({
|
||||
url: `/api/articles/${id}`,
|
||||
data: params
|
||||
})
|
||||
}
|
||||
}
|
||||
@@ -1,25 +0,0 @@
|
||||
import { asyncRoutes } from '@/router/routes/asyncRoutes'
|
||||
import { menuDataToRouter } from '@/router/utils/menuToRouter'
|
||||
import { AppRouteRecord } from '@/types/router'
|
||||
|
||||
interface MenuResponse {
|
||||
menuList: AppRouteRecord[]
|
||||
}
|
||||
|
||||
// 菜单接口
|
||||
export const menuService = {
|
||||
async getMenuList(delay = 300): Promise<MenuResponse> {
|
||||
try {
|
||||
// 模拟接口返回的菜单数据
|
||||
const menuData = asyncRoutes
|
||||
// 处理菜单数据
|
||||
const menuList = menuData.map((route) => menuDataToRouter(route))
|
||||
// 模拟接口延迟
|
||||
await new Promise((resolve) => setTimeout(resolve, delay))
|
||||
|
||||
return { menuList }
|
||||
} catch (error) {
|
||||
throw error instanceof Error ? error : new Error('获取菜单失败')
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -9,6 +9,7 @@ import type {
|
||||
AgentRechargeListResponse,
|
||||
CreateAgentRechargeRequest,
|
||||
ConfirmOfflinePaymentRequest,
|
||||
RejectAgentRechargeRequest,
|
||||
BaseResponse
|
||||
} from '@/types/api'
|
||||
|
||||
@@ -55,4 +56,16 @@ export class AgentRechargeService extends BaseService {
|
||||
data
|
||||
)
|
||||
}
|
||||
|
||||
/**
|
||||
* 拒绝代理充值订单
|
||||
* @param id 充值订单ID
|
||||
* @param data 拒绝请求参数
|
||||
*/
|
||||
static rejectAgentRecharge(
|
||||
id: number,
|
||||
data: RejectAgentRechargeRequest
|
||||
): Promise<BaseResponse<void>> {
|
||||
return this.post<BaseResponse<void>>(`/api/admin/agent-recharges/${id}/reject`, data)
|
||||
}
|
||||
}
|
||||
|
||||
@@ -1,72 +0,0 @@
|
||||
/**
|
||||
* 文章相关类型定义
|
||||
*/
|
||||
|
||||
// 文章类型 (新命名规范)
|
||||
export interface Article {
|
||||
id?: number
|
||||
blogClass: string
|
||||
title: string
|
||||
count?: number
|
||||
htmlContent: string
|
||||
createTime: string
|
||||
homeImg: string
|
||||
brief: string
|
||||
typeName?: string
|
||||
status?: number
|
||||
author?: string
|
||||
tags?: string[]
|
||||
}
|
||||
|
||||
// 兼容原有的文章类型命名
|
||||
export interface ArticleType {
|
||||
id?: number
|
||||
blog_class: string
|
||||
title: string
|
||||
count?: number
|
||||
html_content: string
|
||||
create_time: string
|
||||
home_img: string
|
||||
brief: string
|
||||
type_name?: string
|
||||
}
|
||||
|
||||
// 文章分类类型 (新命名规范)
|
||||
export interface ArticleCategory {
|
||||
id: number
|
||||
name: string
|
||||
icon: string
|
||||
count: number
|
||||
description?: string
|
||||
sortOrder?: number
|
||||
}
|
||||
|
||||
// 兼容原有的文章分类类型命名
|
||||
export interface ArticleCategoryType {
|
||||
id: number
|
||||
name: string
|
||||
icon: string
|
||||
count: number
|
||||
}
|
||||
|
||||
// 文章查询参数
|
||||
export interface ArticleQueryParams {
|
||||
page?: number
|
||||
size?: number
|
||||
searchVal?: string
|
||||
year?: string
|
||||
categoryId?: number
|
||||
status?: number
|
||||
}
|
||||
|
||||
// 文章创建/更新参数
|
||||
export interface ArticleFormData {
|
||||
blogClass: string
|
||||
title: string
|
||||
htmlContent: string
|
||||
homeImg: string
|
||||
brief: string
|
||||
author?: string
|
||||
tags?: string[]
|
||||
status?: number
|
||||
}
|
||||
@@ -4,8 +4,14 @@
|
||||
*/
|
||||
|
||||
import { BaseService } from '../BaseService'
|
||||
import {
|
||||
assertAssetActionAllowed,
|
||||
markAssetActionCalled,
|
||||
type AssetRateLimitedAction
|
||||
} from '@/utils/business/apiRateLimit'
|
||||
import type {
|
||||
BaseResponse,
|
||||
AssetResolveParams,
|
||||
AssetResolveResponse,
|
||||
AssetRealtimeStatusResponse,
|
||||
AssetRefreshResponse,
|
||||
@@ -21,18 +27,36 @@ import type {
|
||||
UpdateAssetRealnameStatusRequest,
|
||||
DtoUpdateAssetRealnameStatusResponse,
|
||||
AssetOperationLogsResponse,
|
||||
AssetOperationLogsParams
|
||||
AssetOperationLogsParams,
|
||||
AssetPackageUsageRecord,
|
||||
UpdateAssetPackageUsedDataRequest,
|
||||
UpdateAssetPackageExpiresAtRequest
|
||||
} from '@/types/api'
|
||||
|
||||
const runRateLimitedAssetAction = async <T>(
|
||||
action: AssetRateLimitedAction,
|
||||
identifier: string,
|
||||
request: () => Promise<T>
|
||||
): Promise<T> => {
|
||||
assertAssetActionAllowed(action, identifier)
|
||||
markAssetActionCalled(action, identifier)
|
||||
const response = await request()
|
||||
return response
|
||||
}
|
||||
|
||||
export class AssetService extends BaseService {
|
||||
/**
|
||||
* 通过任意标识符查询设备或卡的完整详情
|
||||
* 支持虚拟号、ICCID、IMEI、SN、MSISDN
|
||||
* GET /api/admin/assets/resolve/:identifier
|
||||
* @param identifier 资产标识符（虚拟号、ICCID、IMEI、SN、MSISDN）
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static resolveAsset(identifier: string): Promise<BaseResponse<AssetResolveResponse>> {
|
||||
return this.getOne<AssetResolveResponse>(`/api/admin/assets/resolve/${identifier}`)
|
||||
static resolveAsset(
|
||||
identifier: string,
|
||||
params?: AssetResolveParams
|
||||
): Promise<BaseResponse<AssetResolveResponse>> {
|
||||
return this.getOne<AssetResolveResponse>(`/api/admin/assets/resolve/${identifier}`, params)
|
||||
}
|
||||
|
||||
/**
|
||||
@@ -55,13 +79,16 @@ export class AssetService extends BaseService {
|
||||
/**
|
||||
* 主动调网关拉取最新数据后返回
|
||||
* POST /api/admin/assets/:identifier/refresh
|
||||
* 注意：设备有 30 秒冷却期，冷却中调用返回 429
|
||||
* 前端按资产标识限制 5 分钟内只能调用一次
|
||||
* @param identifier 资产标识符（ICCID 或 VirtualNo）
|
||||
*/
|
||||
static refreshAsset(identifier: string): Promise<BaseResponse<AssetRefreshResponse>> {
|
||||
return this.post<BaseResponse<AssetRefreshResponse>>(
|
||||
`/api/admin/assets/${identifier}/refresh`,
|
||||
{}
|
||||
return runRateLimitedAssetAction('refresh', identifier, () =>
|
||||
this.post<BaseResponse<AssetRefreshResponse>>(
|
||||
`/api/admin/assets/${identifier}/refresh`,
|
||||
{},
|
||||
{ timeout: 60000 }
|
||||
)
|
||||
)
|
||||
}
|
||||
|
||||
@@ -104,6 +131,36 @@ export class AssetService extends BaseService {
|
||||
)
|
||||
}
|
||||
|
||||
/**
|
||||
* 修改套餐真实已用量
|
||||
* PATCH /api/admin/assets/:identifier/packages/:package_usage_id/used-data
|
||||
*/
|
||||
static updateAssetPackageUsedData(
|
||||
identifier: string,
|
||||
packageUsageId: number,
|
||||
data: UpdateAssetPackageUsedDataRequest
|
||||
): Promise<BaseResponse<AssetPackageUsageRecord>> {
|
||||
return this.patch<BaseResponse<AssetPackageUsageRecord>>(
|
||||
`/api/admin/assets/${identifier}/packages/${packageUsageId}/used-data`,
|
||||
data as Record<string, any>
|
||||
)
|
||||
}
|
||||
|
||||
/**
|
||||
* 修改套餐过期时间
|
||||
* PATCH /api/admin/assets/:identifier/packages/:package_usage_id/expires-at
|
||||
*/
|
||||
static updateAssetPackageExpiresAt(
|
||||
identifier: string,
|
||||
packageUsageId: number,
|
||||
data: UpdateAssetPackageExpiresAtRequest
|
||||
): Promise<BaseResponse<AssetPackageUsageRecord>> {
|
||||
return this.patch<BaseResponse<AssetPackageUsageRecord>>(
|
||||
`/api/admin/assets/${identifier}/packages/${packageUsageId}/expires-at`,
|
||||
data as Record<string, any>
|
||||
)
|
||||
}
|
||||
|
||||
// ========== 资产停复机操作（统一接口）==========
|
||||
|
||||
/**
|
||||
@@ -113,20 +170,21 @@ export class AssetService extends BaseService {
|
||||
* @param identifier 资产标识符（ICCID 或 VirtualNo）
|
||||
*/
|
||||
static stopAsset(identifier: string): Promise<BaseResponse<DeviceStopResponse | void>> {
|
||||
return this.post<BaseResponse<DeviceStopResponse | void>>(
|
||||
`/api/admin/assets/${identifier}/stop`,
|
||||
{}
|
||||
return runRateLimitedAssetAction('stop', identifier, () =>
|
||||
this.post<BaseResponse<DeviceStopResponse | void>>(`/api/admin/assets/${identifier}/stop`, {})
|
||||
)
|
||||
}
|
||||
|
||||
/**
|
||||
* 复机资产（卡或设备）
|
||||
* POST /api/admin/assets/:identifier/start
|
||||
* 复机成功后设置 1 小时复机保护期（保护期内禁止停机）
|
||||
* 前端按资产标识限制 5 分钟内只能调用一次
|
||||
* @param identifier 资产标识符（ICCID 或 VirtualNo）
|
||||
*/
|
||||
static startAsset(identifier: string): Promise<BaseResponse<void>> {
|
||||
return this.post<BaseResponse<void>>(`/api/admin/assets/${identifier}/start`, {})
|
||||
return runRateLimitedAssetAction('start', identifier, () =>
|
||||
this.post<BaseResponse<void>>(`/api/admin/assets/${identifier}/start`, {})
|
||||
)
|
||||
}
|
||||
|
||||
// ========== 资产停用 ==========
|
||||
|
||||
@@ -17,6 +17,7 @@ import type {
|
||||
SuspendResumeRecord,
|
||||
CardOrder,
|
||||
BaseResponse,
|
||||
PaginationParams,
|
||||
PaginationResponse,
|
||||
ListResponse,
|
||||
GatewayRealnameLinkResponse,
|
||||
@@ -24,12 +25,36 @@ import type {
|
||||
ImportIotCardResponse,
|
||||
IotCardImportTask,
|
||||
IotCardImportTaskDetail,
|
||||
IotCardImportTaskQueryParams,
|
||||
StandaloneCardQueryParams,
|
||||
StandaloneIotCard,
|
||||
AllocateStandaloneCardsRequest,
|
||||
AllocateStandaloneCardsResponse,
|
||||
RecallStandaloneCardsRequest,
|
||||
AssetAllocationRecordQueryParams,
|
||||
AssetAllocationRecord,
|
||||
AssetAllocationRecordDetail,
|
||||
BatchSetCardSeriesBindingRequest,
|
||||
BatchSetCardSeriesBindingResponse
|
||||
} from '@/types/api'
|
||||
|
||||
type ApiQueryParams = PaginationParams & Record<string, unknown>
|
||||
|
||||
interface ImportFailureRecord {
|
||||
line?: number
|
||||
row?: number
|
||||
iccid?: string
|
||||
reason: string
|
||||
}
|
||||
|
||||
interface CardChangeNotice {
|
||||
id: string | number
|
||||
iccids: string[]
|
||||
reason: string
|
||||
createTime?: string
|
||||
operatorName?: string
|
||||
}
|
||||
|
||||
export class CardService extends BaseService {
|
||||
// ========== 号卡商品管理 ==========
|
||||
|
||||
@@ -37,7 +62,7 @@ export class CardService extends BaseService {
|
||||
* 获取号卡商品列表
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getSimCardProducts(params?: any): Promise<PaginationResponse<SimCardProduct>> {
|
||||
static getSimCardProducts(params?: ApiQueryParams): Promise<PaginationResponse<SimCardProduct>> {
|
||||
return this.getPage<SimCardProduct>('/api/simcard-products', params)
|
||||
}
|
||||
|
||||
@@ -95,15 +120,6 @@ export class CardService extends BaseService {
|
||||
return this.getOne<Card>(`/api/cards/iccid/${iccid}`)
|
||||
}
|
||||
|
||||
/**
|
||||
* 通过ICCID查询单卡详情（旧接口，已废弃）
|
||||
* @deprecated 使用 AssetService.resolveAsset 替代
|
||||
* @param iccid ICCID
|
||||
*/
|
||||
static getIotCardDetailByIccid(iccid: string): Promise<BaseResponse<any>> {
|
||||
return this.getOne<any>(`/api/admin/iot-cards/by-iccid/${iccid}`)
|
||||
}
|
||||
|
||||
/**
|
||||
* 网卡操作（充值、停复机、增减流量等）
|
||||
* @param params 操作参数
|
||||
@@ -214,7 +230,7 @@ export class CardService extends BaseService {
|
||||
* 获取导入批次列表
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getImportBatches(params?: any): Promise<PaginationResponse<CardImportBatch>> {
|
||||
static getImportBatches(params?: ApiQueryParams): Promise<PaginationResponse<CardImportBatch>> {
|
||||
return this.getPage<CardImportBatch>('/api/cards/import-batches', params)
|
||||
}
|
||||
|
||||
@@ -223,7 +239,7 @@ export class CardService extends BaseService {
|
||||
* @param file Excel文件
|
||||
* @param params 额外参数
|
||||
*/
|
||||
static importCards(file: File, params?: Record<string, any>): Promise<BaseResponse> {
|
||||
static importCards(file: File, params?: Record<string, unknown>): Promise<BaseResponse> {
|
||||
return this.upload('/api/cards/import', file, params)
|
||||
}
|
||||
|
||||
@@ -231,15 +247,17 @@ export class CardService extends BaseService {
|
||||
* 获取导入失败记录
|
||||
* @param batchId 批次ID
|
||||
*/
|
||||
static getImportFailures(batchId: string | number): Promise<ListResponse<any>> {
|
||||
return this.getList(`/api/cards/import-batches/${batchId}/failures`)
|
||||
static getImportFailures(batchId: string | number): Promise<ListResponse<ImportFailureRecord>> {
|
||||
return this.getList<ImportFailureRecord>(`/api/cards/import-batches/${batchId}/failures`)
|
||||
}
|
||||
|
||||
/**
|
||||
* 批量充值记录列表
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getBatchRechargeRecords(params?: any): Promise<PaginationResponse<BatchRechargeRecord>> {
|
||||
static getBatchRechargeRecords(
|
||||
params?: ApiQueryParams
|
||||
): Promise<PaginationResponse<BatchRechargeRecord>> {
|
||||
return this.getPage<BatchRechargeRecord>('/api/cards/batch-recharge-records', params)
|
||||
}
|
||||
|
||||
@@ -258,7 +276,7 @@ export class CardService extends BaseService {
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getCardChangeApplications(
|
||||
params?: any
|
||||
params?: ApiQueryParams
|
||||
): Promise<PaginationResponse<CardChangeApplication>> {
|
||||
return this.getPage<CardChangeApplication>('/api/card-change-applications', params)
|
||||
}
|
||||
@@ -284,8 +302,10 @@ export class CardService extends BaseService {
|
||||
* 获取换卡通知记录
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getCardChangeNotices(params?: any): Promise<PaginationResponse<any>> {
|
||||
return this.getPage('/api/card-change-notices', params)
|
||||
static getCardChangeNotices(
|
||||
params?: ApiQueryParams
|
||||
): Promise<PaginationResponse<CardChangeNotice>> {
|
||||
return this.getPage<CardChangeNotice>('/api/card-change-notices', params)
|
||||
}
|
||||
|
||||
// ========== ICCID批量导入相关 ==========
|
||||
@@ -302,8 +322,10 @@ export class CardService extends BaseService {
|
||||
* 获取导入任务列表
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getIotCardImportTasks(params?: any): Promise<PaginationResponse<IotCardImportTask>> {
|
||||
return this.getPage('/api/admin/iot-cards/import-tasks', params)
|
||||
static getIotCardImportTasks(
|
||||
params?: IotCardImportTaskQueryParams
|
||||
): Promise<PaginationResponse<IotCardImportTask>> {
|
||||
return this.getPage<IotCardImportTask>('/api/admin/iot-cards/import-tasks', params)
|
||||
}
|
||||
|
||||
/**
|
||||
@@ -330,16 +352,26 @@ export class CardService extends BaseService {
|
||||
* 批量分配单卡
|
||||
* @param data 分配参数
|
||||
*/
|
||||
static allocateStandaloneCards(data: any): Promise<BaseResponse<any>> {
|
||||
return this.post('/api/admin/iot-cards/standalone/allocate', data)
|
||||
static allocateStandaloneCards(
|
||||
data: Partial<AllocateStandaloneCardsRequest>
|
||||
): Promise<BaseResponse<AllocateStandaloneCardsResponse>> {
|
||||
return this.post<BaseResponse<AllocateStandaloneCardsResponse>>(
|
||||
'/api/admin/iot-cards/standalone/allocate',
|
||||
data
|
||||
)
|
||||
}
|
||||
|
||||
/**
|
||||
* 批量回收单卡
|
||||
* @param data 回收参数
|
||||
*/
|
||||
static recallStandaloneCards(data: any): Promise<BaseResponse<any>> {
|
||||
return this.post('/api/admin/iot-cards/standalone/recall', data)
|
||||
static recallStandaloneCards(
|
||||
data: Partial<RecallStandaloneCardsRequest>
|
||||
): Promise<BaseResponse<AllocateStandaloneCardsResponse>> {
|
||||
return this.post<BaseResponse<AllocateStandaloneCardsResponse>>(
|
||||
'/api/admin/iot-cards/standalone/recall',
|
||||
data
|
||||
)
|
||||
}
|
||||
|
||||
// ========== 资产分配记录相关 ==========
|
||||
@@ -348,16 +380,20 @@ export class CardService extends BaseService {
|
||||
* 获取资产分配记录列表
|
||||
* @param params 查询参数
|
||||
*/
|
||||
static getAssetAllocationRecords(params?: any): Promise<PaginationResponse<any>> {
|
||||
return this.getPage('/api/admin/asset-allocation-records', params)
|
||||
static getAssetAllocationRecords(
|
||||
params?: AssetAllocationRecordQueryParams
|
||||
): Promise<PaginationResponse<AssetAllocationRecord>> {
|
||||
return this.getPage<AssetAllocationRecord>('/api/admin/asset-allocation-records', params)
|
||||
}
|
||||
|
||||
/**
|
||||
* 获取资产分配记录详情
|
||||
* @param id 记录ID
|
||||
*/
|
||||
static getAssetAllocationRecordDetail(id: number): Promise<BaseResponse<any>> {
|
||||
return this.getOne(`/api/admin/asset-allocation-records/${id}`)
|
||||
static getAssetAllocationRecordDetail(
|
||||
id: number
|
||||
): Promise<BaseResponse<AssetAllocationRecordDetail>> {
|
||||
return this.getOne<AssetAllocationRecordDetail>(`/api/admin/asset-allocation-records/${id}`)
|
||||
}
|
||||
|
||||
// ========== 批量设置卡的套餐系列绑定相关 ==========
|
||||
|
||||
@@ -13,8 +13,6 @@ import type {
|
||||
WithdrawalSettingItem,
|
||||
CreateWithdrawalSettingParams,
|
||||
CommissionRecordQueryParams,
|
||||
MyCommissionRecordPageResult,
|
||||
MyCommissionSummary,
|
||||
SubmitWithdrawalParams,
|
||||
ShopCommissionRecordPageResult,
|
||||
ShopFundSummaryQueryParams,
|
||||
|
||||
@@ -1,74 +0,0 @@
|
||||
/**
|
||||
* 客户账号管理 API (企业账号)
|
||||
*
|
||||
* @deprecated 此 API 已废弃，请使用统一的 AccountService 代替
|
||||
* @see AccountService - 统一账号管理接口 (/api/admin/accounts)
|
||||
*
|
||||
* 迁移说明：
|
||||
* - 所有账号类型统一使用 /api/admin/accounts 接口
|
||||
* - 通过 user_type 参数区分账号类型 (2=平台, 3=代理, 4=企业)
|
||||
* - customer-accounts 已改名为 enterprise（企业账号）
|
||||
* - 详见：docs/迁移指南.md
|
||||
*/
|
||||
|
||||
import { BaseService } from '../BaseService'
|
||||
import type { BaseResponse } from '@/types/api'
|
||||
import type {
|
||||
CustomerAccountItem,
|
||||
CustomerAccountPageResult,
|
||||
CustomerAccountQueryParams,
|
||||
CreateCustomerAccountParams,
|
||||
UpdateCustomerAccountParams,
|
||||
UpdateCustomerAccountPasswordParams,
|
||||
UpdateCustomerAccountStatusParams
|
||||
} from '@/types/api/customerAccount'
|
||||
|
||||
export class CustomerAccountService extends BaseService {
|
||||
/**
|
||||
* 查询客户账号列表
|
||||
*/
|
||||
static getCustomerAccounts(
|
||||
params?: CustomerAccountQueryParams
|
||||
): Promise<BaseResponse<CustomerAccountPageResult>> {
|
||||
return this.get<BaseResponse<CustomerAccountPageResult>>('/api/admin/customer-accounts', params)
|
||||
}
|
||||
|
||||
/**
|
||||
* 新增代理商账号
|
||||
*/
|
||||
static createCustomerAccount(
|
||||
data: CreateCustomerAccountParams
|
||||
): Promise<BaseResponse<CustomerAccountItem>> {
|
||||
return this.post<BaseResponse<CustomerAccountItem>>('/api/admin/customer-accounts', data)
|
||||
}
|
||||
|
||||
/**
|
||||
* 编辑账号
|
||||
*/
|
||||
static updateCustomerAccount(
|
||||
id: number,
|
||||
data: UpdateCustomerAccountParams
|
||||
): Promise<BaseResponse<CustomerAccountItem>> {
|
||||
return this.put<BaseResponse<CustomerAccountItem>>(`/api/admin/customer-accounts/${id}`, data)
|
||||
}
|
||||
|
||||
/**
|
||||
* 修改账号密码
|
||||
*/
|
||||
static updateCustomerAccountPassword(
|
||||
id: number,
|
||||
data: UpdateCustomerAccountPasswordParams
|
||||
): Promise<BaseResponse> {
|
||||
return this.put<BaseResponse>(`/api/admin/customer-accounts/${id}/password`, data)
|
||||
}
|
||||
|
||||
/**
|
||||
* 修改账号状态
|
||||
*/
|
||||
static updateCustomerAccountStatus(
|
||||
id: number,
|
||||
data: UpdateCustomerAccountStatusParams
|
||||
): Promise<BaseResponse> {
|
||||
return this.put<BaseResponse>(`/api/admin/customer-accounts/${id}/status`, data)
|
||||
}
|
||||
}
|
||||
@@ -241,7 +241,7 @@ export class DeviceService extends BaseService {
|
||||
/**
|
||||
* 设置切卡模式
|
||||
* @param identifier 设备标识（虚拟号 / IMEI / SN）
|
||||
* @param switchMode 切卡模式（0=自动切卡，1=手动切卡）
|
||||
* @param data
|
||||
*/
|
||||
static setSwitchMode(
|
||||
identifier: string,
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user