Compare commits
203 Commits
868a3352ad
...
iteration/
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
8dec2b42f8 | ||
|
|
0d094a0537 | ||
|
|
c907d6e21f | ||
|
|
227dd63bb8 | ||
|
|
8fe65ca66d | ||
|
|
8b01169219 | ||
|
|
3411b66c71 | ||
|
|
984db9889c | ||
|
|
49a4d32eab | ||
|
|
d24506ab54 | ||
|
|
8569255f75 | ||
|
|
2f4eed917e | ||
|
|
1a1ec485a5 | ||
|
|
e41adb4505 | ||
|
|
2c8de04041 | ||
|
|
98a4be8719 | ||
|
|
f5730089a1 | ||
|
|
f2614d8efb | ||
|
|
06684e1fc0 | ||
|
|
049f8257fb | ||
|
|
ecce4f6e7b | ||
|
|
c706f543a4 | ||
|
|
d82e716d33 | ||
|
|
22e796ba23 | ||
|
|
6dedd9f852 | ||
|
|
7f3ff10fda | ||
|
|
eeeab03295 | ||
|
|
0d77a7d55b | ||
|
|
16effb69f3 | ||
|
|
c31183205d | ||
|
|
b2a76adc9a | ||
|
|
52268859aa | ||
|
|
f1006187f6 | ||
|
|
944f17ec3f | ||
|
|
633c88d0aa | ||
|
|
f61a3f84b6 | ||
|
|
327516dd40 | ||
|
|
2f23aeaaba | ||
|
|
2c64957e55 | ||
|
|
1a5f3d1e7d | ||
|
|
d02ce01f6a | ||
|
|
aec2a27a65 | ||
|
|
f896cad34f | ||
|
|
7a74bec337 | ||
|
|
5364916b1d | ||
|
|
6655638116 | ||
|
|
e79d599da1 | ||
|
|
015f990fb6 | ||
|
|
063337e6a3 | ||
|
|
c26d36154c | ||
|
|
669610a84a | ||
|
|
a26d7b4284 | ||
|
|
10fccc4def | ||
|
|
0a28b7d8ef | ||
|
|
c136f68ab8 | ||
|
|
c5d7a260d0 | ||
|
|
ffba959d45 | ||
|
|
9a6761e01d | ||
|
|
2c00341a7c | ||
| 5c1dc59579 | |||
| d52219b5c8 | |||
| bce5d6f270 | |||
| 42e57cf698 | |||
| 55eec78a90 | |||
| cb1561a317 | |||
|
|
94764b0e0a | ||
|
|
a6ce24f2f2 | ||
|
|
085a83d4e4 | ||
|
|
e37d4902ca | ||
|
|
08889d2e42 | ||
|
|
5e7f5eaba4 | ||
|
|
ac541b17af | ||
|
|
68d8f769d1 | ||
|
|
068d0c4ac2 | ||
|
|
9a3a764120 | ||
|
|
cea805f5d8 | ||
|
|
76d4e4ec02 | ||
|
|
2308d82d0f | ||
|
|
d3d257cdf8 | ||
|
|
ef966171b4 | ||
|
|
65cc63674e | ||
|
|
01cddd7eda | ||
|
|
a7b006076a | ||
|
|
c36c59e268 | ||
|
|
e56951d4b7 | ||
|
|
b5c58d695f | ||
|
|
6f6ac83b71 | ||
|
|
48e4adf3ff | ||
|
|
d335984c20 | ||
|
|
89e6d19d1f | ||
|
|
889ff3bc28 | ||
|
|
d8191f03a0 | ||
|
|
4d023e7666 | ||
|
|
fe357f56d9 | ||
|
|
2cb961fd1b | ||
|
|
4e3ea6c6d6 | ||
|
|
2d6948010b | ||
|
|
95abcb97ef | ||
|
|
d9d07422a9 | ||
|
|
93f67967c5 | ||
|
|
857d565f33 | ||
|
|
9a982e0446 | ||
|
|
737ade3a5e | ||
|
|
0d2a982f69 | ||
|
|
3dd17e9d7b | ||
|
|
ca748999ec | ||
|
|
e86f61f3f6 | ||
|
|
10ee87bf49 | ||
|
|
32635da58c | ||
|
|
8627d203cf | ||
|
|
41f3b61b62 | ||
|
|
33485b137f | ||
|
|
9599a4d52b | ||
|
|
8650b490d7 | ||
|
|
373ad4c2a5 | ||
|
|
9f7f619083 | ||
|
|
b8b2854aa6 | ||
|
|
fa3d7088f9 | ||
|
|
34455a9f18 | ||
|
|
db9aaa7920 | ||
|
|
1e740b1526 | ||
|
|
81d52892f5 | ||
|
|
06f39815db | ||
|
|
83f1c88c65 | ||
|
|
055fed0cf1 | ||
|
|
93ed3fbd63 | ||
|
|
17d2eeebc5 | ||
|
|
4394ae0f78 | ||
|
|
827de02f2b | ||
|
|
831f03c3a7 | ||
|
|
ee266c51cc | ||
|
|
b51a3f5537 | ||
|
|
261f5f2853 | ||
|
|
0e8a11430a | ||
|
|
2706c52a47 | ||
|
|
f0a2b84e53 | ||
|
|
cc6fc9243e | ||
|
|
dd6bceeeb7 | ||
|
|
ee508c3e1e | ||
|
|
9289a6e940 | ||
|
|
eb13763020 | ||
|
|
d1ff4d5f6c | ||
|
|
4c6d871c35 | ||
|
|
9a84cd0d31 | ||
|
|
e043fd86d1 | ||
|
|
a0c44ff538 | ||
|
|
15122e225a | ||
|
|
127fdb560b | ||
|
|
5e15127a89 | ||
|
|
d7c2c146fe | ||
|
|
3a819e86c9 | ||
|
|
e9c0e17d6a | ||
|
|
d5fd8ac564 | ||
|
|
7d3352038a | ||
|
|
8faa2ea2ef | ||
|
|
8de4339505 | ||
|
|
68aa03b538 | ||
|
|
fbfdd01eec | ||
|
|
5079f97326 | ||
|
|
830476d49d | ||
|
|
db7b3562da | ||
|
|
f52970ae6c | ||
|
|
47a2d88c9d | ||
|
|
6febc66eca | ||
|
|
45d255cabf | ||
|
|
eddfd157ad | ||
| 09225dd8bc | |||
| 563804f67f | |||
|
|
e95dc8e4f5 | ||
|
|
ca338dd345 | ||
|
|
fac05db39a | ||
|
|
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": []
|
||||
|
||||
18
.dockerignore
Normal file
18
.dockerignore
Normal file
@@ -0,0 +1,18 @@
|
||||
node_modules
|
||||
dist
|
||||
.git
|
||||
.gitea
|
||||
.husky
|
||||
.vscode
|
||||
.idea
|
||||
.DS_Store
|
||||
*.log
|
||||
npm-debug.log*
|
||||
yarn-debug.log*
|
||||
yarn-error.log*
|
||||
.env.local
|
||||
.env.*.local
|
||||
openspec
|
||||
.codex
|
||||
.claude
|
||||
.agents
|
||||
@@ -3,9 +3,12 @@ name: 构建并部署前端到测试环境
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
- iteration/8-11
|
||||
- dev
|
||||
- test
|
||||
# 如果不再需要 main 分支触发构建,可以把下面这行删掉;
|
||||
# 如果只是想保留构建(不部署),可以留着,反正部署条件已经只认 iteration/8-11
|
||||
- main
|
||||
|
||||
env:
|
||||
REGISTRY: registry.boss160.cn
|
||||
@@ -13,7 +16,7 @@ env:
|
||||
DEPLOY_DIR: /opt/junhong_cmp_web
|
||||
|
||||
jobs:
|
||||
build-and-deploy:
|
||||
deploy:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
@@ -24,67 +27,49 @@ jobs:
|
||||
git clone https://git.boss160.cn/luo/one-pipe-system.git .
|
||||
git checkout ${{ github.sha }}
|
||||
|
||||
- name: 设置镜像标签
|
||||
id: tag
|
||||
run: |
|
||||
if [ "${{ github.ref }}" = "refs/heads/main" ]; then
|
||||
echo "tag=latest" >> $GITHUB_OUTPUT
|
||||
elif [ "${{ github.ref }}" = "refs/heads/dev" ]; then
|
||||
echo "tag=dev" >> $GITHUB_OUTPUT
|
||||
elif [ "${{ github.ref }}" = "refs/heads/test" ]; then
|
||||
echo "tag=test" >> $GITHUB_OUTPUT
|
||||
else
|
||||
echo "tag=unknown" >> $GITHUB_OUTPUT
|
||||
fi
|
||||
|
||||
- name: 登录 Docker Registry
|
||||
run: |
|
||||
echo "${{ secrets.REGISTRY_PASSWORD }}" | docker login "${{ env.REGISTRY }}" --username "${{ secrets.REGISTRY_USERNAME }}" --password-stdin
|
||||
|
||||
- name: 构建前端镜像
|
||||
- name: 校验镜像存在
|
||||
run: |
|
||||
docker build -t ${{ env.IMAGE_NAME }}:${{ steps.tag.outputs.tag }} .
|
||||
docker tag ${{ env.IMAGE_NAME }}:${{ steps.tag.outputs.tag }} ${{ env.IMAGE_NAME }}:${{ github.sha }}
|
||||
if ! docker manifest inspect "${{ env.IMAGE_NAME }}:${{ github.sha }}" >/dev/null 2>&1; then
|
||||
echo "镜像不存在:${{ env.IMAGE_NAME }}:${{ github.sha }}"
|
||||
echo "请先在开发机完成 pre-push 镜像构建和推送"
|
||||
exit 1
|
||||
fi
|
||||
|
||||
- name: 推送镜像到 Registry
|
||||
- name: 部署到测试环境
|
||||
if: github.ref == 'refs/heads/iteration/8-11'
|
||||
run: |
|
||||
docker push ${{ env.IMAGE_NAME }}:${{ steps.tag.outputs.tag }}
|
||||
docker push ${{ env.IMAGE_NAME }}:${{ github.sha }}
|
||||
mkdir -p "${{ env.DEPLOY_DIR }}"
|
||||
cp -v docker-compose.prod.yml "${{ env.DEPLOY_DIR }}/"
|
||||
cd "${{ env.DEPLOY_DIR }}"
|
||||
|
||||
- name: 部署到本地(仅 main 分支)
|
||||
if: github.ref == 'refs/heads/main'
|
||||
run: |
|
||||
# 确保部署目录存在
|
||||
mkdir -p ${{ env.DEPLOY_DIR }}
|
||||
IMAGE_TAG=${{ github.sha }} docker compose -f docker-compose.prod.yml pull
|
||||
IMAGE_TAG=${{ github.sha }} docker compose -f docker-compose.prod.yml up -d
|
||||
|
||||
echo "当前工作目录: $(pwd)"
|
||||
echo "当前目录内容:"
|
||||
ls -la
|
||||
echo "等待服务健康检查通过..."
|
||||
for i in $(seq 1 30); do
|
||||
WEB_HEALTH=$(docker inspect junhong-cmp-web --format='{{if .State.Health}}{{.State.Health.Status}}{{else}}none{{end}}' 2>/dev/null || true)
|
||||
if [ "$WEB_HEALTH" = "healthy" ]; then
|
||||
break
|
||||
fi
|
||||
if [ "$i" -eq 30 ]; then
|
||||
echo "前端服务在等待窗口内未恢复健康"
|
||||
docker compose -f docker-compose.prod.yml logs web --tail=100
|
||||
exit 1
|
||||
fi
|
||||
sleep 2
|
||||
done
|
||||
|
||||
# 更新 docker-compose.prod.yml
|
||||
echo "更新部署配置文件..."
|
||||
cp -v docker-compose.prod.yml ${{ env.DEPLOY_DIR }}/
|
||||
|
||||
cd ${{ env.DEPLOY_DIR }}
|
||||
|
||||
echo "拉取最新镜像..."
|
||||
docker compose -f docker-compose.prod.yml pull
|
||||
|
||||
echo "重启服务..."
|
||||
docker compose -f docker-compose.prod.yml up -d
|
||||
|
||||
echo "等待服务启动..."
|
||||
sleep 5
|
||||
|
||||
echo "部署完成!"
|
||||
docker compose -f docker-compose.prod.yml ps
|
||||
IMAGE_TAG=${{ github.sha }} docker compose -f docker-compose.prod.yml ps
|
||||
|
||||
- name: 构建结果通知
|
||||
if: always()
|
||||
run: |
|
||||
if [ "${{ job.status }}" = "success" ]; then
|
||||
echo "构建成功: ${{ steps.tag.outputs.tag }}"
|
||||
echo "镜像标签: ${{ github.sha }}"
|
||||
echo "部署成功: ${{ github.sha }}"
|
||||
else
|
||||
echo "构建失败"
|
||||
echo "部署失败"
|
||||
fi
|
||||
|
||||
16
.gitignore
vendored
16
.gitignore
vendored
@@ -2,6 +2,13 @@ node_modules
|
||||
.DS_Store
|
||||
dist
|
||||
docs
|
||||
!docs/
|
||||
docs/*
|
||||
!docs/权限.md
|
||||
!docs/api/
|
||||
docs/api/*
|
||||
!docs/api/package-silence.openapi.json
|
||||
!docs/2026-10-26-轮询账户限流-后台接入交付.md
|
||||
dist-ssr
|
||||
*.local
|
||||
.cursorrules
|
||||
@@ -21,3 +28,12 @@ dist-ssr
|
||||
# Logs
|
||||
*.log
|
||||
npminstall-debug.log
|
||||
|
||||
# plan
|
||||
.scratch
|
||||
|
||||
# ai
|
||||
.agents
|
||||
|
||||
#build
|
||||
one-pipe-system-dist.zip
|
||||
|
||||
1
.husky/pre-push
Executable file
1
.husky/pre-push
Executable file
@@ -0,0 +1 @@
|
||||
node scripts/deploy-frontend.mjs --pre-push
|
||||
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
|
||||
13
Dockerfile
13
Dockerfile
@@ -6,15 +6,16 @@ FROM --platform=linux/amd64 node:20-alpine AS builder
|
||||
# 使用阿里云镜像源加速
|
||||
RUN sed -i 's/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g' /etc/apk/repositories
|
||||
|
||||
# 设置工作目录
|
||||
WORKDIR /build
|
||||
|
||||
# 安装 pnpm
|
||||
RUN corepack enable && corepack prepare pnpm@10.15.0 --activate
|
||||
|
||||
# 设置 npm 镜像源
|
||||
# 清除宿主机注入的失效代理,再安装 pnpm
|
||||
RUN npm config delete proxy && npm config delete https-proxy && npm install --global pnpm@10.15.0 --registry=https://registry.npmmirror.com
|
||||
RUN pnpm config set registry https://registry.npmmirror.com
|
||||
|
||||
# 限制 Node 堆,防止前端构建耗尽宿主机内存
|
||||
ARG NODE_OPTIONS=--max-old-space-size=1536
|
||||
ENV NODE_OPTIONS=${NODE_OPTIONS}
|
||||
|
||||
# 复制 package.json 和 pnpm-lock.yaml(利用 Docker 缓存)
|
||||
COPY package.json pnpm-lock.yaml ./
|
||||
|
||||
@@ -30,7 +31,7 @@ RUN pnpm run nd
|
||||
# ================================
|
||||
# 阶段 2: 运行阶段
|
||||
# ================================
|
||||
FROM --platform=linux/amd64 nginx:alpine
|
||||
FROM --platform=linux/amd64 nginx:1.31.2-alpine
|
||||
|
||||
# 使用阿里云镜像源加速
|
||||
RUN sed -i 's/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g' /etc/apk/repositories
|
||||
|
||||
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']
|
||||
|
||||
@@ -1,20 +1,25 @@
|
||||
version: '3.8'
|
||||
|
||||
services:
|
||||
web:
|
||||
image: registry.boss160.cn/junhong/cmp-admin-web:latest
|
||||
image: registry.boss160.cn/junhong/cmp-admin-web:${IMAGE_TAG:-latest}
|
||||
container_name: junhong-cmp-web
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- '3001:80'
|
||||
networks:
|
||||
- junhong-network
|
||||
|
||||
# === 以下是新增的修复内容 ===
|
||||
tmpfs:
|
||||
- /run:rw
|
||||
- /tmp:rw
|
||||
|
||||
healthcheck:
|
||||
test: ['CMD', 'wget', '--no-verbose', '--tries=1', '--spider', 'http://127.0.0.1:80/health']
|
||||
interval: 30s
|
||||
timeout: 3s
|
||||
retries: 3
|
||||
start_period: 5s
|
||||
|
||||
logging:
|
||||
driver: 'json-file'
|
||||
options:
|
||||
|
||||
128
docs/2026-10-26-轮询账户限流-后台接入交付.md
Normal file
128
docs/2026-10-26-轮询账户限流-后台接入交付.md
Normal file
@@ -0,0 +1,128 @@
|
||||
# 轮询账户限流:后台接入交付
|
||||
|
||||
本次仅修改本后台前端,未修改独立 C 端、未推送 Git 或部署生产、未配置数据库菜单。真实接口权限和调度行为仍需测试环境联调。本地写操作全部通过 mock 验证。
|
||||
|
||||
## 后台配置与使用
|
||||
|
||||
新增菜单、隐藏详情、按钮编码和平台账号限制见 [权限增量清单](./权限.md#轮询管理运营商账户限流与调度2026-10-26-增量)。原有网关、轮询配置预览/统计、停复机记录 URL 和权限保留。仅超级管理员的维护项不列入普通配置清单。
|
||||
|
||||
UI 沿用店铺列表表头、可选列、分页和店铺详情返回/标题/两列布局;窄屏详情单列。时间统一店铺格式,运营商账户按名称远程搜索,搜索条件 >=4 才出现展开。
|
||||
|
||||
新增配置字段现可保存,旧文档“仅预览”已失效。四项间隔:空继承、0 禁止且不再继承、正数执行。编辑清空使用 clear_fields,保存 warnings 单独展示;不再发送保护期间隔。
|
||||
|
||||
## C 端需要同步哪些
|
||||
|
||||
**必须修改(文档明确要求)**
|
||||
|
||||
1. C 端资产详情调用 `GET /api/c/v1/asset/info` 后,不再展示保护期状态(`device_protect_status`),包括标签、说明、倒计时和相关状态分支(如有)。
|
||||
2. 废弃字段可能仍返回固定 `none`,也可能缺失;兼容解析,但不能再依赖它决定页面展示或是否允许操作。不要把 `none` 当成新的异常状态。
|
||||
|
||||
**随新后端回归验证(不是要求 C 端增加后台功能)**
|
||||
|
||||
- 订单/套餐生效、有效期变化后,重新读取资产实际 `enable_polling`;后台可能自动恢复轮询,不要仅凭旧前端缓存维持“已关闭”。
|
||||
- 指令队列启用时,业务受理不等于上游已完成停复机。若 C 端有即时完成提示,改为区分“已受理/处理中”和实际状态,并在合理刷新后确认。
|
||||
- 资产详情读入口的请求检查、延迟确认及冷却由后端场景配置控制,C 端不要自行复制调度逻辑或高频循环触发。
|
||||
|
||||
C 端不需要新增本次后台菜单、告警/调度参数/导入接口;本仓库没有修改任何 C 端代码。若 C 端本来没有保护期 UI 或逻辑,第一项只需核查删除残留引用。
|
||||
|
||||
## 接口覆盖
|
||||
|
||||
文档 46 个新增操作中,已有 GatewayService 17 个、PollingConfigService 7 个,本次 PollingSchedulerService 补 22 个。自动测试逐条解析原文附录的 46 个方法/路径,与实际服务调用对照,不以数量代替路径验收。
|
||||
|
||||
下表路径省略 `/api/admin`。精确 URL、Query/Body 测试位于 `gateway.test.mjs`、`pollingConfigExtensions.test.mjs`、`pollingScheduler.test.mjs`。
|
||||
|
||||
| HTTP 操作 | 服务方法 | 后台入口 |
|
||||
| --- | --- | --- |
|
||||
| `DELETE /gateway-error-classifications/{id}` | `GatewayService.deleteRule` | 上游错误分类 |
|
||||
| `DELETE /polling-carrier-params/{carrier_id}` | `PollingSchedulerService.resetCarrierParam` | 账户参数维护 |
|
||||
| `DELETE /polling-rate-limit-groups/{id}` | `GatewayService.deleteGroup` | 网关限流组维护 |
|
||||
| `GET /card-polling-pauses` | `PollingSchedulerService.getPauses` | 不轮询清单 |
|
||||
| `GET /card-stop-resume-records` | `GatewayService.getRecords` | 停复机记录 |
|
||||
| `GET /gateway-error-classifications` | `GatewayService.getRules` | 上游错误分类 |
|
||||
| `GET /iot-cards/{id}/polling-state` | `PollingSchedulerService.getCardState` | 单卡/设备绑定卡/告警详情 |
|
||||
| `GET /iot-cards/{id}/stop-resume-records` | `GatewayService.getCardRecords` | 单卡/告警详情 |
|
||||
| `GET /polling-carrier-params` | `PollingSchedulerService.getCarrierParams` | 运营商账户调度参数 |
|
||||
| `GET /polling-carrier-params/{carrier_id}` | `PollingSchedulerService.getCarrierParam` | 账户参数详情 |
|
||||
| `GET /polling-check-scenes` | `PollingSchedulerService.getScenes` | 请求检查场景 |
|
||||
| `GET /polling-configs/match-preview` | `PollingConfigService.previewMatch` | 配置匹配预览 |
|
||||
| `GET /polling-configs/recalculate-due/{task_id}` | `PollingConfigService.getRecalculateTask` | 重算进度 |
|
||||
| `GET /polling-failure-alerts` | `PollingSchedulerService.getAlerts` | 告警普通/停机被拒 |
|
||||
| `GET /polling-failure-alerts/summary` | `PollingSchedulerService.getAlertSummary` | 告警账户汇总 |
|
||||
| `GET /polling-failure-alerts/{id}` | `PollingSchedulerService.getAlert` | 告警详情 |
|
||||
| `GET /polling-options` | `GatewayService.getOptions` | 网关各页枚举 |
|
||||
| `GET /polling-rate-limit-groups` | `GatewayService.getGroups` | 网关限流组 |
|
||||
| `GET /polling-rate-limit-groups/{id}` | `GatewayService.getGroup` | 网关限流组详情 |
|
||||
| `GET /polling-stats/carrier-queues` | `PollingSchedulerService.getQueues` | 账户队列监控 |
|
||||
| `GET /polling-stats/carriers` | `GatewayService.getCarrierStats` | 网关汇总/限流模式 |
|
||||
| `GET /polling-stats/carriers/{carrier_id}/trend` | `GatewayService.getCarrierTrend` | 账户调用趋势 |
|
||||
| `GET /polling-stats/pre-reset` | `PollingConfigService.getPreResetStats` | 重置日前统计 |
|
||||
| `GET /polling-stats/tiers` | `PollingConfigService.getTierStats` | 分层统计 |
|
||||
| `GET /polling-status-imports` | `PollingSchedulerService.getImports` | 导入任务列表 |
|
||||
| `GET /polling-status-imports/{id}` | `PollingSchedulerService.getImport` | 导入逐行结果 |
|
||||
| `GET /polling-status/impact` | `PollingSchedulerService.getImpact` | 单项/批量/导入确认 |
|
||||
| `GET /stop-resume-rule/dry-run` | `PollingSchedulerService.dryRun` | 规则演练(只读) |
|
||||
| `POST /devices/batch-update-polling-status` | `PollingSchedulerService.toggleDevices` | 设备批量/清单恢复 |
|
||||
| `POST /gateway-error-classifications` | `GatewayService.createRule` | 上游错误分类 |
|
||||
| `POST /gateway-error-classifications/test` | `GatewayService.testRule` | 错误分类测试 |
|
||||
| `POST /iot-cards/batch-update-polling-status` | `PollingSchedulerService.toggleCards` | 卡批量/清单恢复 |
|
||||
| `POST /polling-configs/match-preview` | `PollingConfigService.previewDraft` | 配置草稿预览 |
|
||||
| `POST /polling-configs/recalculate-due` | `PollingConfigService.recalculateDue` | 重算到期 |
|
||||
| `POST /polling-failure-alerts/close-polling` | `PollingSchedulerService.closeAlertPolling` | 告警批量关闭卡轮询 |
|
||||
| `POST /polling-rate-limit-groups` | `GatewayService.createGroup` | 网关限流组维护 |
|
||||
| `POST /polling-status-imports` | `PollingSchedulerService.createImport` | 创建导入 |
|
||||
| `POST /stop-resume-rule/dry-run/export` | `PollingSchedulerService.exportDryRun` | 演练导出 |
|
||||
| `PUT /gateway-error-classifications/{id}` | `GatewayService.updateRule` | 上游错误分类 |
|
||||
| `PUT /gateway-error-classifications/{id}/status` | `GatewayService.setRuleStatus` | 上游错误分类 |
|
||||
| `PUT /polling-carrier-params/{carrier_id}` | `PollingSchedulerService.saveCarrierParam` | 账户参数维护 |
|
||||
| `PUT /polling-check-scenes/{scene}` | `PollingSchedulerService.saveScene` | 请求检查场景维护 |
|
||||
| `PUT /polling-configs/priorities` | `PollingConfigService.updatePriorities` | 整体优先级(拖动/上移下移) |
|
||||
| `PUT /polling-failure-alerts/{id}/status` | `PollingSchedulerService.handleAlert` | 告警处理 |
|
||||
| `PUT /polling-rate-limit-groups/{id}` | `GatewayService.updateGroup` | 网关限流组维护 |
|
||||
| `PUT /polling-rate-limit-groups/{id}/status` | `GatewayService.setGroupStatus` | 网关限流组维护 |
|
||||
|
||||
### 16 个既有接口改动的处理
|
||||
|
||||
| 既有接口 | 接入结果 |
|
||||
| --- | --- |
|
||||
| GET /polling-configs | 列表新增资产/套餐条件、重置日前窗口和间隔列 |
|
||||
| GET /polling-configs/:id | 编辑读入全部新增字段,废弃保护间隔不再参与 |
|
||||
| POST /polling-configs | 白名单保存新增匹配及窗口字段、三态间隔,展示 warnings |
|
||||
| PUT /polling-configs/:id | clear_fields 显式清空,0 保留,展示 warnings |
|
||||
| GET /assets/resolve/:identifier | 不再映射废弃保护期展示;其余资产身份不变 |
|
||||
| GET /assets/:identifier/realtime-status | 不再更新保护期 UI 字段 |
|
||||
| POST /assets/:identifier/refresh | 沿用刷新读取,界面无保护期展示 |
|
||||
| GET /api/c/v1/asset/info | 独立 C 端同步项,本仓库不改 |
|
||||
| PUT /carriers/:id | 0→1 首次不带确认;展示后端实际影响后确认重提 |
|
||||
| GET /system-configs | 新增 polling 模块,复用 string/int/bool/json 编辑与校验 |
|
||||
| GET /iot-cards/standalone | 三态是否轮询筛选,保留 false |
|
||||
| GET /devices | 新增筛选与是否轮询列 |
|
||||
| PATCH /assets/:identifier/polling-status | 先读 impact 确认,拒绝/取消恢复 UI,不提供强制参数 |
|
||||
| POST /storage/upload-url | purpose=polling_status_import;校验 key 前缀后上传,成功才建任务 |
|
||||
| POST /export-tasks | 三个新增场景;卡/设备保留 enable_polling 筛选 |
|
||||
| GET /export-tasks | 三个场景列表、共用详情与下载权限;历史文件不做客户端改写 |
|
||||
|
||||
`PUT /system-configs/:key` 继续走原编辑能力,新增键来自服务器;本次不会自动修改 scheduler、rate_limit_mode、queue_enabled。
|
||||
|
||||
## 验证与限制
|
||||
|
||||
本地复现:
|
||||
|
||||
```powershell
|
||||
$tests = @(rg --files scripts/tests -g '*.test.mjs')
|
||||
node --import ./scripts/tests/register-esbuild.mjs --test $tests
|
||||
.\node_modules\.bin\vue-tsc.cmd --noEmit
|
||||
node scripts/tests/verifyBuild.mjs
|
||||
node scripts/tests/verifyBuild.mjs --serve --scheduler
|
||||
```
|
||||
|
||||
最后一项在 `http://127.0.0.1:5190` 启动本地 mock,所有 /api 被拦截;可使用 local-scheduler-platform/admin/agent/enterprise 模拟 token。该结果不等于线上后端已联调。
|
||||
|
||||
已覆盖:46 路径映射、22 新方法请求结构、null/0/false、清空与废弃字段、权限/身份、500 条和 CSV 50000 行边界、引号换行、部分成功、影响说明失败/取消、上传失败、迟到请求/账号范围切换/卸载、模板编译。旧实名管控回归改成后端实际文案确认。
|
||||
|
||||
生产构建的既有循环依赖、常量 v-model 和大 chunk 警告仍存在;未在本次跨范围重构。后端若将实名确认提示升级为独立错误码,可替换当前的语义识别,避免依赖提示中的“实名/确认”关键词。当前未知网络错误或不相关错误不会触发确认重试。
|
||||
|
||||
2026-10-26 最终回归:全量 191 项通过(本次调度接入新增 17 项,保留并升级原有回归)。类型检查、生产构建、针对性 ESLint / Prettier / 新增组件样式检查、全仓 UTF-8 编码检查通过。
|
||||
|
||||
浏览器使用本地 mock 验证了平台账号入口、特殊告警视图、批量 impact 确认与四类逐项结果、CSV 上传建任务/详情、演练汇总与明细、时间格式、网关 80% 成功率及 p95 超桶显示;检查了浅/深色与 375/390/768/1024/1440 宽度布局。开发热更新仍可能遇到项目既有 API 循环依赖,刷新后进行验收,不把热更新错误当作真实接口结果。
|
||||
|
||||
真实后端账号、数据范围、错误码、异步终态和导出文件内容需由部署后的联调确认;本次未进行线上写入、Git 推送或部署。
|
||||
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 单点登录
|
||||
- [ ] 添加第三方登录(微信、钉钉等)
|
||||
- [ ] 完善密码强度检测
|
||||
- [ ] 添加登录日志记录
|
||||
4390
docs/api/package-silence.openapi.json
Normal file
4390
docs/api/package-silence.openapi.json
Normal file
File diff suppressed because it is too large
Load Diff
@@ -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
|
||||
}
|
||||
437
docs/权限.md
Normal file
437
docs/权限.md
Normal file
@@ -0,0 +1,437 @@
|
||||
# 权限清单
|
||||
|
||||
## 套餐管理:真流量预警规则
|
||||
|
||||
页面 URL:`/package-management/traffic-alert-rules`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| -------- | ------------- | ------------------------------------ |
|
||||
| 页面查看 | `rulesView` | `package_traffic_alert:rules_view` |
|
||||
| 新增规则 | `ruleCreate` | `package_traffic_alert:rule_create` |
|
||||
| 编辑规则 | `ruleUpdate` | `package_traffic_alert:rule_update` |
|
||||
| 启用规则 | `ruleEnable` | `package_traffic_alert:rule_enable` |
|
||||
| 停用规则 | `ruleDisable` | `package_traffic_alert:rule_disable` |
|
||||
|
||||
启用和停用不得复用编辑权限。
|
||||
|
||||
## 套餐管理:真流量达量预警
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 预警列表 | `/package-management/traffic-alerts` | `recordsView` | `package_traffic_alert:records_view` |
|
||||
| 点击套餐名称进入预警详情 | `/package-management/traffic-alerts/detail/:id` | `recordDetail` | `package_traffic_alert:record_detail` |
|
||||
| 导出预警记录 | — | `export` | `package_traffic_alert:export` |
|
||||
| 导出任务页面 | `/asset-management/export-task-management/export-package-traffic-alert` | `page` | `export_task:package_traffic_alert_page` |
|
||||
|
||||
## 店铺管理:店铺列表
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 店铺列表 | `/shop-management/list` | `listView` | `shop:list_view` |
|
||||
| 店铺详情 | `/shop-management/detail/:id` | `detailView` | `shop:detail_view` |
|
||||
| 新增店铺 | — | — | `shop:add` |
|
||||
| 批量交接 | — | `batch` | `shop:business_owner_batch` |
|
||||
| 导入业务员 | — | `importPage` | `shop:business_owner_import_view` |
|
||||
| 查看店铺详情 | — | — | `shop:detail` |
|
||||
| 切换店铺状态 | — | — | `shop:modify_status` |
|
||||
| 账号列表 | — | — | `shop:look_customer` |
|
||||
| 默认角色 | — | — | `shop:default_role` |
|
||||
| 调整实际信用额度 | — | — | `shop:credit_limit_manage` |
|
||||
| 编辑店铺 | — | — | `shop:edit` |
|
||||
| 删除店铺 | — | — | `shop:delete` |
|
||||
| 审计记录 | — | — | `audit:shop_entry` / `audit:agent_resource_activity` |
|
||||
| 资金链路 | — | — | `audit:finance_timeline` |
|
||||
|
||||
## 店铺管理:业务用户组
|
||||
|
||||
页面 URL:`/shop-management/business-user-groups`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| -------- | --------- | ----------------------------- |
|
||||
| 页面查看 | `page` | `business_user_group:page` |
|
||||
| 新增 | `create` | `business_user_group:create` |
|
||||
| 编辑 | `update` | `business_user_group:update` |
|
||||
| 删除 | `delete` | `business_user_group:delete` |
|
||||
| 成员管理 | `members` | `business_user_group:members` |
|
||||
|
||||
## 店铺管理:批量换绑业务员
|
||||
|
||||
页面 URL:`/shop-management/business-owner-import`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| ---------------------------- | -------------- | ----------------------------------- |
|
||||
| 页面查看 | `importPage` | `shop:business_owner_import_view` |
|
||||
| 创建导入任务 | `importCreate` | `shop:business_owner_import_create` |
|
||||
| 详情按钮 | `importDetail` | `shop:business_owner_import_detail` |
|
||||
| 详情页面(当前为列表页抽屉) | `importDetail` | `shop:business_owner_import_detail` |
|
||||
|
||||
## 店铺管理:代理注册申请
|
||||
|
||||
列表不显示操作列,点击“申请店铺”名称进入详情页。
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 申请列表 | `/shop-management/agent-distribution-registrations` | `list` | `agent_distribution_registration:list` |
|
||||
| 申请详情 | `/shop-management/agent-distribution-registrations/detail/:id` | `detail` | `agent_distribution_registration:detail` |
|
||||
| 恢复审批 | — | `recoverApproval` | `agent_distribution_registration:recover_approval` |
|
||||
|
||||
## 资产管理:手机号资产关联
|
||||
|
||||
页面 URL:`/asset-management/phone-asset-association`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| ---------------- | -------------------- | ---------------------------------------------- |
|
||||
| 页面查看 | `list` | `phone_asset_association:list` |
|
||||
| 单条解绑 | `unbind` | `phone_asset_association:unbind` |
|
||||
| 批量解绑 | `unbindBatch` | `phone_asset_association:unbind_batch` |
|
||||
| 解绑导入页面 | `unbindImportPage` | `phone_asset_association:unbind_import_view` |
|
||||
| 创建解绑导入任务 | `unbindImportCreate` | `phone_asset_association:unbind_import_create` |
|
||||
|
||||
## 资产管理:解绑导入任务
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 任务列表 | `/asset-management/task-management/phone-asset-unbind-import-tasks` | `unbindImportPage` | `phone_asset_association:unbind_import_page` |
|
||||
| 任务详情 | `/asset-management/task-management/phone-asset-unbind-import-tasks/detail` | `unbindImportDetail` | `phone_asset_association:unbind_import_detail` |
|
||||
| 详情按钮 | — | `unbindImportDetail` | `asset_association:unbind_import_detail` |
|
||||
|
||||
## 资产管理:临期资产
|
||||
|
||||
页面 URL:`/asset-management/expiring-assets`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| -------- | -------- | ----------------------- |
|
||||
| 页面查看 | `page` | `expiring_asset:page` |
|
||||
| 导出 | `export` | `expiring_asset:export` |
|
||||
|
||||
## 资产管理:导出任务页面
|
||||
|
||||
详情按钮为导出任务列表中的任务编号点击入口,权限编码按导出场景区分;详情页面统一使用 `id` 查询参数。
|
||||
|
||||
| 导出场景 | 列表页面 URL | 页面权限编码 | 详情按钮权限编码 | 详情页面 URL |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| 设备 | `/asset-management/export-task-management/export-device` | `export_task:device_page` | `export_task:device_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| IoT 卡 | `/asset-management/export-task-management/export-iot-card` | `export_task:iot_card_page` | `export_task:iot_card_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 订单 | `/asset-management/export-task-management/export-order` | `export_task:order_page` | `export_task:order_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 套餐 | `/asset-management/export-task-management/export-package` | `export_task:package_page` | `export_task:package_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 代理主钱包流水 | `/asset-management/export-task-management/export-agent-wallet-transaction` | `export_task:agent_wallet_transaction_page` | `export_task:agent_wallet_transaction_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 代理充值 | `/asset-management/export-task-management/export-agent-recharge` | `export_task:agent_recharge_page` | `export_task:agent_recharge_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 退款 | `/asset-management/export-task-management/export-refund` | `export_task:refund_page` | `export_task:refund_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 换货 | `/asset-management/export-task-management/export-exchange` | `export_task:exchange_page` | `export_task:exchange_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 佣金明细 | `/asset-management/export-task-management/export-commission-record` | `export_task:commission_record_page` | `export_task:commission_record_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 套餐真流量达量预警 | `/asset-management/export-task-management/export-package-traffic-alert` | `export_task:package_traffic_alert_page` | `export_task:package_traffic_alert_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 临期资产 | `/asset-management/export-task-management/export-expiring-asset` | `export_task:expiring_asset_page` | `export_task:expiring_asset_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 设备激活报表 | `/asset-management/export-task-management/export-operations-activation` | `export_task:operations_activation_page` | `export_task:operations_activation_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
| 套餐续费报表 | `/asset-management/export-task-management/export-operations-renewal` | `export_task:operations_renewal_page` | `export_task:operations_renewal_detail` | `/asset-management/export-task-management/export-task-detail?id=:id` |
|
||||
|
||||
## 财务管理:退款管理
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --------- | ---------------------------- | ----------------- | ------------------------- |
|
||||
| 退款列表 | `/finance/refund` | `page` | `refund:page` |
|
||||
| 退款详情 | `/finance/refund/detail/:id` | `detailPage` | `refund:detail_page` |
|
||||
| 恢复审批 | — | `recoverApproval` | `refund:recover_approval` |
|
||||
|
||||
## 财务管理:员工代收款账单
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 账单列表 | `/finance/employee-collection/bills` | `billPage` | `employee_collection:bill_view` |
|
||||
| 账单详情 | `/finance/employee-collection/bills/detail/:id` | `billDetail` | `employee_collection:bill_detail` |
|
||||
| 创建核销申请 | — | `applicationCreate` | `employee_collection:application_create` |
|
||||
| 关闭账单 | — | `billClose` | `employee_collection:bill_close` |
|
||||
|
||||
## 财务管理:核销申请
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 申请列表 | `/finance/employee-collection/applications` | `applicationPage` | `employee_collection:application_view` |
|
||||
| 申请详情 | `/finance/employee-collection/applications/detail/:id` | `applicationDetail` | `employee_collection:application_detail` |
|
||||
| 修改并重新提交 | — | `applicationUpdate` | `employee_collection:application_update` |
|
||||
| 查看凭证 | — | `applicationViewVoucher` | `employee_collection:application_view_voucher` |
|
||||
| 恢复审批 | — | `applicationRecoverApproval` | `employee_collection:application_recover_approval` |
|
||||
|
||||
## 财务管理:收款方式管理
|
||||
|
||||
页面 URL:`/finance/employee-collection/payment-methods`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| -------- | --------------------- | ------------------------------------------- |
|
||||
| 页面查看 | `paymentMethodPage` | `employee_collection:payment_method_view` |
|
||||
| 新增 | `paymentMethodCreate` | `employee_collection:payment_method_create` |
|
||||
| 编辑 | `paymentMethodEdit` | `employee_collection:payment_method_edit` |
|
||||
| 删除 | `paymentMethodDelete` | `employee_collection:payment_method_delete` |
|
||||
|
||||
## 财务管理:代理商资金概况
|
||||
|
||||
页面 URL:`/finance/agent-fund-overview`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| ------------ | ------------------ | --------------------------------------- |
|
||||
| 页面查看 | `page` | `agent_fund_overview:page` |
|
||||
| 佣金明细导出 | `commissionExport` | `agent_fund_overview:commission_export` |
|
||||
|
||||
## 设置:商户池管理
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 管理页面 | `/settings/payment-merchant-pools` | `page` | `payment_merchant_pool:page` |
|
||||
| 商户详情 | `/settings/payment-merchant-pools/detail/:id` | `merchantDetail` | `payment_merchant_pool:merchant_detail` |
|
||||
| 商户池详情 | `/settings/payment-merchant-pools/pool-detail/:id` | `poolDetail` | `payment_merchant_pool:pool_detail` |
|
||||
| 新增/编辑/启停/删除商户 | — | — | `payment_merchant_pool:merchant_create` / `merchant_edit` / `merchant_toggle` / `merchant_delete` |
|
||||
| 新增/编辑/启停商户池 | — | — | `payment_merchant_pool:pool_create` / `pool_edit` / `pool_toggle` |
|
||||
| 保存微信授权配置 | — | `wechatAuthEdit` | `payment_merchant_pool:wechat_auth_edit` |
|
||||
|
||||
## 设置:H5运营弹窗配置
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 配置列表 | `/settings/h5-popup-configuration` | `list` | `h5_popup_configuration:list` |
|
||||
| 配置详情 | `/settings/h5-popup-configuration/detail/:id` | `detail` | `h5_popup_configuration:detail` |
|
||||
| 新增/编辑/启用/停用 | — | — | `h5_popup_configuration:create` / `update` / `enable` / `disable` |
|
||||
|
||||
## 设置:资产钱包自动续费
|
||||
|
||||
| 页面/操作 | URL | 权限名称 | 权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 页面查看 | `/settings/asset-wallet-auto-renewal` | `page` | `asset_wallet_auto_renewal:page` |
|
||||
| 保存配置 | — | `update` | `asset_wallet_auto_renewal:update` |
|
||||
|
||||
## 轮询管理:优先队列
|
||||
|
||||
页面 URL:`/polling-management/priority-queue`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| ------------ | -------- | ------------------------------- |
|
||||
| 页面查看 | `page` | `polling_priority_queue:page` |
|
||||
| 人工优先入队 | `create` | `polling_priority_queue:create` |
|
||||
| 查看详情 | `detail` | `polling_priority_queue:detail` |
|
||||
|
||||
## 运营报表:设备激活报表
|
||||
|
||||
页面 URL:`/operations-reports/activation`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| -------- | ------------------ | -------------------------------------- |
|
||||
| 页面查看 | `activationPage` | `operations_reports:activation_page` |
|
||||
| 导出 | `activationExport` | `operations_reports:activation_export` |
|
||||
|
||||
## 运营报表:套餐续费报表
|
||||
|
||||
页面 URL:`/operations-reports/renewal`
|
||||
|
||||
| 类型 | 权限名称 | 权限编码 |
|
||||
| -------- | --------------- | ----------------------------------- |
|
||||
| 页面查看 | `renewalPage` | `operations_reports:renewal_page` |
|
||||
| 导出 | `renewalExport` | `operations_reports:renewal_export` |
|
||||
|
||||
## 通用:导出任务详情
|
||||
|
||||
页面 URL:`/asset-management/export-task-management/export-task-detail`
|
||||
|
||||
- 页面权限:`export_task:detail_page`
|
||||
- 各场景详情权限:`export_task:<scene>_detail`
|
||||
- 各场景下载权限:`export_task:<scene>_download`
|
||||
|
||||
所有权限编码必须保持唯一;页面 URL 权限与按钮权限应分别定义。
|
||||
|
||||
## 轮询管理:网关限流
|
||||
|
||||
以下仅列普通账号需要配置的项。父菜单为已有「轮询管理」`/polling-management`,无需新增一级菜单。
|
||||
|
||||
| 菜单名称 | URL | 父菜单 | 菜单权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 停复机记录 | `/polling-management/stop-resume-records` | 轮询管理 | `card_stop_resume_record:page` |
|
||||
| 上游错误分类 | `/polling-management/error-classifications` | 轮询管理 | `gateway_error_classification:page` |
|
||||
| 网关限流组 | `/polling-management/rate-limit-groups` | 轮询管理 | `gateway_rate_limit_group:page` |
|
||||
| 网关调用统计 | `/polling-management/gateway-stats` | 轮询管理 | `gateway_call_stats:page` |
|
||||
| 网关限流组详情(隐藏) | `/polling-management/rate-limit-groups/detail/:id` | 轮询管理 | `gateway_rate_limit_group:detail_page` |
|
||||
|
||||
详情为轮询管理下的同级隐藏路由,不挂在列表组件下。`:id` 保留路由参数形式;普通账号需同时获得该隐藏菜单与「查看详情」按钮授权。
|
||||
|
||||
| 按钮名称 | 所属菜单/位置 | 按钮权限编码 |
|
||||
| --- | --- | --- |
|
||||
| 测试分类 / 草稿测试 | 上游错误分类 | `gateway_error_classification:test` |
|
||||
| 查看详情 | 网关限流组 | `gateway_rate_limit_group:detail` |
|
||||
| 查询趋势 | 网关调用统计 | `gateway_call_stats:trend` |
|
||||
| 停复机记录 | 资产管理 → 单卡信息,卡信息头部 | `iot_info:stop_resume_records` |
|
||||
| 停复机记录 | 资产管理 → 单卡信息,设备绑定卡操作区 | `device_info:stop_resume_records` |
|
||||
|
||||
查询、重置、分页与刷新使用页面权限,无需另配按钮。运营商名称搜索下拉需要当前账号能读取 `/api/admin/carriers`;这些前端编码不替代后端独立鉴权。
|
||||
|
||||
## 轮询管理:轮询配置预览与统计
|
||||
|
||||
本次只需新增一个菜单;已有「轮询配置」`/polling-management/config` 保留,不改旧 CRUD 权限。以下仅列普通账号需要配置的项。
|
||||
|
||||
| 菜单名称 | URL | 父菜单 | 菜单权限编码 |
|
||||
| --- | --- | --- | --- |
|
||||
| 轮询配置统计 | `/polling-management/config-stats` | 轮询管理 `/polling-management` | `polling_config_stats:page` |
|
||||
|
||||
| 按钮名称 | 所属菜单 | 按钮权限编码 |
|
||||
| --- | --- | --- |
|
||||
| 匹配预览 / 草稿预览 / 预览未保存修改 | 轮询配置 `/polling-management/config` | `polling_config:match_preview` |
|
||||
| 查询重算进度 | 轮询配置 `/polling-management/config` | `polling_config:recalculate_progress` |
|
||||
| 查看重置日前加密查流量效果统计 | 轮询配置统计 | `polling_config_stats:pre_reset` |
|
||||
| 查看分层轮询统计 | 轮询配置统计 | `polling_config_stats:tiers` |
|
||||
|
||||
统计菜单权限和区域权限需同时授权;若仅授权其中一个统计区域,另一区域不会请求接口。进度查询权限只允许查询已有任务,不授予创建任务的能力。上述编码是前端配置约定,后端独立鉴权。
|
||||
|
||||
### 接入说明
|
||||
|
||||
- 当前配置预览使用 GET;草稿预览使用 POST,并在 Query 和 Body 同时传入同一 ICCID。多条草稿可覆盖已有配置或以 id=0 新增,预览不调用持久化 CRUD。
|
||||
- 草稿中实名、流量、套餐、卡状态检查区分继承(null)、禁止且不再继承(0)、指定秒数(正数)。保护期已下线,表单和请求均移除。重置日前加密需明确开启,窗口和窗口内流量间隔成对设置。
|
||||
- 以 2026-10-26 完整接口文档为准:资产状态、套餐状态、重置日前窗口字段现已支持创建/编辑保存;编辑清空通过 `clear_fields`,保存成功展示 `warnings`。
|
||||
- 时间使用与店铺列表相同的 `formatDateTime`。运营商账户按名称远程搜索,仍提交数字 ID;搜索条件 >=4 时才显示展开按钮。
|
||||
- 任务进度每 3 秒查询一次,终态、失败、关闭、路由离开和卸载后停止;保留真实 task_id、任务状态及 string 类型的响应账户 ID。
|
||||
- 统计周期为 null 时显示「无周期数据」,真实 0 保留。分层统计标明 5 分钟缓存,未匹配配置的在库卡和已销售无套餐卡突出告警;刷新不宣称清除服务器缓存。
|
||||
|
||||
### 本地验证
|
||||
|
||||
```powershell
|
||||
node --test scripts/tests/pollingConfigExtensions.test.mjs
|
||||
.\node_modules\.bin\vue-tsc.cmd --noEmit
|
||||
node scripts/tests/verifyBuild.mjs
|
||||
node scripts/tests/verifyBuild.mjs --serve --polling
|
||||
```
|
||||
|
||||
最后一条命令启动 `http://127.0.0.1:5190` 的本地模拟接口页面;所有 `/api` 请求被拦截,不会对真实后端保存配置或创建任务。当前未进行真实后端联调、菜单数据写入、Git 推送或生产部署。
|
||||
|
||||
2026-10-26 验证:新增轮询配置测试 20 项、全量回归 174 项通过;类型、生产构建、针对性 lint / 格式 / 编码检查通过。浏览器验证了当前预览、草稿控件、异步进度、空周期/零值统计、普通账号入口及小屏布局。生产构建仍有项目既有循环依赖、其他页面常量绑定与大 chunk 警告。
|
||||
|
||||
## 轮询管理:运营商账户限流与调度(2026-10-26 增量)
|
||||
|
||||
本节在前两次配置的基础上新增,旧菜单和旧权限不必重建。仅列非超级管理员专属的菜单/按钮;标注“平台”的项只允许 user_type=1/2,权限码不能突破身份限制。前端编码是本项目约定,后端仍需独立授权。
|
||||
|
||||
### 新增可见菜单
|
||||
|
||||
| 菜单名称 | URL | 父菜单 | 菜单权限 |
|
||||
| --- | --- | --- | --- |
|
||||
| 运营商账户调度参数 | `/polling-management/carrier-params` | 轮询管理 `/polling-management` | `polling_carrier_params:page` |
|
||||
| 请求检查场景 | `/polling-management/check-scenes` | 轮询管理 | `polling_check_scene:page` |
|
||||
| 失败告警 | `/polling-management/failure-alerts` | 轮询管理 | `polling_failure_alert:page` |
|
||||
| 账户队列监控 | `/polling-management/carrier-queues` | 轮询管理 | `polling_carrier_queue:page` |
|
||||
| 停复机规则演练(平台) | `/polling-management/stop-resume-dry-run` | 轮询管理 | `stop_resume_dry_run:page` |
|
||||
| 不轮询清单(平台) | `/polling-management/polling-pauses` | 轮询管理 | `polling_pause:page` |
|
||||
| 轮询开关导入(平台) | `/polling-management/polling-status-imports` | 轮询管理 | `polling_status_import:page` |
|
||||
| 导出不轮询清单(平台) | `/asset-management/export-task-management/export-polling-pause` | 导出管理 `/asset-management/export-task-management` | `export_task:polling_pause_page` |
|
||||
| 导出停机被拒告警(平台) | `/asset-management/export-task-management/export-polling-stop-refused-alert` | 导出管理 | `export_task:polling_stop_refused_alert_page` |
|
||||
| 导出停复机规则演练(平台) | `/asset-management/export-task-management/export-stop-resume-rule-dry-run` | 导出管理 | `export_task:stop_resume_rule_dry_run_page` |
|
||||
|
||||
### 新增隐藏详情菜单
|
||||
|
||||
这些是独立页面,不是按钮编码,需配置隐藏路由;URL 参数保留,不替换为具体 ID。
|
||||
|
||||
| 菜单名称 | URL | 父菜单 | 菜单权限 |
|
||||
| --- | --- | --- | --- |
|
||||
| 运营商账户调度参数详情 | `/polling-management/carrier-params/detail/:carrier_id` | 轮询管理 | `polling_carrier_params:detail_page` |
|
||||
| 失败告警详情 | `/polling-management/failure-alerts/detail/:id` | 轮询管理 | `polling_failure_alert:detail_page` |
|
||||
| 轮询开关导入详情(平台) | `/polling-management/polling-status-imports/detail/:id` | 轮询管理 | `polling_status_import:detail_page` |
|
||||
|
||||
三个导出场景共用已有隐藏详情 `/asset-management/export-task-management/export-task-detail?id=任务ID`,沿用 `export_task:detail_page`,不再新增详情路由。
|
||||
|
||||
### 新增按钮权限编码
|
||||
|
||||
| 所属页面 | 按钮/能力 | 编码 |
|
||||
| --- | --- | --- |
|
||||
| 运营商账户调度参数 | 查看详情 | `polling_carrier_params:detail` |
|
||||
| 失败告警 | 查看详情 | `polling_failure_alert:detail` |
|
||||
| 失败告警 | 账户汇总 | `polling_failure_alert:summary` |
|
||||
| 失败告警 | 标记已处理(仅未处理状态) | `polling_failure_alert:handle` |
|
||||
| 失败告警 | 批量关闭卡轮询(平台) | `polling_failure_alert:close_polling` |
|
||||
| 失败告警 | 导出停机被拒(平台) | `polling_failure_alert:export` |
|
||||
| 停复机规则演练 | 导出演练明细(平台) | `stop_resume_dry_run:export` |
|
||||
| 不轮询清单 | 批量开启轮询(平台) | `polling_pause:restore` |
|
||||
| 不轮询清单 | 创建导出任务(平台) | `polling_pause:export` |
|
||||
| 轮询开关导入 | 上传并创建任务(平台) | `polling_status_import:create` |
|
||||
| 轮询开关导入 | 查看任务与逐行结果(平台) | `polling_status_import:detail` |
|
||||
| IoT 卡列表 | 批量开关轮询(平台/代理) | `iot_card:batch_polling` |
|
||||
| 设备列表 | 批量开关轮询(平台/代理) | `device:batch_polling` |
|
||||
| 单卡资产详情 / 卡级告警详情 | 查询单卡轮询状态 | `iot_info:polling_state` |
|
||||
| 设备资产详情的绑定卡 | 查询该绑定卡轮询状态 | `device_info:polling_state` |
|
||||
| 导出不轮询清单 | 查看详情 / 下载 | `export_task:polling_pause_detail` / `export_task:polling_pause_download` |
|
||||
| 导出停机被拒告警 | 查看详情 / 下载 | `export_task:polling_stop_refused_alert_detail` / `export_task:polling_stop_refused_alert_download` |
|
||||
| 导出停复机规则演练 | 查看详情 / 下载 | `export_task:stop_resume_rule_dry_run_detail` / `export_task:stop_resume_rule_dry_run_download` |
|
||||
|
||||
“详情”按钮及对应隐藏详情菜单需同时授权。告警详情内查看停复机记录复用已有 `iot_info:stop_resume_records`;资产单项轮询开关复用 `iot_info:auto_polling` / `device_info:auto_polling`,无需新编码。请求检查场景、队列监控无新增普通写按钮。系统配置沿用旧菜单与权限,仅新增 polling 模块选项。
|
||||
|
||||
### 操作边界
|
||||
|
||||
- 批量只提交当前勾选 ID,最多 500 条,不扩展成全量筛选;原因必填,先读 impact 再确认。四类逐项结果完整保留,部分成功不回滚。
|
||||
- 企业账号不开放批量;代理资产范围由后端校验。风险停机、已销户不提供“强制开启”。
|
||||
- 账户级告警 card_id=0 不请求单卡接口、不允许勾选关闭卡轮询;停机被拒视图隐藏并剔除不支持的筛选。
|
||||
- 导入仅 CSV,首行为表头,首列保留文本,最多 50000 数据行;上传成功后才创建任务。任务终态/请求失败停止自动刷新。
|
||||
- 演练仅判断不执行;明细 result 不改变汇总,导出也不带 result;演练允许每页 500,其他列表最大 100。
|
||||
- 调度、限流、指令队列开关不会因本次前端接入自动修改。旧并发配置仅 legacy 模式有效。
|
||||
|
||||
C 端同步项和接口覆盖/验证见 [本次接入交付说明](./2026-10-26-轮询账户限流-后台接入交付.md)。
|
||||
|
||||
本次验证:191 项回归通过;类型、生产构建、代码/样式/格式与 UTF-8 检查通过。仅本地 mock 验收,没有写入菜单数据、推送或部署;生产构建仍有项目既有循环依赖与大 chunk 警告。
|
||||
|
||||
## 订单分类与沉默期(2026-10-28)
|
||||
|
||||
后台实现已按 Apifox 定义补齐。以下为实际路由和前端权限约定;后端仍需创建真实菜单/按钮记录并独立校验权限与数据范围。未推送、部署或写入服务器菜单,真实支付/审批/退款/导出需测试环境联调。准确范围见 [执行记录](../openspec/changes/add-order-segmentation-and-package-silence/implementation.md)。
|
||||
|
||||
### 新增可见菜单
|
||||
|
||||
| 菜单名称 | URL | 父菜单 | 菜单权限 |
|
||||
| --- | --- | --- | --- |
|
||||
| 平台订单 | `/order-management/platform-orders` | 订单管理 `/order-management` | `orders:platform_page` |
|
||||
| 代理商订单 | `/order-management/agent-orders` | 订单管理 | `orders:agent_page` |
|
||||
| 在线支付订单 | `/order-management/online-orders` | 订单管理 | `orders:online_page` |
|
||||
| 延期订单 | `/package-management/silence-orders` | 套餐管理 `/package-management` | `package_silence:orders_page` |
|
||||
| 延期批次与异常 | `/package-management/silence-batches` | 套餐管理 | `package_silence:batches_page` |
|
||||
| 沉默期临期/过期套餐 | `/package-management/silence-usages` | 套餐管理 | `package_silence:usages_page` |
|
||||
| 延期政策 | `/package-management/silence-policies` | 套餐管理 | `package_silence:policies_page`(并需 `package_silence:policy`) |
|
||||
| 导出平台订单 | `/asset-management/export-task-management/export-order-platform` | 导出管理 `/asset-management/export-task-management` | `export_task:order_platform_page` |
|
||||
| 导出代理商订单 | `/asset-management/export-task-management/export-order-agent` | 导出管理 | `export_task:order_agent_page` |
|
||||
| 导出在线支付订单 | `/asset-management/export-task-management/export-order-online` | 导出管理 | `export_task:order_online_page` |
|
||||
| 导出延期订单 | `/asset-management/export-task-management/export-silence-order` | 导出管理 | `export_task:package_silence_order_page` |
|
||||
| 导出沉默期套餐 | `/asset-management/export-task-management/export-silence-usage` | 导出管理 | `export_task:package_silence_usage_page` |
|
||||
|
||||
代理账号仅可配置平台/代理商普通订单及其导出;在线普通订单及导出只允许 user_type=1/2。企业不得配置普通订单菜单。旧普通订单列表/详情保留。沉默期模块没有额外虚构身份范围,按后端真实授权及数据范围工作。
|
||||
|
||||
### 新增隐藏详情菜单
|
||||
|
||||
| 菜单名称 | URL | 父菜单 | 菜单权限 |
|
||||
| --- | --- | --- | --- |
|
||||
| 延期订单详情 | `/package-management/silence-orders/detail/:id` | 套餐管理 | `package_silence:order_detail_page` |
|
||||
| 延期批次详情 | `/package-management/silence-batches/detail/:id` | 套餐管理 | `package_silence:batch_detail_page` |
|
||||
|
||||
直接访问详情同时要求对应列表页权限、隐藏详情菜单权限和下表详情按钮权限;不能只配隐藏详情菜单。导出详情沿用已有隐藏 `export_task:detail_page` 与已有导出详情 URL。仅超管专属配置不列入普通菜单清单。
|
||||
|
||||
### 新增及沿用按钮权限
|
||||
|
||||
| 操作 | 权限编码 |
|
||||
| --- | --- |
|
||||
| 下单时调整本次沉默期(两个单项购买入口) | `package_silence:override` |
|
||||
| 扫码付费延期、单项特殊延期 | `package_silence:extend` |
|
||||
| 批量特殊延期(含 CSV 导入) | 同时需要 `package_silence:extend`、`package_silence:extend_batch` |
|
||||
| 登记线下付费延期 | `package_silence:offline` |
|
||||
| 异常明细重试/关闭 | `package_silence:exception` |
|
||||
| 政策查询/新增/编辑/启停/匹配 | `package_silence:policy` |
|
||||
| 查看延期订单详情 | `package_silence:order_detail` |
|
||||
| 查看延期批次详情 | `package_silence:batch_detail` |
|
||||
| 创建延期订单导出 | `package_silence:order_export` |
|
||||
| 创建沉默期套餐清单导出 | `package_silence:usage_export` |
|
||||
| 创建普通订单/查看详情/导出 | 沿用 `orders:add` / `orders:view_detail` / `orders:export` |
|
||||
| 平台普通订单导出详情/下载 | `export_task:order_platform_detail` / `export_task:order_platform_download` |
|
||||
| 代理商普通订单导出详情/下载 | `export_task:order_agent_detail` / `export_task:order_agent_download` |
|
||||
| 在线普通订单导出详情/下载 | `export_task:order_online_detail` / `export_task:order_online_download` |
|
||||
| 延期订单导出详情/下载 | `export_task:package_silence_order_detail` / `export_task:package_silence_order_download` |
|
||||
| 沉默期套餐导出详情/下载 | `export_task:package_silence_usage_detail` / `export_task:package_silence_usage_download` |
|
||||
|
||||
沉默期流水、首次购买记录没有在后端文档声明独立按钮权限,继承所属资产/列表页的读取范围,不虚构按钮编码。角色配置继续使用后端真实权限树,需后端提供权限记录和 ID,前端不伪造记录。
|
||||
|
||||
### 操作边界与验证
|
||||
|
||||
- 默认商品沉默期 1–90 天,购买覆盖天数仅最小 1;付费延期天数/金额由资格和试算决定,不复制算法。
|
||||
- 特殊延期 CSV 为前端解析:表头 `package_usage_id,days`,每行两个整数,转换为文档 items[];不假设后端导入文件格式。
|
||||
- 政策免审批完整枚举未在 OpenAPI 给出;已有值原样保留,提供明确的 offline_paid/batch,其他值需填写后端精确编码。政策接口没有 DELETE,不提供删除。
|
||||
- 二维码/线下同一快照重试复用幂等键;特殊请求结果不明时提示核对批次并阻止重复提交。待审批、已支付和已完成严格区分。
|
||||
- 异常关闭必须填写原因并确认,提示在线订单可能原路退款;不直接修改套餐截止时间。
|
||||
- 企业资产五项限制保持;首次购买为只读事实,不回填绑定卡或换货资产;对象缺失隐藏沉默期入口。
|
||||
- 236 项测试、类型与生产构建通过;仅本地 mock 验收,没有真实支付、审批、退款、开关切换、导出、推送或部署。
|
||||
|
||||
### C 端同步(本仓库未修改)
|
||||
|
||||
独立 C 端需接入可选 silence、状态/格式化截止日及 extendable 入口;`/api/c/v1/package-silence` 下的资格、报价、自助下单/qr_content、订单状态刷新、我的延期订单/详情、流水。对象缺失或总开关关闭时隐藏入口;金额单位分、结果取后端,不能复制计费/审批算法,不调用后台 URL。资产归属由后端校验。
|
||||
@@ -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进行真实数据调试。恭喜项目顺利完成!🎊
|
||||
@@ -0,0 +1,35 @@
|
||||
## Context
|
||||
|
||||
临期结果由后端根据资产当前套餐及排队套餐计算。管理端需要在独立列表、普通资产列表、代理首页和通知中心保持相同的临期语义。本变更只覆盖管理端,C 端资产和续费能力不纳入实现范围。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: 统一消费 `estimated_final_expires_at`、`days_until_final_expiry`、`expiry_level`、`expiry_level_name` 和 `can_renew`;提供临期查询、排序、高亮、统计、通知跳转和管理端续费入口。
|
||||
- Goals: 由后端负责临期边界、预计到期结果和通知触发,前端只负责展示和路由。
|
||||
- Non-Goals: 不计算套餐接续到期时间,不修改历史订单或已购套餐,不实现 C 端入口,不展示企微临期消息。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 临期独立列表使用 `GET /api/admin/expiring-assets`,查询参数保持文档约定的 `asset_type`、`keyword`、`shop_id`、`package_id`、`days_min`、`days_max`、`expires_from`、`expires_to`、`page`、`size`。
|
||||
- Decision: 临期接口负责跨分页排序,返回结果按 0-3 天优先、其余按 `estimated_final_expires_at` 升序排列;前端只保留接口顺序,不改变普通资产列表原始接口排序。
|
||||
- Decision: 颜色只按剩余天数映射:8-15 天粉红、4-7 天紫色、0-3 天红色。已过期和不可预计记录由接口排除,前端不把它们补入临期列表。
|
||||
- Decision: 续费入口由 `can_renew` 控制,具体续费动作复用现有管理端续费/充值路由和接口,不新增 C 端逻辑。
|
||||
- Decision: 通知中心继续复用现有通知接口和目标跳转协议;临期通知由后端按 15 天、7 天、3 天生成,前端按通知目标跳转到临期列表或对应资产详情。
|
||||
- Alternatives considered: 前端从普通资产列表筛选临期记录。Rejected because it无法保证全量、统一排序和后端预计最终到期结果的一致性。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 风险:代理首页当前概览接口未必已有临期计数字段。Mitigation:在现有首页/概览响应中增加 `expiring_card_count` 和 `expiring_device_count`,避免前端分页统计。
|
||||
- 风险:不同资产列表的字段结构不完全一致。Mitigation:在各自 API 类型中复用同一组临期字段语义,并通过统一展示格式处理空值和等级。
|
||||
- 风险:续费入口的现有路由可能依赖资产类型。Mitigation:由 `asset_type` 和 `asset_id` 选择对应管理端续费入口,按钮仅在 `can_renew=true` 时展示。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 先扩展管理端 API 类型和服务,确认列表、首页统计和通知目标字段。
|
||||
2. 上线临期列表及普通列表高亮,再接入首页统计和续费入口。
|
||||
3. 最后验证通知中心过滤、已读和跳转,不修改 C 端功能。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 代理首页现有概览接口的具体路径和响应字段名称,需要以后端接口实现为准确认。
|
||||
- 管理端卡/设备续费入口的现有路由是否统一,需实现时复用当前权限和路由定义。
|
||||
@@ -0,0 +1,35 @@
|
||||
# Change: 增加管理端临期资产高亮、通知与续费入口
|
||||
|
||||
## Why
|
||||
|
||||
管理端目前缺少统一的临期资产查询入口,运营人员需要在普通资产列表中自行识别临近到期资产,且无法从临期记录快速进入续费操作。需要基于后端统一计算的预计最终到期结果,在管理端集中展示临期资产、标记普通列表并接入站内通知。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增管理端临期资产列表,支持资产类型、关键字、店铺、套餐、剩余天数和预计到期时间筛选。
|
||||
- 临期列表按 0-3 天固定置顶,其余按预计最终到期时间升序;已过期和不可预计资产不进入列表。
|
||||
- 在卡列表、设备列表和资产相关列表中增加临期颜色高亮,但不改变普通列表原有排序。
|
||||
- 在代理首页增加临期卡数量和临期设备数量展示,并可跳转临期列表。
|
||||
- 在临期列表提供后端返回 `can_renew` 控制的续费入口,复用现有管理端续费/充值流程。
|
||||
- 接入通知中心中的 15 天、7 天、3 天临期提醒及通知跳转;管理端不展示企微临期消息。
|
||||
- 所有页面直接使用后端返回的预计最终到期字段和临期等级,不在前端重新计算最终到期时间。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `admin-expiring-assets`
|
||||
- Affected code:
|
||||
- `src/api/modules` 和 `src/types/api` 中的临期资产接口及类型
|
||||
- 管理端临期资产列表页面和路由
|
||||
- 网卡列表、设备列表及资产信息展示组件
|
||||
- 代理首页统计组件
|
||||
- 通知中心跳转处理
|
||||
- API contracts:
|
||||
- `GET /api/admin/expiring-assets`
|
||||
- 现有代理首页/概览接口增加临期卡、设备数量字段,或提供等价的管理端统计响应
|
||||
- 复用现有通知查询、已读和目标跳转接口
|
||||
- Out of scope:
|
||||
- C 端资产页临期展示
|
||||
- C 端续费按钮和 C 端续费流程
|
||||
- 企微临期消息展示或企微通知改造
|
||||
- 前端根据套餐明细自行推导预计最终到期时间
|
||||
@@ -0,0 +1,111 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Admin Expiring Asset Query
|
||||
|
||||
The admin frontend SHALL provide an expiring asset list backed by `GET /api/admin/expiring-assets`. The query SHALL support `asset_type`, `keyword`, `shop_id`, `package_id`, `days_min`, `days_max`, `expires_from`, `expires_to`, `page`, and `size`.
|
||||
|
||||
#### Scenario: Filter expiring assets
|
||||
|
||||
- **WHEN** 管理端用户打开临期资产列表并提交筛选条件
|
||||
- **THEN** 前端 MUST send the documented query parameters to `GET /api/admin/expiring-assets`
|
||||
- **AND** 页面 MUST display the paginated response items
|
||||
|
||||
#### Scenario: Exclude unavailable assets
|
||||
|
||||
- **WHEN** 接口返回临期列表
|
||||
- **THEN** 页面 MUST not add expired assets or assets without an estimable final expiry to the list on the client side
|
||||
|
||||
### Requirement: Expiring Asset Fields
|
||||
|
||||
Each expiring asset item SHALL preserve and display the backend fields `asset_type`, `asset_id`, `identifier`, `shop_name`, `package_name`, `estimated_final_expires_at`, `days_until_final_expiry`, `expiry_level`, `expiry_level_name`, and `can_renew`. The frontend MUST use backend-provided expiry results and MUST NOT calculate the estimated final expiry from package details.
|
||||
|
||||
#### Scenario: Display an estimable asset
|
||||
|
||||
- **WHEN** 临期接口返回资产及 `estimated_final_expires_at`
|
||||
- **THEN** 页面 MUST display the asset identifier, shop, package, estimated final expiry, remaining days, and backend expiry level name
|
||||
|
||||
#### Scenario: Preserve backend result
|
||||
|
||||
- **WHEN** 临期接口返回 `estimated_final_expires_at` 或 `days_until_final_expiry`
|
||||
- **THEN** 前端 MUST display the returned values
|
||||
- **AND** 前端 MUST NOT derive or replace them from current or queued package data
|
||||
|
||||
### Requirement: Expiring List Ordering And Highlighting
|
||||
|
||||
The expiring asset API and standalone admin list SHALL return and preserve records with 0-3 remaining days first, then order the remaining records by `estimated_final_expires_at` ascending. The list SHALL apply pink highlighting to 8-15 days, purple highlighting to 4-7 days, and red highlighting to 0-3 days.
|
||||
|
||||
#### Scenario: Order critical assets first
|
||||
|
||||
- **GIVEN** the response contains assets in multiple expiry ranges
|
||||
- **WHEN** 页面渲染临期列表
|
||||
- **THEN** the API response MUST place assets with 0-3 remaining days before assets with more remaining days
|
||||
- **AND** the API response MUST order records in the remaining ranges by estimated final expiry ascending
|
||||
- **AND** the frontend MUST preserve that cross-page ordering
|
||||
|
||||
#### Scenario: Highlight by remaining days
|
||||
|
||||
- **WHEN** 页面渲染临期资产
|
||||
- **THEN** 8-15 days MUST use the pink visual treatment
|
||||
- **AND** 4-7 days MUST use the purple visual treatment
|
||||
- **AND** 0-3 days MUST use the red visual treatment
|
||||
|
||||
### Requirement: Ordinary Admin Asset List Highlighting
|
||||
|
||||
The admin card and device lists SHALL apply the same expiry color treatment to returned expiring asset fields without changing their existing server or client sort order.
|
||||
|
||||
#### Scenario: Highlight ordinary asset rows
|
||||
|
||||
- **WHEN** 卡列表或设备列表返回临期字段
|
||||
- **THEN** 页面 MUST apply the matching expiry color treatment
|
||||
- **AND** 页面 MUST preserve the list's existing ordering
|
||||
|
||||
### Requirement: Admin Expiring Asset Renewal Entry
|
||||
|
||||
The admin expiring asset list SHALL display a renewal action only when the backend item has `can_renew=true`. The action SHALL navigate to the existing management-side renewal or recharge flow for the asset type.
|
||||
|
||||
#### Scenario: Renewable asset
|
||||
|
||||
- **GIVEN** 临期资产项返回 `can_renew=true`
|
||||
- **WHEN** 用户查看临期列表
|
||||
- **THEN** 页面 MUST provide the management-side renewal entry
|
||||
- **AND** the entry MUST target the corresponding asset and preserve asset type context
|
||||
|
||||
#### Scenario: Non-renewable asset
|
||||
|
||||
- **GIVEN** 临期资产项返回 `can_renew=false`
|
||||
- **WHEN** 用户查看临期列表
|
||||
- **THEN** 页面 MUST NOT display an enabled renewal action
|
||||
|
||||
### Requirement: Agent Dashboard Expiry Counts
|
||||
|
||||
The agent-facing admin home SHALL display the number of expiring cards and expiring devices using backend-provided summary fields and SHALL provide navigation to the standalone expiring asset list.
|
||||
|
||||
#### Scenario: Display expiry counts
|
||||
|
||||
- **WHEN** 代理首页概览数据返回临期卡和设备数量
|
||||
- **THEN** 页面 MUST display the expiring card count and expiring device count
|
||||
- **AND** 页面 MUST not calculate the counts from a paginated asset list
|
||||
|
||||
### Requirement: Admin Expiry Notifications
|
||||
|
||||
The notification center SHALL display backend-generated admin expiry reminders for 15 days, 7 days, and 3 days through the existing notification API and target navigation. The admin frontend SHALL not display WeCom expiry messages.
|
||||
|
||||
#### Scenario: Display expiry reminder
|
||||
|
||||
- **WHEN** 通知接口返回 15 天、7 天或 3 天的临期提醒
|
||||
- **THEN** 通知中心 MUST classify it as a 临期提醒
|
||||
- **AND** 用户点击通知后 MUST navigate to the returned management-side target
|
||||
|
||||
#### Scenario: Exclude WeCom expiry message
|
||||
|
||||
- **WHEN** 管理端加载通知中心
|
||||
- **THEN** 页面 MUST not add or render a separate WeCom expiry message channel
|
||||
|
||||
### Requirement: Admin-Only Scope
|
||||
|
||||
This capability SHALL be limited to the management frontend. It SHALL NOT add or modify C-end asset expiry display, C-end renewal buttons, C-end renewal APIs, or C-end notification behavior.
|
||||
|
||||
#### Scenario: Keep C-end unchanged
|
||||
|
||||
- **WHEN** this change is implemented
|
||||
- **THEN** C-end asset pages and renewal flows MUST remain outside the change scope
|
||||
@@ -0,0 +1,35 @@
|
||||
## 1. API Contract
|
||||
|
||||
- [x] 1.1 增加 `GET /api/admin/expiring-assets` 的查询参数、分页响应和临期资产项类型。
|
||||
- [x] 1.2 为卡列表、设备列表、资产信息和首页概览类型补充统一临期字段及临期计数字段。
|
||||
- [x] 1.3 增加临期资产 API 服务方法,并确认续费入口复用现有管理端服务和权限。
|
||||
|
||||
## 2. Expiring Asset List
|
||||
|
||||
- [x] 2.1 增加或接入 `/operations/expiring-assets` 管理端路由和页面。
|
||||
- [x] 2.2 实现资产类型、关键字、店铺、套餐、剩余天数和预计到期时间筛选。
|
||||
- [x] 2.3 展示资产、店铺、当前套餐、预计最终到期、剩余天数和后端临期等级名称。
|
||||
- [x] 2.4 实现 0-3 天置顶、其余按预计到期时间升序,并排除已过期和不可预计记录。
|
||||
- [x] 2.5 按 8-15 天粉红、4-7 天紫色、0-3 天红色实现行或到期字段高亮。
|
||||
- [x] 2.6 根据 `can_renew` 展示管理端续费入口,并跳转现有续费/充值流程。
|
||||
|
||||
## 3. Existing Admin Pages
|
||||
|
||||
- [x] 3.1 在网卡普通列表增加临期字段展示和颜色高亮,不改变原排序。
|
||||
- [x] 3.2 在设备普通列表增加临期字段展示和颜色高亮,不改变原排序。
|
||||
- [x] 3.3 在资产信息详情复用同一临期展示规则,禁止前端重新计算预计最终到期时间。
|
||||
- [x] 3.4 在代理首页展示临期卡数量和临期设备数量,并支持跳转临期列表。
|
||||
|
||||
## 4. Notifications
|
||||
|
||||
- [x] 4.1 在通知中心复用临期分类,展示后端生成的 15 天、7 天、3 天临期提醒。
|
||||
- [x] 4.2 使用现有通知目标跳转到临期列表或对应管理端资产详情。
|
||||
- [x] 4.3 确认管理端不展示企微临期消息,不新增 C 端通知入口。
|
||||
|
||||
## 5. Verification
|
||||
|
||||
- [x] 5.1 验证临期字段直接使用后端值,前端不根据套餐明细推导最终到期时间。
|
||||
- [x] 5.2 验证 0-3 天置顶、日期升序、颜色映射和普通列表原排序保持不变。
|
||||
- [x] 5.3 验证 `can_renew=false` 不展示续费入口,且各资产类型使用正确管理端入口。
|
||||
- [x] 5.4 验证通知中心临期分类、已读状态和跳转行为。
|
||||
- [x] 5.5 运行类型检查、相关 ESLint/Stylelint、构建和 `openspec validate add-admin-expiring-assets-notifications --strict`。
|
||||
@@ -0,0 +1,23 @@
|
||||
# Change: 代理扫码分销注册与提现资料资格前端对接
|
||||
|
||||
## Why
|
||||
|
||||
新增强代理扫码分销注册与提现资料资格能力:代理可通过 H5 注册页扫码注册,审批通过后登录后台;代理本人可维护提现资料资格并发起/重提提现,超管可作废资格。后端契约已按 `docs/产品迭代8月份/frontend-api-simple.md` 落地,后台管理端当前缺少对应接口封装、独立注册页与资格管理入口。
|
||||
|
||||
本次前端按后端实际契约对齐:注册验码 `POST /api/c/v1/auth/send-code`(`scene` 为 `bind_phone`,返回 `cooldown_seconds`);扫码注册 `POST /api/c/v1/agent-distribution-registrations`(成功仅返回「待审批」);店铺列表/详情/更新响应新增 `distribution_code`;提现资料资格提交/查询/作废与提现申请重提/详情按新文档补齐。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增 `agent-distribution-registration` 能力:独立注册页挂在后台项目内、静态路由免登录访问(H5 与 PC 同一套表单),支持分销码自动填、短信验证码 60s 倒计时、密码掩码与强度提示、省市区级联;提交成功进入「待审批」结束页,失败统一提示「分销码不可用」且不复用同一验证码。
|
||||
- 新增公开 API 封装:`sendCode()` 与 `registerAgent()`,请求不带登录态(`requestOptions.withToken: false`)。
|
||||
- 店铺模块补充 `distribution_code` 字段类型,店铺详情页展示分销码与注册二维码。
|
||||
- 佣金模块新增:提现资料资格提交/替换、资格查询(证件号脱敏、含审批与作废信息)、资格作废(超管,`reason` 必填)、重提被驳回的提现、提现申请详情(含尝试记录与异常标记)。
|
||||
- 扩展企微审批场景业务类型:`agent_distribution_approval`、`withdrawal_qualification_approval`、`commission_withdrawal_approval`。
|
||||
- 提现交互约束:资格替换合同/法人身份证后旧资格失效需重新审批;提现仅在有效资格且余额充足时可提交,否则不冻结、不建单。
|
||||
- 不实现后端接口、数据库、企微回调;不实现 C 端(客户)登录体系。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `agent-distribution-registration`、`shop-management`、`commission-management`、`wecom-scenes`
|
||||
- Affected code: `src/api/modules/agentDistribution.ts`、`src/api/modules/commission.ts`、`src/types/api/shop.ts`、`src/types/api/commission.ts`、`src/types/api/wecom.ts`、`src/router/routes/staticRoutes.ts`、`src/router/guards/permission.ts`、`src/views/agent-registration/index.vue`、`src/views/shop-management/detail/index.vue`、`src/views/commission-management/my-commission/index.vue`、`src/views/settings/wecom/scenes/index.vue`
|
||||
- Dependencies: `docs/产品迭代8月份/frontend-api-simple.md`
|
||||
@@ -0,0 +1,61 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 独立代理注册页免登录访问
|
||||
代理扫码分销注册页 MUST 独立于登录态提供,未登录可访问,且挂在后台项目内(H5 与 PC 共用同一套表单);注册流程 MUST NOT 复用当前登录态。
|
||||
|
||||
#### Scenario: 未登录访问注册页
|
||||
- **GIVEN** 用户未登录并通过扫码或直接访问注册入口
|
||||
- **WHEN** 其打开注册页面
|
||||
- **THEN** 页面 MUST 正常渲染注册表单
|
||||
- **AND** MUST NOT 跳转到登录页
|
||||
|
||||
#### Scenario: 已登录用户访问注册页
|
||||
- **GIVEN** 用户已登录后台
|
||||
- **WHEN** 其打开注册页面
|
||||
- **THEN** 注册流程 MUST 不携带登录态
|
||||
|
||||
### Requirement: 发送短信验证码
|
||||
注册页 MUST 调用 `POST /api/c/v1/auth/send-code` 发送验证码,请求体 `{ phone, scene }`(`scene` 为 `bind_phone`),响应 `data.cooldown_seconds` MUST 用于 60 秒倒计时;请求 MUST 不携带 Token。
|
||||
|
||||
#### Scenario: 发送验证码并倒计时
|
||||
- **GIVEN** 用户输入手机号
|
||||
- **WHEN** 其点击获取验证码
|
||||
- **THEN** 系统 MUST 调用发送验证码接口
|
||||
- **AND** 按钮 MUST 进入 60 秒倒计时且不可重复点击
|
||||
|
||||
#### Scenario: 注册失败后不复用验证码
|
||||
- **GIVEN** 一次注册提交失败
|
||||
- **WHEN** 用户再次尝试注册
|
||||
- **THEN** 页面 MUST 提示重新获取验证码
|
||||
- **AND** MUST NOT 复用已消费的验证码
|
||||
|
||||
### Requirement: 代理扫码注册提交
|
||||
注册页 MUST 调用 `POST /api/c/v1/agent-distribution-registrations` 提交注册,必填 `distribution_code`(扫码自动带)、`phone`、`code`、`password`、`shop_name`、`shop_code`、`username`,选填 `contact_name`、`province`、`city`、`district`、`address`;成功响应为「待审批」,前端 MUST 展示待审批结束页且不自动登录。
|
||||
|
||||
#### Scenario: 注册成功进入待审批
|
||||
- **GIVEN** 用户填写完整表单并通过校验
|
||||
- **WHEN** 其提交注册
|
||||
- **THEN** 系统 MUST 调用注册接口
|
||||
- **AND** 成功时 MUST 展示「待审批,审核结果将通知你」结束页
|
||||
- **AND** MUST NOT 发放账号凭证或自动登录
|
||||
|
||||
#### Scenario: 注册失败统一提示
|
||||
- **GIVEN** 注册提交失败(无效分销码、上级停用、验证码无效或已消费等)
|
||||
- **WHEN** 注册接口返回失败
|
||||
- **THEN** 页面 MUST 统一提示「分销码不可用」
|
||||
- **AND** MUST NOT 根据错误文案区分原因
|
||||
|
||||
### Requirement: 表单适配与敏感项处理
|
||||
注册表单 MUST 同时适配手机 H5 与 PC:H5 单列、大触控区、软键盘友好、地址使用级联选择器;PC 使用居中卡片或两列布局且字段一致。密码输入 MUST 掩码并展示强度提示;页面 MUST NOT 展示除手机号外的完整个人敏感信息。
|
||||
|
||||
#### Scenario: H5 与 PC 同一表单
|
||||
- **GIVEN** 用户分别在手机与 PC 打开注册页
|
||||
- **WHEN** 其填写注册信息
|
||||
- **THEN** 两端的字段集合 MUST 一致
|
||||
- **AND** 布局 MUST 按端侧自适应
|
||||
|
||||
#### Scenario: 密码强度与掩码
|
||||
- **GIVEN** 用户在密码输入框输入
|
||||
- **WHEN** 其提交表单
|
||||
- **THEN** 输入 MUST 为掩码展示
|
||||
- **AND** MUST 展示密码强度提示
|
||||
@@ -0,0 +1,61 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 提交/替换提现资料资格
|
||||
代理本人 MUST 能提交或替换提现资料资格,调用 `POST /api/admin/shops/{shop_id}/withdrawal-qualifications`,请求体包含 `subject_type`、`subject_code`、`legal_person_id_card` 与合同、身份证正反面、营业执照、门头照、发票等 `*_file_key`,以及 `invoice_title`、`invoice_subject_code`;附件 MUST 先通过对象存储上传接口取得 `file_key` 再提交。
|
||||
|
||||
#### Scenario: 提交资格成功
|
||||
- **GIVEN** 代理本人已登录并选好主体类型
|
||||
- **WHEN** 其上传资料并提交
|
||||
- **THEN** 前端 MUST 先取得全部附件 `file_key`
|
||||
- **AND** 再调用提交接口并在成功后刷新资格列表
|
||||
|
||||
#### Scenario: 替换资格使旧资格失效
|
||||
- **GIVEN** 已存在通过审批的资格
|
||||
- **WHEN** 代理提交合同或法人身份证变更
|
||||
- **THEN** 旧资格 MUST 立即失效
|
||||
- **AND** 新资格 MUST 重新审批通过后方可提现
|
||||
|
||||
### Requirement: 查询提现资料资格
|
||||
代理本人 MUST 能分页查询提现资料资格,调用 `GET /api/admin/shops/{shop_id}/withdrawal-qualifications`(`page` / `page_size` / `status`);响应 MUST 展示脱敏的 `subject_code_masked` 与 `legal_person_id_card_masked`,并展示 `status`、`approval_status`、`invalid_reason`、`invalidated_at` 与各附件 `file_key` 预览。
|
||||
|
||||
#### Scenario: 查看资格版本与审批状态
|
||||
- **GIVEN** 代理本人打开提现资料资格列表
|
||||
- **WHEN** 接口返回资格记录
|
||||
- **THEN** 列表 MUST 展示脱敏证件号与审批状态
|
||||
- **AND** 证件号 MUST NOT 以明文展示
|
||||
|
||||
### Requirement: 作废提现资料资格
|
||||
超级管理员 MUST 能作废提现资料资格,调用 `POST /api/admin/withdrawal-qualifications/{id}/void`,`reason` 必填。
|
||||
|
||||
#### Scenario: 作废资格须填原因
|
||||
- **GIVEN** 超级管理员打开作废弹窗
|
||||
- **WHEN** 其未填写原因直接提交
|
||||
- **THEN** 前端 MUST 阻止提交并提示填写原因
|
||||
|
||||
#### Scenario: 超管作废资格
|
||||
- **GIVEN** 超级管理员选择一条资格
|
||||
- **WHEN** 其填写原因并确认作废
|
||||
- **THEN** 系统 MUST 调用作废接口并在成功后刷新列表
|
||||
|
||||
### Requirement: 重提被驳回的提现
|
||||
代理本人 MUST 能重提被驳回的提现,调用 `PUT /api/admin/shops/{shop_id}/withdrawal-requests/{id}`,请求体包含 `account_name`、`account_number`、`amount`、`withdrawal_method` 与 `invoice_keys`;成功响应返回新提现单(`withdrawal_no`、`actual_amount`、`fee`、`fee_rate`、`status`)。
|
||||
|
||||
#### Scenario: 重提被驳回的提现
|
||||
- **GIVEN** 代理本人的提现申请被驳回
|
||||
- **WHEN** 其修改信息并重新提交
|
||||
- **THEN** 系统 MUST 调用重提接口
|
||||
- **AND** 成功后 MUST 刷新提现记录并展示新单号
|
||||
|
||||
#### Scenario: 非驳回状态不可重提
|
||||
- **GIVEN** 提现申请不是被驳回状态
|
||||
- **WHEN** 代理尝试重提
|
||||
- **THEN** 重提入口 MUST 不可用或不展示
|
||||
|
||||
### Requirement: 提现申请详情
|
||||
代理本人 MUST 能查看提现申请详情,调用 `GET /api/admin/shops/{shop_id}/withdrawal-requests/{id}`;响应包含 `reject_reason`、`anomaly_flag`、`anomaly_name`、`anomaly_reason` 与 `attempts` 尝试记录,前端 MUST 展示这些字段。
|
||||
|
||||
#### Scenario: 查看提现详情
|
||||
- **GIVEN** 代理本人点击提现记录
|
||||
- **WHEN** 详情返回
|
||||
- **THEN** 页面 MUST 展示提现金额、实际到账、手续费、状态
|
||||
- **AND** 展示驳回原因、异常标记与尝试记录
|
||||
@@ -0,0 +1,15 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 店铺数据返回分销码
|
||||
店铺列表、详情与更新接口响应 MUST 包含 `distribution_code` 字段,前端类型 MUST 覆盖该字段并在列表/详情中展示。
|
||||
|
||||
#### Scenario: 店铺详情展示分销码
|
||||
- **GIVEN** 用户打开店铺详情页
|
||||
- **WHEN** 店铺存在 `distribution_code`
|
||||
- **THEN** 页面 MUST 展示分销码
|
||||
- **AND** MUST 以该码生成注册入口二维码
|
||||
|
||||
#### Scenario: 分销码为空
|
||||
- **GIVEN** 店铺尚未分配分销码
|
||||
- **WHEN** 页面展示店铺信息
|
||||
- **THEN** 分销码与二维码区域 MUST 展示空态(`-` 或「未分配」)
|
||||
@@ -0,0 +1,15 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 企微审批场景业务类型扩展
|
||||
企微审批场景的 `business_type` MUST 支持以下枚举:`refund_approval`(退款审批)、`offline_recharge_approval`(员工线下代充值审批)、`employee_collection_approval`(员工代收款核销审批)、`agent_distribution_approval`(代理扫码分销注册审批)、`withdrawal_qualification_approval`(提现资料资格审批)、`commission_withdrawal_approval`(佣金提现终审)。前端类型与场景配置页选项 MUST 与后端枚举一致;`GET /api/admin/wecom/scenes/{business_type}/fields` 允许查询上述任一类型。
|
||||
|
||||
#### Scenario: 场景配置页可选新业务类型
|
||||
- **GIVEN** 超级管理员打开企微审批场景配置页
|
||||
- **WHEN** 其新建场景并选择业务类型
|
||||
- **THEN** 下拉选项 MUST 包含全部六个业务类型
|
||||
- **AND** 新增三个业务类型 MUST 与后端枚举一致
|
||||
|
||||
#### Scenario: 查询新增场景业务字段
|
||||
- **GIVEN** 已选择 `agent_distribution_approval`、`withdrawal_qualification_approval` 或 `commission_withdrawal_approval`
|
||||
- **WHEN** 页面加载业务字段
|
||||
- **THEN** 前端 MUST 调用对应 `business_type` 的字段查询接口
|
||||
@@ -0,0 +1,29 @@
|
||||
## 1. 提案与 API 层
|
||||
- [x] 1.1 新增 `src/api/modules/agentDistribution.ts`:`sendCode()` 与 `registerAgent()`,公开请求不带 Token
|
||||
- [x] 1.2 扩展 `src/types/api/shop.ts`:`ShopResponse` 增加 `distribution_code`
|
||||
- [x] 1.3 扩展 `src/types/api/commission.ts`:提现资料资格提交/查询、作废、重提、详情的请求与响应类型
|
||||
- [x] 1.4 扩展 `src/api/modules/commission.ts`:`submitWithdrawalQualification` / `getWithdrawalQualifications` / `voidWithdrawalQualification` / `resubmitWithdrawalRequest` / `getWithdrawalRequestDetail`
|
||||
- [x] 1.5 扩展 `src/types/api/wecom.ts`:`WecomBusinessType` 增加三个业务类型
|
||||
- [x] 1.6 汇总导出新增类型
|
||||
|
||||
## 2. 企微审批场景
|
||||
- [x] 2.1 场景配置页新增三个业务类型选项(`agent_distribution_approval` / `withdrawal_qualification_approval` / `commission_withdrawal_approval`)
|
||||
|
||||
## 3. 独立注册页
|
||||
- [x] 3.1 `staticRoutes.ts` 新增 `/agent-registration` 静态路由
|
||||
- [x] 3.2 `LOGIN_WHITE_LIST` 增加注册页路径
|
||||
- [x] 3.3 新增 `src/views/agent-registration/index.vue`:表单、验证码倒计时、密码强度、省市区级联、提交与结束页、H5/PC 响应式
|
||||
|
||||
## 4. 店铺详情
|
||||
- [x] 4.1 店铺详情页展示 `distribution_code` 与注册二维码
|
||||
|
||||
## 5. 我的佣金(代理侧)
|
||||
- [x] 5.1 新增「提现资料资格」Tab:资格列表(脱敏展示)+ 提交/替换弹窗(附件走上传接口)
|
||||
- [x] 5.2 提现记录新增「详情」抽屉:展示明细、驳回原因、异常标记与尝试记录
|
||||
- [x] 5.3 被驳回记录新增「重新提交」弹窗(PUT 重提)
|
||||
- [x] 5.4 超管可见「作废资格」操作(reason 必填)
|
||||
|
||||
## 6. 验证
|
||||
- [x] 6.1 运行 `npm run build`(含 `vue-tsc --noEmit`)
|
||||
- [x] 6.2 运行 `npm run check:encoding`
|
||||
- [x] 6.3 运行 `openspec.cmd validate add-agent-distribution-registration-and-withdrawal --strict`
|
||||
@@ -0,0 +1,16 @@
|
||||
## Context
|
||||
|
||||
代理注册申请由公开注册接口创建,后台需要按数据范围查询申请并展示审批提交状态。恢复审批只恢复原企业微信审批提交,不创建新的注册申请或审批实例。
|
||||
|
||||
## Decisions
|
||||
|
||||
- 使用列表页 + 独立详情页,详情页 URL 为 `/shop-management/agent-distribution-registrations/detail/:id`。
|
||||
- 列表和详情均使用后端返回的 `status`、`approval_status`、`submission_status` 和名称字段,不在前端推导状态。
|
||||
- 恢复按钮仅由后端返回的 `recoverable` 控制,并使用独立 `agent_distribution_registration:recover_approval` 权限。
|
||||
- 详情响应直接消费后端完整手机号和注册地址,不展示密码或内部审批字段。
|
||||
|
||||
## Risks / Mitigations
|
||||
|
||||
- 状态可能在列表与详情之间发生变化 → 详情和恢复成功/失败后重新加载后端数据。
|
||||
- 恢复请求并发冲突 → 后端返回错误时提示并刷新详情,不做乐观更新。
|
||||
- 手机号属于敏感业务数据 → 页面仅受注册申请列表/详情权限和后端数据范围控制。
|
||||
@@ -0,0 +1,31 @@
|
||||
# Change: 增加代理注册申请后台管理
|
||||
|
||||
## Why
|
||||
|
||||
后台目前无法查看代理扫码注册申请,也无法处理企业微信审批提交失败或结果未知的注册申请。根据 `docs/产品迭代8月份/代理注册管理.md`,需要提供申请列表、详情和恢复原审批提交入口。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增后台代理注册申请列表页,支持状态、申请/决定时间、手机号、关键字、直接上级店铺和提交异常筛选。
|
||||
- 新增注册申请详情页,展示完整手机号、注册地址、申请店铺、分销码、业务状态、审批状态和企微提交状态。
|
||||
- 当 `recoverable = true` 时显示“恢复审批”,调用 `POST /api/admin/agent-distribution-registrations/{id}/recover-approval`,成功后刷新详情。
|
||||
- 新增代理注册申请 API、类型、路由和权限编码。
|
||||
- 权限编码:列表 `agent_distribution_registration:list`、详情 `agent_distribution_registration:detail`、恢复审批 `agent_distribution_registration:recover_approval`。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `agent-distribution-registration`
|
||||
- Affected code:
|
||||
- `src/api/modules/agentDistribution.ts`
|
||||
- `src/types/api/agentDistribution.ts`
|
||||
- `src/config/constants/augustIteration.ts`
|
||||
- `src/router/routesAlias.ts`
|
||||
- `src/router/routes/asyncRoutes.ts`
|
||||
- `src/views/shop-management/agent-distribution-registrations/index.vue`
|
||||
- `src/views/shop-management/agent-distribution-registrations/detail.vue`
|
||||
- `src/locales/langs/zh.json`
|
||||
- `docs/权限.md`
|
||||
- Out of scope:
|
||||
- C 端注册流程和代理登录流程。
|
||||
- 后端审批、数据库和企业微信回调实现。
|
||||
- 修改注册申请业务资料或审批结果。
|
||||
@@ -0,0 +1,33 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Agent Registration Application List
|
||||
|
||||
The admin frontend SHALL provide a paginated agent registration application list with the documented filters and backend response statuses.
|
||||
|
||||
#### Scenario: Filter registration applications
|
||||
|
||||
- **WHEN** an authorized user selects status, time, phone, keyword, parent shop, or submission anomaly filters
|
||||
- **THEN** the frontend MUST send those filters to `GET /api/admin/agent-distribution-registrations`
|
||||
- **AND** the list MUST display business, approval, and submission status names from the response
|
||||
|
||||
### Requirement: Agent Registration Application Detail
|
||||
|
||||
The admin frontend SHALL provide a detail page for `GET /api/admin/agent-distribution-registrations/{id}` and display the complete registration information returned by the backend.
|
||||
|
||||
#### Scenario: Open registration detail
|
||||
|
||||
- **WHEN** an authorized user opens a registration application
|
||||
- **THEN** the frontend MUST request the application detail by ID
|
||||
- **AND** MUST display the phone, address, shop, distribution code, business status, approval status, and submission status
|
||||
- **AND** MUST NOT display password or internal approval fields not present in the response
|
||||
|
||||
### Requirement: Recover Agent Registration Approval
|
||||
|
||||
The frontend SHALL expose `POST /api/admin/agent-distribution-registrations/{id}/recover-approval` only when `recoverable = true` and the user has the recovery permission.
|
||||
|
||||
#### Scenario: Recover approval
|
||||
|
||||
- **GIVEN** a registration response has `recoverable = true`
|
||||
- **WHEN** the user confirms “恢复审批”
|
||||
- **THEN** the frontend MUST call the recovery endpoint with only the registration ID
|
||||
- **AND** MUST refresh the detail after success or a state conflict
|
||||
@@ -0,0 +1,17 @@
|
||||
## 1. API And Types
|
||||
|
||||
- [x] 1.1 增加代理注册申请列表、详情和恢复审批 TypeScript 类型。
|
||||
- [x] 1.2 扩展 `AgentDistributionService`:列表、详情、恢复审批接口。
|
||||
- [x] 1.3 增加唯一权限常量 `list`、`detail`、`recoverApproval`。
|
||||
|
||||
## 2. Pages And Routes
|
||||
|
||||
- [x] 2.1 新增注册申请列表页和筛选条件。
|
||||
- [x] 2.2 新增详情页和审批/提交状态展示。
|
||||
- [x] 2.3 接入“恢复审批”按钮、确认、错误提示和刷新。
|
||||
- [x] 2.4 增加店铺管理下的列表/详情路由与中英文菜单文案。
|
||||
|
||||
## 3. Documentation And Verification
|
||||
|
||||
- [x] 3.1 将页面、详情和恢复审批权限写入 `docs/权限.md`。
|
||||
- [x] 3.2 运行类型检查、lint、编码检查、构建和 OpenSpec 校验。
|
||||
33
openspec/changes/add-asset-batch-realname-policy/proposal.md
Normal file
33
openspec/changes/add-asset-batch-realname-policy/proposal.md
Normal file
@@ -0,0 +1,33 @@
|
||||
# Change: 新增资产批量实名认证策略配置
|
||||
|
||||
## Why
|
||||
|
||||
运营需要一次性为多个卡或设备配置实名认证顺序。现有后台仅支持单资产设置实名认证策略,无法满足列表多选后的批量配置需求。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在后台卡列表和设备列表分别增加“批量修改实名顺序”入口,基于当前勾选资产执行配置。
|
||||
- 批量配置弹框展示已选资产数量,并提供“无需实名”“先实名后购买”“先购买后实名”三种互斥策略。
|
||||
- 卡列表调用 `POST /api/admin/iot-cards/batch-update-realname-policy`;设备列表调用 `POST /api/admin/devices/batch-update-realname-policy`。
|
||||
- 批量请求传递 `asset_ids` 和 `realname_policy`;前端限制单次提交至多 500 条,并在超限时阻止提交并明确提示。
|
||||
- 设备批量配置弹框提示“实际H5流程由设备策略决定”。
|
||||
- 后端批量接口按全成全败处理;前端在失败时展示明确的后端业务错误,成功后刷新当前列表。
|
||||
- 前端不根据资产类型、卡类型或其他字段自行覆盖或推导实名认证策略。
|
||||
- 本提案不包含任何 H5 初始化、购买流程或 `effective_realname_policy` 的处理。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `iot-card-management`
|
||||
- `device-management`
|
||||
- Affected code:
|
||||
- `src/api/modules/asset.ts` 或对应卡、设备 API 模块
|
||||
- `src/types/api/asset.ts` 或对应卡、设备 API 类型
|
||||
- `src/views/asset-management/iot-card-management/index.vue`
|
||||
- `src/views/asset-management/device-list/index.vue`
|
||||
- API contracts:
|
||||
- `POST /api/admin/iot-cards/batch-update-realname-policy`
|
||||
- `POST /api/admin/devices/batch-update-realname-policy`
|
||||
- Out of scope:
|
||||
- H5 初始化返回字段和购买流程
|
||||
- 单资产实名认证策略设置接口 `PATCH /api/admin/assets/{identifier}/realname-mode`
|
||||
@@ -0,0 +1,54 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Device Batch Realname Policy Configuration
|
||||
|
||||
The device management list SHALL provide a `批量修改实名顺序` action for selected devices. The action SHALL submit the selected device IDs and exactly one realname policy to `POST /api/admin/devices/batch-update-realname-policy`.
|
||||
|
||||
#### Scenario: Open batch realname policy dialog for selected devices
|
||||
|
||||
- **GIVEN** 用户在设备列表勾选了一台或多台设备
|
||||
- **WHEN** 用户点击“批量修改实名顺序”
|
||||
- **THEN** 页面 MUST open a dialog that displays the selected device count
|
||||
- **AND** 页面 MUST provide mutually exclusive options `无需实名`、`先实名后购买` 和 `先购买后实名`
|
||||
- **AND** 页面 MUST display `实际H5流程由设备策略决定` 提示
|
||||
|
||||
#### Scenario: Submit selected device policy
|
||||
|
||||
- **GIVEN** 用户已选择一项实名认证策略
|
||||
- **WHEN** 用户确认批量修改
|
||||
- **THEN** 系统 MUST call `POST /api/admin/devices/batch-update-realname-policy`
|
||||
- **AND** 请求 MUST contain the selected device IDs as `asset_ids`
|
||||
- **AND** 请求 MUST contain the selected `realname_policy` as `none`、`before_order` 或 `after_order`
|
||||
|
||||
#### Scenario: Refresh devices after all-or-nothing success
|
||||
|
||||
- **WHEN** 设备批量实名认证策略接口成功返回
|
||||
- **THEN** 页面 MUST close the dialog
|
||||
- **AND** 页面 MUST refresh the current device list
|
||||
|
||||
#### Scenario: Show failed batch update reason
|
||||
|
||||
- **WHEN** 设备批量实名认证策略接口返回业务失败或请求失败
|
||||
- **THEN** 页面 MUST display the backend business reason when provided
|
||||
- **AND** 页面 MUST NOT refresh the list as a partial-success result
|
||||
|
||||
### Requirement: Device Batch Realname Policy Limit
|
||||
|
||||
The device management list MUST limit each realname policy batch submission to 500 selected devices.
|
||||
|
||||
#### Scenario: Prevent device batch submission over the limit
|
||||
|
||||
- **GIVEN** 用户在设备列表选择超过 500 台设备
|
||||
- **WHEN** 用户尝试确认批量修改实名认证策略
|
||||
- **THEN** 页面 MUST prevent the request from being sent
|
||||
- **AND** 页面 MUST display an explicit maximum-500-items error
|
||||
|
||||
### Requirement: Device Batch Policy Is User Selected
|
||||
|
||||
The device management list MUST submit the policy explicitly selected by the user and MUST NOT infer, override, or transform it from asset type, card type, or other asset fields.
|
||||
|
||||
#### Scenario: Preserve selected device policy value
|
||||
|
||||
- **GIVEN** 用户在批量配置弹框选择任一实名认证策略
|
||||
- **WHEN** 用户确认提交
|
||||
- **THEN** 请求中的 `realname_policy` MUST equal the selected option
|
||||
@@ -0,0 +1,53 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: IoT Card Batch Realname Policy Configuration
|
||||
|
||||
The IoT card management list SHALL provide a `批量修改实名顺序` action for selected cards. The action SHALL submit the selected card IDs and exactly one realname policy to `POST /api/admin/iot-cards/batch-update-realname-policy`.
|
||||
|
||||
#### Scenario: Open batch realname policy dialog for selected cards
|
||||
|
||||
- **GIVEN** 用户在卡列表勾选了一张或多张卡
|
||||
- **WHEN** 用户点击“批量修改实名顺序”
|
||||
- **THEN** 页面 MUST open a dialog that displays the selected card count
|
||||
- **AND** 页面 MUST provide mutually exclusive options `无需实名`、`先实名后购买` 和 `先购买后实名`
|
||||
|
||||
#### Scenario: Submit selected card policy
|
||||
|
||||
- **GIVEN** 用户已选择一项实名认证策略
|
||||
- **WHEN** 用户确认批量修改
|
||||
- **THEN** 系统 MUST call `POST /api/admin/iot-cards/batch-update-realname-policy`
|
||||
- **AND** 请求 MUST contain the selected card IDs as `asset_ids`
|
||||
- **AND** 请求 MUST contain the selected `realname_policy` as `none`、`before_order` 或 `after_order`
|
||||
|
||||
#### Scenario: Refresh cards after all-or-nothing success
|
||||
|
||||
- **WHEN** 卡批量实名认证策略接口成功返回
|
||||
- **THEN** 页面 MUST close the dialog
|
||||
- **AND** 页面 MUST refresh the current card list
|
||||
|
||||
#### Scenario: Show failed batch update reason
|
||||
|
||||
- **WHEN** 卡批量实名认证策略接口返回业务失败或请求失败
|
||||
- **THEN** 页面 MUST display the backend business reason when provided
|
||||
- **AND** 页面 MUST NOT refresh the list as a partial-success result
|
||||
|
||||
### Requirement: IoT Card Batch Realname Policy Limit
|
||||
|
||||
The IoT card management list MUST limit each realname policy batch submission to 500 selected cards.
|
||||
|
||||
#### Scenario: Prevent card batch submission over the limit
|
||||
|
||||
- **GIVEN** 用户在卡列表选择超过 500 张卡
|
||||
- **WHEN** 用户尝试确认批量修改实名认证策略
|
||||
- **THEN** 页面 MUST prevent the request from being sent
|
||||
- **AND** 页面 MUST display an explicit maximum-500-items error
|
||||
|
||||
### Requirement: IoT Card Batch Policy Is User Selected
|
||||
|
||||
The IoT card management list MUST submit the policy explicitly selected by the user and MUST NOT infer, override, or transform it from asset type, card type, or other asset fields.
|
||||
|
||||
#### Scenario: Preserve selected card policy value
|
||||
|
||||
- **GIVEN** 用户在批量配置弹框选择任一实名认证策略
|
||||
- **WHEN** 用户确认提交
|
||||
- **THEN** 请求中的 `realname_policy` MUST equal the selected option
|
||||
28
openspec/changes/add-asset-batch-realname-policy/tasks.md
Normal file
28
openspec/changes/add-asset-batch-realname-policy/tasks.md
Normal file
@@ -0,0 +1,28 @@
|
||||
## 1. API Contract
|
||||
|
||||
- [x] 1.1 定义批量实名认证策略请求类型,包含 `asset_ids:int64[]` 与 `realname_policy:none|before_order|after_order`。
|
||||
- [x] 1.2 接入卡批量更新接口 `POST /api/admin/iot-cards/batch-update-realname-policy`。
|
||||
- [x] 1.3 接入设备批量更新接口 `POST /api/admin/devices/batch-update-realname-policy`。
|
||||
|
||||
## 2. IoT Card Batch Configuration
|
||||
|
||||
- [x] 2.1 在卡列表多选操作区增加“批量修改实名顺序”入口。
|
||||
- [x] 2.2 弹框展示已选卡数量并提供三种互斥实名认证策略。
|
||||
- [x] 2.3 超过 500 张卡时阻止提交并显示明确提示。
|
||||
- [x] 2.4 成功后关闭弹框并刷新卡列表;失败时保留选择并展示后端业务原因。
|
||||
|
||||
## 3. Device Batch Configuration
|
||||
|
||||
- [x] 3.1 在设备列表多选操作区增加“批量修改实名顺序”入口。
|
||||
- [x] 3.2 弹框展示已选设备数量并提供三种互斥实名认证策略。
|
||||
- [x] 3.3 展示“实际H5流程由设备策略决定”提示。
|
||||
- [x] 3.4 超过 500 台设备时阻止提交并显示明确提示。
|
||||
- [x] 3.5 成功后关闭弹框并刷新设备列表;失败时保留选择并展示后端业务原因。
|
||||
|
||||
## 4. Policy Integrity and Verification
|
||||
|
||||
- [x] 4.1 前端不根据资产类型、卡类型或其他字段覆盖或推导提交策略。
|
||||
- [ ] 4.2 验证卡和设备三种策略均按所选值提交,且单次 500 条以内成功。
|
||||
- [ ] 4.3 验证超过 500 条、后端全成全败失败和网络失败均显示明确错误且不部分刷新列表。
|
||||
- [ ] 4.4 验证设备弹框显示 H5 流程归属提示。
|
||||
- [x] 4.5 运行相关前端校验,并执行 `openspec validate add-asset-batch-realname-policy --strict`。
|
||||
@@ -0,0 +1,41 @@
|
||||
## Context
|
||||
|
||||
运营需要在资产层查看当前主套餐及所有排队主套餐顺序接续后的预计最终到期时间。该结果依赖后端套餐队列、激活条件与计时规则,前端只负责展示接口结果。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals:
|
||||
- 在资产详情、IoT 卡列表和设备列表统一展示“预计套餐到期时间”。
|
||||
- 区分可精确预计与待激活后才可计算的状态。
|
||||
- 对临期资产提供基于后端剩余天数的视觉提示。
|
||||
- Non-Goals:
|
||||
- 不修改单个套餐明细的“到期时间”展示或套餐队列顺序。
|
||||
- 不新增预计到期时间筛选、排序或前端日期计算。
|
||||
- 不改变套餐续费、激活或到期规则。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 统一使用以下五个后台响应字段:`estimated_final_expires_at`、`days_until_final_expiry`、`expiry_estimate_status`、`expiry_estimate_status_name`、`is_expiring`,不调用额外计算接口。
|
||||
- Decision: `expiry_estimate_status` 仅使用 `exact`、`waiting_activation`、`none`、`invalid_data`。除 `exact` 外,`estimated_final_expires_at` 和 `days_until_final_expiry` 必须为 `null`;已过期的 `exact` 资产允许返回负数剩余天数。
|
||||
- Decision: 仅当 `expiry_estimate_status=exact` 且存在 `estimated_final_expires_at` 时格式化展示日期;不可预计状态展示“待激活后起算”。
|
||||
- Decision: `is_expiring=true` 是临期样式的唯一触发条件,`days_until_final_expiry` 只作为剩余天数展示或样式辅助信息,前端不自行判定临期阈值。
|
||||
- Decision: 普通卡和设备列表保持既有服务端返回顺序与前端排序行为,不因临期字段重排。
|
||||
- Alternatives considered: 前端根据当前套餐到期时间、排队套餐时长和计时基准计算最终日期。未采用,因为等待激活和后端队列规则会导致结果不准确。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 后端缺少预计字段时无法显示最终日期 -> 对空值显示稳定占位,不以当前套餐日期替代。
|
||||
- 未知 `expiry_estimate_status` 可能导致错误日期展示 -> 仅 `exact` 可显示日期,其他状态显示稳定占位或后端约定的不可预计提示。
|
||||
- 列表增加时间列会占用宽度 -> 作为可配置动态列,沿用现有横向滚动与列选择能力。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 扩展资产详情及卡、设备列表类型以保留预计最终到期字段。
|
||||
2. 将资产详情响应字段映射到页面状态,并在基础信息区域展示。
|
||||
3. 在卡和设备列表增加预计套餐到期时间列及临期样式。
|
||||
4. 验证无套餐、仅当前套餐、多个排队套餐和待激活后起算四类响应。
|
||||
5. 如需回滚,移除新增展示字段和列表列;不涉及数据迁移。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 后端若返回未约定的状态值,前端不得按 `estimated_final_expires_at` 是否为空展示日期,应按不可预计状态处理。
|
||||
@@ -0,0 +1,40 @@
|
||||
# Change: 新增资产预计套餐到期时间展示
|
||||
|
||||
## Why
|
||||
|
||||
当前页面只能在套餐明细中查看单个套餐的到期时间,运营无法快速了解当前主套餐与全部排队主套餐接续后的资产最终到期时间。前端也不能可靠地自行叠加套餐时长,尤其当套餐需要激活后才开始计时时。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在资产详情、IoT 卡列表和设备列表增加统一的 `预计套餐到期时间` 展示。
|
||||
- 资产详情接口和资产列表响应支持统一的 5 个字段:`estimated_final_expires_at`、`days_until_final_expiry`、`expiry_estimate_status`、`expiry_estimate_status_name` 和 `is_expiring`。
|
||||
- `expiry_estimate_status` 使用 `exact`、`waiting_activation`、`none`、`invalid_data` 四种状态;非 `exact` 状态下日期和剩余天数字段必须为 `null`。
|
||||
- 当 `expiry_estimate_status=exact` 时,展示后端返回的 `estimated_final_expires_at`。
|
||||
- 当套餐尚待激活等无法预计最终日期时,展示“待激活后起算”,不得伪造日期。
|
||||
- 当 `is_expiring=true` 时,按后端返回的剩余天数使用临期颜色提示;普通资产列表不得因临期状态改变既有排序。
|
||||
- 当前套餐自身的到期时间继续仅在套餐明细中展示;前端不得叠加套餐时长计算预计最终到期时间。
|
||||
- 本次仅覆盖后台资产详情、IoT 卡列表和设备列表,不处理 C 端资产信息接口或页面。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-information`
|
||||
- `iot-card-management`
|
||||
- `device-management`
|
||||
- Affected code:
|
||||
- `src/types/api/asset.ts`
|
||||
- `src/types/api/card.ts`
|
||||
- `src/types/api/device.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`
|
||||
- `src/views/asset-management/iot-card-management/index.vue`
|
||||
- `src/views/asset-management/device-list/index.vue`
|
||||
- API contracts:
|
||||
- `GET /api/admin/assets/resolve/{identifier}`
|
||||
- `GET /api/admin/iot-cards/standalone`
|
||||
- `GET /api/admin/devices`
|
||||
- Dependencies:
|
||||
- 后端在资产详情与资产列表响应中返回预计最终到期字段。
|
||||
- Out of scope:
|
||||
- `GET /api/c/v1/asset/info` 及 C 端资产信息页面
|
||||
@@ -0,0 +1,86 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Asset Estimated Final Expiry Contract
|
||||
|
||||
The admin asset information integration SHALL preserve the five backend fields `estimated_final_expires_at`, `days_until_final_expiry`, `expiry_estimate_status`, `expiry_estimate_status_name`, and `is_expiring` returned by `GET /api/admin/assets/resolve/{identifier}`. `estimated_final_expires_at` SHALL be an RFC3339 string or `null`, `days_until_final_expiry` SHALL be an integer or `null`, and `expiry_estimate_status` SHALL be one of `exact`, `waiting_activation`, `none`, or `invalid_data`. This requirement applies only to the admin frontend and excludes C-end asset information.
|
||||
|
||||
#### Scenario: Preserve an exact final expiry estimate
|
||||
|
||||
- **GIVEN** 用户查询后台资产详情
|
||||
- **WHEN** `GET /api/admin/assets/resolve/{identifier}` returns `expiry_estimate_status=exact`
|
||||
- **THEN** 前端状态 MUST preserve `estimated_final_expires_at` as `string | null`
|
||||
- **AND** 前端状态 MUST preserve `days_until_final_expiry` as `number | null`
|
||||
- **AND** 前端状态 MUST preserve `is_expiring` as a boolean
|
||||
- **AND** 前端状态 MUST preserve `expiry_estimate_status_name` as the backend-provided status name
|
||||
|
||||
#### Scenario: Preserve null fields for non-exact estimates
|
||||
|
||||
- **GIVEN** 用户查询后台资产详情
|
||||
- **WHEN** `expiry_estimate_status` is `waiting_activation`, `none`, or `invalid_data`
|
||||
- **THEN** `estimated_final_expires_at` MUST be preserved as `null`
|
||||
- **AND** `days_until_final_expiry` MUST be preserved as `null`
|
||||
- **AND** 前端 MUST NOT calculate either field
|
||||
|
||||
#### Scenario: Preserve an unavailable final expiry estimate
|
||||
|
||||
- **GIVEN** 用户查询后台资产详情
|
||||
- **WHEN** 接口返回待激活或其他不可预计的 `expiry_estimate_status`
|
||||
- **THEN** 前端状态 MUST preserve `expiry_estimate_status`
|
||||
- **AND** 前端 MUST NOT derive `estimated_final_expires_at` from current-package or package-detail fields
|
||||
- **AND** 前端 MUST NOT use `expiry_estimate_status_name` as a substitute for the status enum when choosing the display rule
|
||||
|
||||
### Requirement: Asset Estimated Final Expiry Display
|
||||
|
||||
The admin asset information view SHALL display one asset-level field labeled `预计套餐到期时间` for the current primary package and all queued primary packages, without replacing individual package expiry dates in package details.
|
||||
|
||||
#### Scenario: Display an exact final expiry date
|
||||
|
||||
- **GIVEN** 资产详情返回 `expiry_estimate_status=exact`
|
||||
- **AND** `estimated_final_expires_at` has a value
|
||||
- **WHEN** 页面渲染卡资产或设备资产基础信息
|
||||
- **THEN** 页面 MUST display `预计套餐到期时间`
|
||||
- **AND** 页面 MUST format and display `estimated_final_expires_at`
|
||||
|
||||
#### Scenario: Display activation-pending final expiry
|
||||
|
||||
- **GIVEN** 资产详情返回 `expiry_estimate_status=waiting_activation`
|
||||
- **WHEN** 页面渲染卡资产或设备资产基础信息
|
||||
- **THEN** `预计套餐到期时间` MUST display `待激活后起算`
|
||||
- **AND** 页面 MUST NOT display a fabricated date
|
||||
|
||||
#### Scenario: Handle an unknown estimate status safely
|
||||
|
||||
- **GIVEN** 资产详情返回未约定的 `expiry_estimate_status`
|
||||
- **WHEN** 页面渲染资产基础信息
|
||||
- **THEN** 页面 MUST treat the estimate as unavailable
|
||||
- **AND** 页面 MUST NOT display `estimated_final_expires_at` as a date
|
||||
|
||||
#### Scenario: Display no-package placeholder
|
||||
|
||||
- **GIVEN** 资产没有当前或排队主套餐
|
||||
- **AND** `estimated_final_expires_at` is null or absent
|
||||
- **WHEN** 页面渲染资产基础信息
|
||||
- **THEN** `预计套餐到期时间` MUST display a stable placeholder
|
||||
- **AND** 页面 MUST NOT substitute the current package detail expiry date
|
||||
|
||||
#### Scenario: Highlight backend-designated expiring asset
|
||||
|
||||
- **GIVEN** 资产详情返回 `is_expiring=true`
|
||||
- **WHEN** 页面渲染 `预计套餐到期时间`
|
||||
- **THEN** 页面 MUST apply the expiring visual treatment using `days_until_final_expiry`
|
||||
- **AND** 页面 MUST NOT derive whether the asset is expiring from a locally calculated date difference
|
||||
|
||||
#### Scenario: Preserve package detail expiry semantics
|
||||
|
||||
- **GIVEN** 用户查看资产详情中的套餐明细
|
||||
- **WHEN** 页面渲染单个套餐的到期时间
|
||||
- **THEN** 页面 MUST continue to display that package's own expiry field in the package detail context
|
||||
- **AND** 页面 MUST NOT replace it with `estimated_final_expires_at`
|
||||
|
||||
#### Scenario: Display no-package and invalid-data statuses
|
||||
|
||||
- **GIVEN** 资产详情返回 `expiry_estimate_status=none` 或 `expiry_estimate_status=invalid_data`
|
||||
- **WHEN** 页面渲染资产基础信息
|
||||
- **THEN** `none` MUST display a stable empty placeholder
|
||||
- **AND** `invalid_data` MUST display `数据异常`
|
||||
- **AND** 页面 MUST NOT display a fabricated date
|
||||
@@ -0,0 +1,54 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Device Estimated Final Expiry Display
|
||||
|
||||
The device management list integration SHALL preserve and display the five backend device-level estimated final package expiry fields `estimated_final_expires_at`, `days_until_final_expiry`, `expiry_estimate_status`, `expiry_estimate_status_name`, and `is_expiring` returned in `data.items[]` by `GET /api/admin/devices`. The status SHALL be one of `exact`, `waiting_activation`, `none`, or `invalid_data`; non-`exact` records SHALL have `estimated_final_expires_at=null` and `days_until_final_expiry=null`. The frontend SHALL NOT traverse bound cards or calculate package continuation dates. This requirement applies only to the admin device list.
|
||||
|
||||
#### Scenario: Display exact device final expiry estimate
|
||||
|
||||
- **GIVEN** 设备列表接口返回 `expiry_estimate_status=exact` and `estimated_final_expires_at`
|
||||
- **WHEN** 页面渲染设备列表行
|
||||
- **THEN** 页面 MUST display a column labeled `预计套餐到期时间`
|
||||
- **AND** 该列 MUST format and display `estimated_final_expires_at`
|
||||
|
||||
#### Scenario: Display activation-pending device final expiry
|
||||
|
||||
- **GIVEN** 设备列表接口返回 `expiry_estimate_status=waiting_activation`
|
||||
- **WHEN** 页面渲染设备列表行
|
||||
- **THEN** `预计套餐到期时间` MUST display `待激活后起算`
|
||||
- **AND** 页面 MUST NOT traverse bound cards or display a fabricated date
|
||||
|
||||
#### Scenario: Display device estimate status names for non-exact states
|
||||
|
||||
- **GIVEN** 设备列表接口返回 `expiry_estimate_status=none` 或 `expiry_estimate_status=invalid_data`
|
||||
- **WHEN** 页面渲染设备列表行
|
||||
- **THEN** `none` MUST display a stable empty placeholder
|
||||
- **AND** `invalid_data` MUST display `数据异常`
|
||||
- **AND** 页面 MUST use the status enum to choose the display rule
|
||||
|
||||
#### Scenario: Preserve null fields for non-exact device estimates
|
||||
|
||||
- **GIVEN** 设备列表接口返回 `expiry_estimate_status=none` 或 `expiry_estimate_status=invalid_data`
|
||||
- **THEN** `estimated_final_expires_at` MUST be `null`
|
||||
- **AND** `days_until_final_expiry` MUST be `null`
|
||||
- **AND** 页面 MUST NOT derive either field from绑定卡或套餐数据
|
||||
|
||||
#### Scenario: Highlight expiring device without reordering
|
||||
|
||||
- **GIVEN** 设备列表接口返回 `is_expiring=true` and `days_until_final_expiry`
|
||||
- **WHEN** 页面渲染该设备的预计套餐到期时间
|
||||
- **THEN** 页面 MUST apply the expiring visual treatment based on the backend fields
|
||||
- **AND** 页面 MUST NOT change the ordinary device list sort order because of `is_expiring`
|
||||
|
||||
#### Scenario: Display no-package device placeholder
|
||||
|
||||
- **GIVEN** 设备列表记录没有可预计的最终到期时间
|
||||
- **WHEN** 页面渲染预计套餐到期时间列
|
||||
- **THEN** 页面 MUST display a stable placeholder
|
||||
- **AND** 页面 MUST NOT use an individual package expiry as a substitute
|
||||
|
||||
#### Scenario: Preserve device status name without using it for business calculation
|
||||
|
||||
- **WHEN** 设备列表接口返回 `expiry_estimate_status_name`
|
||||
- **THEN** 前端类型 MUST preserve the field
|
||||
- **AND** 页面 MUST NOT calculate or replace the backend status name
|
||||
@@ -0,0 +1,54 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: IoT Card Estimated Final Expiry Display
|
||||
|
||||
The IoT card management list integration SHALL preserve and display the five backend asset-level estimated final package expiry fields `estimated_final_expires_at`, `days_until_final_expiry`, `expiry_estimate_status`, `expiry_estimate_status_name`, and `is_expiring` returned in `data.items[]` by `GET /api/admin/iot-cards/standalone`. The status SHALL be one of `exact`, `waiting_activation`, `none`, or `invalid_data`; non-`exact` records SHALL have `estimated_final_expires_at=null` and `days_until_final_expiry=null`. The frontend SHALL NOT calculate package continuation dates. This requirement applies only to the admin IoT card list.
|
||||
|
||||
#### Scenario: Display exact card final expiry estimate
|
||||
|
||||
- **GIVEN** 卡列表接口返回 `expiry_estimate_status=exact` and `estimated_final_expires_at`
|
||||
- **WHEN** 页面渲染卡列表行
|
||||
- **THEN** 页面 MUST display a column labeled `预计套餐到期时间`
|
||||
- **AND** 该列 MUST format and display `estimated_final_expires_at`
|
||||
|
||||
#### Scenario: Display activation-pending card final expiry
|
||||
|
||||
- **GIVEN** 卡列表接口返回 `expiry_estimate_status=waiting_activation`
|
||||
- **WHEN** 页面渲染卡列表行
|
||||
- **THEN** `预计套餐到期时间` MUST display `待激活后起算`
|
||||
- **AND** 页面 MUST NOT calculate or display a fabricated date
|
||||
|
||||
#### Scenario: Display card estimate status names for non-exact states
|
||||
|
||||
- **GIVEN** 卡列表接口返回 `expiry_estimate_status=none` 或 `expiry_estimate_status=invalid_data`
|
||||
- **WHEN** 页面渲染卡列表行
|
||||
- **THEN** `none` MUST display a stable empty placeholder
|
||||
- **AND** `invalid_data` MUST display `数据异常`
|
||||
- **AND** 页面 MUST use the status enum to choose the display rule
|
||||
|
||||
#### Scenario: Preserve null fields for non-exact card estimates
|
||||
|
||||
- **GIVEN** 卡列表接口返回 `expiry_estimate_status=none` 或 `expiry_estimate_status=invalid_data`
|
||||
- **THEN** `estimated_final_expires_at` MUST be `null`
|
||||
- **AND** `days_until_final_expiry` MUST be `null`
|
||||
- **AND** 页面 MUST NOT derive either field from套餐数据
|
||||
|
||||
#### Scenario: Highlight expiring card without reordering
|
||||
|
||||
- **GIVEN** 卡列表接口返回 `is_expiring=true` and `days_until_final_expiry`
|
||||
- **WHEN** 页面渲染该卡的预计套餐到期时间
|
||||
- **THEN** 页面 MUST apply the expiring visual treatment based on the backend fields
|
||||
- **AND** 页面 MUST NOT change the ordinary card list sort order because of `is_expiring`
|
||||
|
||||
#### Scenario: Display no-package card placeholder
|
||||
|
||||
- **GIVEN** 卡列表记录没有可预计的最终到期时间
|
||||
- **WHEN** 页面渲染预计套餐到期时间列
|
||||
- **THEN** 页面 MUST display a stable placeholder
|
||||
- **AND** 页面 MUST NOT use an individual package expiry as a substitute
|
||||
|
||||
#### Scenario: Preserve card status name without using it for business calculation
|
||||
|
||||
- **WHEN** 卡列表接口返回 `expiry_estimate_status_name`
|
||||
- **THEN** 前端类型 MUST preserve the field
|
||||
- **AND** 页面 MUST NOT calculate or replace the backend status name
|
||||
@@ -0,0 +1,26 @@
|
||||
## 1. API Contracts And Types
|
||||
|
||||
- [x] 1.1 扩展资产详情响应和资产信息页面状态,支持 5 个预计最终到期字段:`estimated_final_expires_at`、`days_until_final_expiry`、`expiry_estimate_status`、`expiry_estimate_status_name`、`is_expiring`。
|
||||
- [x] 1.2 扩展 IoT 卡和设备列表项类型,支持 5 个预计最终到期字段;不处理 C 端字段。
|
||||
- [x] 1.3 校验四种状态及字段约束:`exact` 可返回日期和剩余天数,其他状态的 `estimated_final_expires_at` 与 `days_until_final_expiry` 必须为 `null`。
|
||||
|
||||
## 2. Asset Information
|
||||
|
||||
- [x] 2.1 将资产解析接口返回的预计最终到期字段映射到资产详情页面状态。
|
||||
- [x] 2.2 在资产详情卡和设备基础信息中展示“预计套餐到期时间”。
|
||||
- [x] 2.3 按 `expiry_estimate_status` 展示:`exact` 显示日期,`waiting_activation` 显示“待激活后起算”,`none` 显示占位,`invalid_data` 显示“数据异常”。
|
||||
- [x] 2.4 `is_expiring=true` 时按 `days_until_final_expiry` 应用临期样式,不根据日期或天数自行推导临期状态。
|
||||
|
||||
## 3. Asset Lists
|
||||
|
||||
- [x] 3.1 在 IoT 卡列表新增“预计套餐到期时间”可配置列,显示接口返回的预计日期或“待激活后起算”。
|
||||
- [x] 3.2 在设备列表新增“预计套餐到期时间”可配置列,显示接口返回的预计日期或“待激活后起算”。
|
||||
- [x] 3.3 在两个列表对 `is_expiring=true` 的预计到期时间使用临期样式,且不改变现有列表排序。
|
||||
|
||||
## 4. Verification
|
||||
|
||||
- [x] 4.1 验证无套餐时不伪造预计日期并显示稳定占位内容。
|
||||
- [x] 4.2 验证仅当前套餐和存在多个排队主套餐时,资产详情和两个列表均显示后端 `estimated_final_expires_at`。
|
||||
- [x] 4.3 验证等待激活等不可预计状态显示“待激活后起算”,不显示计算出的日期。
|
||||
- [x] 4.4 验证 `is_expiring=true` 时使用临期样式,且卡、设备列表顺序不变。
|
||||
- [x] 4.5 运行相关类型检查、lint 或构建验证。
|
||||
@@ -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.
|
||||
37
openspec/changes/add-asset-realname-status-filter/design.md
Normal file
37
openspec/changes/add-asset-realname-status-filter/design.md
Normal file
@@ -0,0 +1,37 @@
|
||||
## Context
|
||||
|
||||
卡和设备列表需要新增统一的实名状态筛选与展示能力。设备的实名状态由设备列表接口直接返回,不能通过关联卡在前端二次计算,以避免多卡设备或卡绑定关系变化时出现不一致。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals:
|
||||
- 支持按“全部”“已实名”“未实名”筛选卡和设备。
|
||||
- 直接展示后端返回的实名状态名称。
|
||||
- 在搜索、刷新、分页和导出查询中保留当前筛选条件。
|
||||
- Non-Goals:
|
||||
- 不新增或修改实名认证流程、策略配置或状态更新操作。
|
||||
- 不在前端推导设备实名状态。
|
||||
- 不变更其他资产详情页的实名状态取值规则。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 使用可选数值查询参数 `real_name_status`,其中 `0` 表示未实名、`1` 表示已实名;“全部”对应不传该参数。
|
||||
- Decision: 列表展示优先使用每条记录的 `real_name_status_name`,而非根据 `real_name_status` 写死文案。
|
||||
- Decision: 设备列表把接口响应中的 `real_name_status` 与 `real_name_status_name` 作为唯一状态来源,不读取或遍历绑定卡数据。
|
||||
- Alternatives considered: 前端将 `0` 和 `1` 映射为固定文案。未采用,因为后端已提供标准显示名称,直接使用可避免展示口径分叉。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 后端未返回 `real_name_status_name` 时无法满足状态名称展示契约 -> 联调时校验列表响应字段,并将该字段设为必需的列表类型字段。
|
||||
- 卡列表实名认证筛选依赖单卡列表接口 -> 实施时确保筛选参数发往 `GET /api/admin/iot-cards/standalone`。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 扩展卡与设备列表 API 类型和查询参数。
|
||||
2. 接入筛选控件、查询参数及状态列。
|
||||
3. 验证全部、已实名、未实名筛选以及分页和重置行为。
|
||||
4. 如需回滚,移除前端筛选控件、查询参数和状态列;不涉及数据迁移。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 无。
|
||||
@@ -0,0 +1,33 @@
|
||||
# Change: 新增卡和设备实名状态筛选
|
||||
|
||||
## Why
|
||||
|
||||
运营人员需要在卡列表和设备列表中快速识别并筛选已实名或未实名的资产。当前页面未完整接入实名状态筛选和后端返回的实名状态名称,设备列表尤其不能依赖前端遍历绑定卡来推导状态。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 卡列表和设备列表的筛选区新增“实名状态”,提供“全部”“已实名”“未实名”选项。
|
||||
- 卡列表查询使用 `GET /api/admin/iot-cards/standalone`,设备列表查询使用 `GET /api/admin/devices`;选择状态后分别传递 `real_name_status=0|1`,未选择时不传该参数。
|
||||
- 卡和设备列表项的类型契约支持 `real_name_status: int` 与 `real_name_status_name: string`。
|
||||
- 两个列表表格新增“实名状态”列,直接展示接口返回的 `real_name_status_name`。
|
||||
- 设备列表直接使用设备列表接口的实名状态字段,不遍历或关联绑定卡计算设备实名状态。
|
||||
- 搜索、刷新和分页切换必须保留当前实名状态筛选;重置搜索时清空该筛选。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `iot-card-management`
|
||||
- `device-management`
|
||||
- Affected code:
|
||||
- `src/api/modules/card.ts`
|
||||
- `src/api/modules/device.ts`
|
||||
- `src/types/api/card.ts`
|
||||
- `src/types/api/device.ts`
|
||||
- `src/views/asset-management/iot-card-management/index.vue`
|
||||
- `src/views/asset-management/device-list/index.vue`
|
||||
- API contracts:
|
||||
- `GET /api/admin/iot-cards/standalone?real_name_status=0|1`
|
||||
- `GET /api/admin/devices?real_name_status=0|1`
|
||||
- List items return `real_name_status: int` and `real_name_status_name: string`
|
||||
- Dependencies:
|
||||
- 后端列表接口必须支持实名状态查询并返回实名状态名称。
|
||||
@@ -0,0 +1,68 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Device Realname Status Query Contract
|
||||
|
||||
The device management list integration SHALL support an optional numeric `real_name_status` parameter on `GET /api/admin/devices`. The list-item contract SHALL include `real_name_status` and `real_name_status_name` returned by the device list API.
|
||||
|
||||
#### Scenario: Query devices by realname status
|
||||
|
||||
- **GIVEN** 用户正在后台设备列表使用实名状态筛选
|
||||
- **WHEN** 用户选择“已实名”并执行搜索
|
||||
- **THEN** 系统 MUST call `GET /api/admin/devices` with `real_name_status=1`
|
||||
|
||||
#### Scenario: Query unverified devices
|
||||
|
||||
- **GIVEN** 用户正在后台设备列表使用实名状态筛选
|
||||
- **WHEN** 用户选择“未实名”并执行搜索
|
||||
- **THEN** 系统 MUST call `GET /api/admin/devices` with `real_name_status=0`
|
||||
- **AND** 前端 MUST NOT 因为该值为 `0` 而省略此参数
|
||||
|
||||
#### Scenario: Query all devices without status restriction
|
||||
|
||||
- **GIVEN** 用户未选择实名状态或选择“全部”
|
||||
- **WHEN** 用户查询、刷新或切换设备列表分页
|
||||
- **THEN** 请求 MUST NOT 携带 `real_name_status`
|
||||
|
||||
#### Scenario: Receive device realname status fields
|
||||
|
||||
- **GIVEN** 设备列表接口返回设备记录
|
||||
- **WHEN** 前端解析列表响应
|
||||
- **THEN** 列表项类型 MUST 支持 `real_name_status: int`
|
||||
- **AND** 列表项类型 MUST 支持 `real_name_status_name: string`
|
||||
|
||||
### Requirement: Device Realname Status Filter And Display
|
||||
|
||||
The device management page SHALL provide a `实名状态` filter with `全部`、`已实名`、`未实名` options and display the backend device realname status name in the device table.
|
||||
|
||||
#### Scenario: Display device realname status filter
|
||||
|
||||
- **GIVEN** 用户打开后台设备列表
|
||||
- **WHEN** 页面渲染筛选区
|
||||
- **THEN** 页面 MUST display a `实名状态` filter
|
||||
- **AND** 筛选项 MUST provide `全部`、`已实名`、`未实名` options
|
||||
|
||||
#### Scenario: Display backend device realname status name
|
||||
|
||||
- **GIVEN** 设备列表接口返回某条记录的 `real_name_status_name`
|
||||
- **WHEN** 页面渲染该设备的表格行
|
||||
- **THEN** 页面 MUST 在“实名状态”列显示该字段值
|
||||
|
||||
#### Scenario: Use the device API as the status source
|
||||
|
||||
- **GIVEN** 设备列表接口返回设备的实名状态字段
|
||||
- **WHEN** 页面渲染设备实名状态
|
||||
- **THEN** 页面 MUST directly use the record's `real_name_status` and `real_name_status_name`
|
||||
- **AND** 页面 MUST NOT 遍历、绑定或计算关联卡的实名状态
|
||||
|
||||
#### Scenario: Preserve device realname status while paginating
|
||||
|
||||
- **GIVEN** 用户已选择“已实名”或“未实名”并获得筛选结果
|
||||
- **WHEN** 用户切换设备列表页码或每页条数
|
||||
- **THEN** 后续列表请求 MUST 保留当前的 `real_name_status` 参数
|
||||
|
||||
#### Scenario: Reset device realname status filter
|
||||
|
||||
- **GIVEN** 用户已选择实名状态
|
||||
- **WHEN** 用户重置设备列表搜索条件
|
||||
- **THEN** 页面 MUST 清空实名状态筛选
|
||||
- **AND** 后续列表请求 MUST NOT 携带 `real_name_status`
|
||||
@@ -0,0 +1,61 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: IoT Card Realname Status Query Contract
|
||||
|
||||
The IoT card management list integration SHALL query `GET /api/admin/iot-cards/standalone` and support an optional numeric `real_name_status` parameter. The list-item contract SHALL include `real_name_status` and `real_name_status_name`.
|
||||
|
||||
#### Scenario: Query cards by realname status
|
||||
|
||||
- **GIVEN** 用户正在后台卡列表使用实名状态筛选
|
||||
- **WHEN** 用户选择“已实名”并执行搜索
|
||||
- **THEN** 系统 MUST call `GET /api/admin/iot-cards/standalone` with `real_name_status=1`
|
||||
|
||||
#### Scenario: Query unverified cards
|
||||
|
||||
- **GIVEN** 用户正在后台卡列表使用实名状态筛选
|
||||
- **WHEN** 用户选择“未实名”并执行搜索
|
||||
- **THEN** 系统 MUST call `GET /api/admin/iot-cards/standalone` with `real_name_status=0`
|
||||
- **AND** 前端 MUST NOT 因为该值为 `0` 而省略此参数
|
||||
|
||||
#### Scenario: Query all cards without status restriction
|
||||
|
||||
- **GIVEN** 用户未选择实名状态或选择“全部”
|
||||
- **WHEN** 用户查询、刷新或切换卡列表分页
|
||||
- **THEN** 请求 MUST NOT 携带 `real_name_status`
|
||||
|
||||
#### Scenario: Receive card realname status fields
|
||||
|
||||
- **GIVEN** 卡列表接口返回资产记录
|
||||
- **WHEN** 前端解析列表响应
|
||||
- **THEN** 列表项类型 MUST 支持 `real_name_status: int`
|
||||
- **AND** 列表项类型 MUST 支持 `real_name_status_name: string`
|
||||
|
||||
### Requirement: IoT Card Realname Status Filter And Display
|
||||
|
||||
The IoT card management page SHALL provide a `实名状态` filter with `全部`、`已实名`、`未实名` options and display the backend realname status name in the card table.
|
||||
|
||||
#### Scenario: Display card realname status filter
|
||||
|
||||
- **GIVEN** 用户打开后台卡列表
|
||||
- **WHEN** 页面渲染筛选区
|
||||
- **THEN** 页面 MUST display a `实名状态` filter
|
||||
- **AND** 筛选项 MUST provide `全部`、`已实名`、`未实名` options
|
||||
|
||||
#### Scenario: Display backend card realname status name
|
||||
|
||||
- **GIVEN** 卡列表接口返回某条记录的 `real_name_status_name`
|
||||
- **WHEN** 页面渲染该卡的表格行
|
||||
- **THEN** 页面 MUST 在“实名状态”列显示该字段值
|
||||
|
||||
#### Scenario: Preserve card realname status while paginating
|
||||
|
||||
- **GIVEN** 用户已选择“已实名”或“未实名”并获得筛选结果
|
||||
- **WHEN** 用户切换卡列表页码或每页条数
|
||||
- **THEN** 后续列表请求 MUST 保留当前的 `real_name_status` 参数
|
||||
|
||||
#### Scenario: Reset card realname status filter
|
||||
|
||||
- **GIVEN** 用户已选择实名状态
|
||||
- **WHEN** 用户重置卡列表搜索条件
|
||||
- **THEN** 页面 MUST 清空实名状态筛选
|
||||
- **AND** 后续列表请求 MUST NOT 携带 `real_name_status`
|
||||
26
openspec/changes/add-asset-realname-status-filter/tasks.md
Normal file
26
openspec/changes/add-asset-realname-status-filter/tasks.md
Normal file
@@ -0,0 +1,26 @@
|
||||
## 1. API Contracts And Types
|
||||
|
||||
- [x] 1.1 扩展卡列表查询参数和列表项类型,支持可选 `real_name_status` 以及必需的 `real_name_status_name`。
|
||||
- [x] 1.2 扩展设备列表查询参数和列表项类型,支持可选 `real_name_status` 以及必需的 `real_name_status_name`。
|
||||
- [x] 1.3 将卡列表查询接入 `GET /api/admin/iot-cards/standalone` 并传递实名状态筛选参数。
|
||||
|
||||
## 2. Card List
|
||||
|
||||
- [x] 2.1 在卡列表筛选区新增“实名状态”的全部、已实名、未实名选项。
|
||||
- [x] 2.2 将选中的实名状态传递给卡列表查询,并在搜索、刷新、分页、导出中保留该条件。
|
||||
- [x] 2.3 在卡列表表格新增“实名状态”列,展示接口返回的 `real_name_status_name`。
|
||||
- [x] 2.4 重置卡列表搜索时清空实名状态筛选。
|
||||
|
||||
## 3. Device List
|
||||
|
||||
- [x] 3.1 在设备列表筛选区新增“实名状态”的全部、已实名、未实名选项。
|
||||
- [x] 3.2 将选中的实名状态传递给 `GET /api/admin/devices`,并在搜索、刷新、分页、导出中保留该条件。
|
||||
- [x] 3.3 在设备列表表格新增“实名状态”列,直接展示接口返回的 `real_name_status_name`,不遍历绑定卡计算状态。
|
||||
- [x] 3.4 重置设备列表搜索时清空实名状态筛选。
|
||||
|
||||
## 4. Verification
|
||||
|
||||
- [ ] 4.1 验证卡列表“全部”“已实名”“未实名”分别不传、传 `1`、传 `0`,且状态列显示接口名称。
|
||||
- [ ] 4.2 验证设备列表“全部”“已实名”“未实名”分别不传、传 `1`、传 `0`,且状态列直接显示设备接口名称。
|
||||
- [ ] 4.3 验证两个列表在分页切换、刷新和导出时保留实名状态筛选,重置后清空该条件。
|
||||
- [x] 4.4 运行相关类型检查、lint 或构建验证。
|
||||
@@ -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 验证格式化函数正确处理各状态值
|
||||
@@ -0,0 +1,39 @@
|
||||
# Change: 新增资产钱包自动续费配置(后台查询/保存 + 自动续费失败通知适配)
|
||||
|
||||
## Why
|
||||
|
||||
根据 `docs/产品迭代8月份/资产钱包.md`。后端测试环境(`https://cmp-api.boss160.cn`,`Authorization: Bearer <token>`)已提供资产钱包自动续费全局配置能力,仅有 2 个后台接口,H5 侧零新增:
|
||||
|
||||
- 查询资产钱包自动续费配置:`GET /api/admin/asset-auto-renewal-config`
|
||||
- 保存资产钱包自动续费配置:`PUT /api/admin/asset-auto-renewal-config`
|
||||
|
||||
后台需要提供配置页面承载总开关、适用范围、指定主套餐、到期前天数等配置;同时新增通知类型 `asset.auto_renewal.failed` 会复用既有通知接口产生新数据,需要适配展示与跳转。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增能力 `asset-wallet-auto-renewal`:
|
||||
- 配置读取:`GET /api/admin/asset-auto-renewal-config`,返回唯一一份全局配置的 `enabled`+`enabled_name`、`scope`+`scope_name`、`package_ids`、`days_before_expiry`、`config_version`、`updater`、`updated_at`。
|
||||
- 配置保存:`PUT /api/admin/asset-auto-renewal-config`:
|
||||
- 请求体 `{ enabled(0/1,必填), scope(all|specified,必填), package_ids(uint[],仅 specified 时非空且只能选当前可售主套餐), days_before_expiry(1–90,必填) }`。
|
||||
- 语义:单行配置、无新增/删除;保存即递增 `config_version`,记录操作者与前后值快照;配置变更只影响后续扫描,历史记录不重算。
|
||||
- 权限:仅超级管理员与平台账号可访问;其他身份(代理/企业/个人客户)`403`,提示「无权限操作该资源或资源不存在」,无权限与不存在不区分。
|
||||
- 通知适配(复用既有接口,不算新接口):
|
||||
- 后台站内通知:新增通知类型 `asset.auto_renewal.failed`(类别 `expiry`、级别 `warning`),接收人是业务员/店铺账号。走既有 `GET /api/admin/notifications` + `GET /api/admin/notifications/{id}/target`;确认 `target_type` 的 `iot_card` / `device` 在导航白名单;`available=false` 时只显示正文不跳转;计入未读数。
|
||||
- H5 个人客户通知:同一类型已由后端加入客户可见白名单,出现在既有 `GET /api/c/v1/notifications` 与 `unread-count`,客户侧只有文案(资产标识、套餐、原因、到期日),无跳转接口、无需新页面,本仓库无需改动。该类型属 `expiry` 类别,展示期以业务到期时间为准,套餐到期后从列表消失(既有类别行为)。
|
||||
- 明确不做(避免前端空等):无自动续费记录页/异常记录页接口、无尝试记录查询接口、无「有余额就不停机」开关、无 H5 客户侧新接口。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `asset-wallet-auto-renewal` — 新增能力
|
||||
- Affected code:
|
||||
- `src/types/api/assetWallet.ts`(新增)
|
||||
- `src/types/api/index.ts`
|
||||
- `src/api/modules/assetWallet.ts`(新增)
|
||||
- `src/api/modules/index.ts`
|
||||
- `src/views/settings/asset-wallet-auto-renewal/index.vue`(新增)
|
||||
- `src/router/routesAlias.ts`
|
||||
- `src/router/routes/asyncRoutes.ts`
|
||||
- `src/utils/business/notificationNavigation.ts`(确认/补充 `iot_card`、`device` 白名单)
|
||||
- `src/components/core/layouts/art-notification/index.vue`(确认 `expiry` 分类覆盖新类型)
|
||||
- `src/locales/langs/zh.json`、`src/locales/langs/en.json`
|
||||
@@ -0,0 +1,94 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 自动续费配置查询
|
||||
|
||||
The admin frontend SHALL load the single global asset wallet auto-renewal configuration through `GET /api/admin/asset-auto-renewal-config`. 响应字段 SHALL 包含并展示 `enabled`+`enabled_name`、`scope`+`scope_name`、`package_ids`、`days_before_expiry`、`config_version`、`updater`、`updated_at`。
|
||||
|
||||
#### Scenario: 读取全局自动续费配置
|
||||
|
||||
- **WHEN** 用户进入资产钱包自动续费配置页面
|
||||
- **THEN** 前端 MUST 调用 `GET /api/admin/asset-auto-renewal-config`
|
||||
- **AND** 页面 MUST 展示总开关及中文名称、适用范围及中文名称、指定主套餐集合、统一到期前天数、配置版本、最近保存操作者与最近保存时间
|
||||
|
||||
### Requirement: 自动续费配置保存
|
||||
|
||||
The admin frontend SHALL save the configuration through `PUT /api/admin/asset-auto-renewal-config` with request body `{ enabled, scope, package_ids, days_before_expiry }`。`enabled` SHALL 取值 0/1 且必填;`scope` SHALL 取值 `all`(全部主套餐)或 `specified`(指定主套餐)且必填;`package_ids` 仅在 `scope=specified` 时必填非空且只能选择当前可售主套餐;`days_before_expiry` SHALL 取值 1 至 90 且必填。配置为单行、无新增/删除;保存 SHALL 递增 `config_version` 并记录操作者与前后值快照;配置变更 SHALL 只影响后续扫描,历史记录不重算。
|
||||
|
||||
#### Scenario: 保存全部主套餐范围配置
|
||||
|
||||
- **WHEN** 用户设置适用范围为「全部主套餐」并提交
|
||||
- **THEN** 前端 MUST 调用 `PUT /api/admin/asset-auto-renewal-config`
|
||||
- **AND** 请求体携带 `enabled`、`scope=all`、`days_before_expiry`
|
||||
- **AND** `package_ids` 以空数组提交
|
||||
- **AND** 保存成功后页面 MUST 以响应中的 `config_version`、`updater`、`updated_at` 刷新展示
|
||||
|
||||
#### Scenario: 保存指定主套餐范围配置
|
||||
|
||||
- **WHEN** 用户设置适用范围为「指定主套餐」并选择若干当前可售主套餐后提交
|
||||
- **THEN** `package_ids` MUST 非空且只包含当前可售主套餐
|
||||
- **AND** 前端 MUST 携带 `scope=specified` 与非空 `package_ids` 提交
|
||||
|
||||
#### Scenario: 参数校验
|
||||
|
||||
- **WHEN** `enabled` 缺失、`scope` 非法、`scope=specified` 时 `package_ids` 为空或包含不可售套餐,或 `days_before_expiry` 超出 1–90
|
||||
- **THEN** 前端 MUST 阻止提交并给出校验提示
|
||||
|
||||
#### Scenario: 仅影响后续扫描
|
||||
|
||||
- **WHEN** 用户修改并保存配置
|
||||
- **THEN** 历史自动续费记录 MUST NOT 被重算
|
||||
- **AND** 新配置 MUST 只对保存后的扫描生效
|
||||
|
||||
### Requirement: 自动续费配置访问权限
|
||||
|
||||
Only super admin and platform accounts SHALL be allowed to query or save the asset wallet auto-renewal configuration. 代理、企业与个人客户等身份访问时 SHALL 返回 `403` 并提示「无权限操作该资源或资源不存在」;无权限与不存在的表现 MUST NOT 可区分。
|
||||
|
||||
#### Scenario: 授权访问
|
||||
|
||||
- **WHEN** 超级管理员或平台账号访问配置接口
|
||||
- **THEN** 页面 MUST 正常查询与保存配置
|
||||
|
||||
#### Scenario: 无权限访问
|
||||
|
||||
- **WHEN** 代理、企业或个人客户账号访问配置接口
|
||||
- **THEN** 页面 MUST 按 `403` 无权限处理并展示统一提示
|
||||
- **AND** 前端 MUST NOT 通过响应区分无权限与资源不存在
|
||||
|
||||
### Requirement: 自动续费失败后台通知
|
||||
|
||||
The admin notification center SHALL display the new notification type `asset.auto_renewal.failed`(类别 `expiry`、级别 `warning`)through the existing notification APIs,接收人为业务员/店铺账号。目标 `target_type` 的 `iot_card` 与 `device` SHALL 位于通知导航白名单;当目标 `available=false` 时页面 SHALL 只展示正文且不跳转;该类型通知 SHALL 计入未读数。
|
||||
|
||||
#### Scenario: 展示并跳转自动续费失败通知
|
||||
|
||||
- **WHEN** 通知列表返回 `asset.auto_renewal.failed` 类型且目标可用
|
||||
- **THEN** 通知中心 MUST 将该通知归入 `expiry` 类别展示
|
||||
- **AND** 用户点击后 MUST 通过既有目标接口按 `iot_card` / `device` 跳转到对应资产详情
|
||||
|
||||
#### Scenario: 目标不可用
|
||||
|
||||
- **WHEN** 目标接口返回 `available=false`
|
||||
- **THEN** 页面 MUST 只展示通知正文且不发起跳转
|
||||
|
||||
### Requirement: H5 客户侧通知边界
|
||||
|
||||
This capability SHALL NOT 新增或修改 H5 客户侧接口与页面。`asset.auto_renewal.failed` 类型已由后端加入客户可见白名单,通过既有 `GET /api/c/v1/notifications` 与 `unread-count` 返回;客户侧仅展示文案(资产标识、套餐、原因、到期日),无跳转接口、无需新页面。该类型属 `expiry` 类别,展示期以业务到期时间为准,套餐到期后从列表消失(既有类别行为)。
|
||||
|
||||
#### Scenario: H5 复用既有接口
|
||||
|
||||
- **WHEN** 客户侧通知接口返回该类型
|
||||
- **THEN** 客户侧 MUST 仅展示文案且不提供跳转
|
||||
- **AND** 本次变更 MUST NOT 新增 H5 客户侧接口或页面
|
||||
|
||||
#### Scenario: 到期展示期
|
||||
|
||||
- **WHEN** 对应套餐业务到期
|
||||
- **THEN** 该通知按 `expiry` 类别既有行为从客户侧列表消失
|
||||
|
||||
### Requirement: 功能范围边界
|
||||
|
||||
This capability SHALL NOT 包含以下内容:自动续费记录页/异常记录页、尝试记录查询、「有余额就不停机」开关、H5 客户侧新接口。
|
||||
|
||||
#### Scenario: 明确不提供的功能
|
||||
|
||||
- **WHEN** 前端对接本次资产钱包自动续费能力
|
||||
- **THEN** 页面 MUST NOT 提供或依赖自动续费记录页、异常记录页、尝试记录查询接口与「有余额就不停机」开关
|
||||
@@ -0,0 +1,27 @@
|
||||
# Tasks: 资产钱包自动续费配置
|
||||
|
||||
## 1. 类型与 API
|
||||
- [x] 1.1 新增 `src/types/api/assetWallet.ts`:`AssetAutoRenewalConfig`(`enabled`/`enabled_name`/`scope`/`scope_name`/`package_ids`/`days_before_expiry`/`config_version`/`updater`/`updated_at`)、`UpdateAssetAutoRenewalConfigRequest`(`enabled`/`scope`/`package_ids`/`days_before_expiry`)等类型
|
||||
- [x] 1.2 `src/types/api/index.ts` 导出新类型
|
||||
- [x] 1.3 新增 `src/api/modules/assetWallet.ts`:
|
||||
- `getAutoRenewalConfig`:`GET /api/admin/asset-auto-renewal-config`
|
||||
- `saveAutoRenewalConfig`:`PUT /api/admin/asset-auto-renewal-config`
|
||||
- [x] 1.4 `src/api/modules/index.ts` 导出新服务
|
||||
|
||||
## 2. 配置页面
|
||||
- [x] 2.1 `src/router/routesAlias.ts` 新增资产钱包自动续费配置路由别名,`src/router/routes/asyncRoutes.ts` 在设置下注册路由与菜单(仅超级管理员与平台账号可见)
|
||||
- [x] 2.2 新增 `src/views/settings/asset-wallet-auto-renewal/index.vue`:读取配置并展示总开关、适用范围、指定主套餐、统一到期前天数、配置版本、最近保存操作者与时间(含 `enabled_name`/`scope_name`)
|
||||
- [x] 2.3 实现保存表单:总开关(0/1)、适用范围(all/specified)、到期前天数(1–90 校验);指定范围时主套餐多选仅支持当前可售主套餐且非空
|
||||
- [x] 2.4 保存成功后使用响应刷新 `config_version`、`updater`、`updated_at`,不做新增/删除记录操作
|
||||
|
||||
## 3. 通知适配
|
||||
- [x] 3.1 确认 `src/utils/business/notificationNavigation.ts` 白名单包含 `iot_card` 与 `device`,目标可用时跳转资产详情
|
||||
- [x] 3.2 确认 `src/components/core/layouts/art-notification/index.vue` 的 `expiry` 分类可展示 `asset.auto_renewal.failed`,`available=false` 时只显示正文不跳转
|
||||
- [x] 3.3 确认该类型通知计入未读数与分类汇总
|
||||
|
||||
## 4. Verification
|
||||
- [x] 4.1 验证 GET/PUT 字段传递与参数校验(enabled、scope、package_ids、days_before_expiry)
|
||||
- [x] 4.2 验证指定范围时 package_ids 非空且仅可售主套餐
|
||||
- [x] 4.3 验证通知类型展示、目标跳转与不可用目标处理
|
||||
- [x] 4.4 验证非超级管理员/平台账号访问的 403 处理
|
||||
- [x] 4.5 运行 lint、类型检查与构建
|
||||
@@ -0,0 +1,53 @@
|
||||
## Context
|
||||
|
||||
本次变更横跨平台、代理和企业三类主体以及资产、订单、退款、钱包、通知等多个业务页面。OpenAPI 将关联关系明确建模为 `investigation_refs`、`linkage` 和稳定资源引用,并区分平台内部 ID 与代理/企业可见的业务标识。前端必须保持这些边界,不能为了补齐跳转而从名称、时间或摘要推断关联关系。
|
||||
|
||||
仓库目前没有已归档的基线 specs,但存在通知中心和旧资产操作日志的活跃变更。本提案建立独立的审计链路能力,通过明确的依赖点与它们集成,不复制或覆盖其已有要求。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: 按 OpenAPI 实现 16 个只读接口的类型、查询、页面和跨视角跳转契约。
|
||||
- Goals: 为平台、代理和企业提供符合各自权限与数据投影的业务审计入口。
|
||||
- Goals: 统一分页、RFC3339 时间范围、枚举展示、在线保留窗口和错误处理。
|
||||
- Non-Goals: 不修改后端接口、数据库、日志采集或保留策略。
|
||||
- Non-Goals: 不提供恢复、重试、修改、删除、处置、封禁、任意全文搜索或导出。
|
||||
- Non-Goals: 不替换现有资产操作日志组件,也不修改 C/H5 端。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 新增独立审计 API 模块和共享类型,按平台审计、主体活动、资金、风险、Integration、链路时间线分组暴露查询函数;统一保留服务端响应包装和 nullable 字段。
|
||||
- Decision: 平台业务入口使用响应中的内部稳定 ID。卡、设备、店铺、企业、订单和退款分别使用对应 `resource_type` 与 `response.data.id`;钱包通过资金时间线的 `wallet_id` 进入。
|
||||
- Decision: 代理与企业入口使用响应中的稳定业务标识。卡使用 `iccid`,设备使用 `virtual_no`;代理的分配、换货、店铺和企业使用接口文档指定的业务编号。缺少稳定标识时隐藏入口。
|
||||
- Decision: 前端只转发后端返回的调查引用。事件的 `event_id`、`actor_ref`、`resource_refs`、`request_id`、`correlation_id`、`integration_refs`,以及 Integration 的 `linkage`/`resource` 是跨视角导航的唯一数据来源。
|
||||
- Decision: `request_id` 可以来自调查引用、Integration、或用户从 Access Log 明确粘贴;`correlation_id` 和 `integration_id` 只能来自接口返回的稳定字段。前端不使用 UUID 或其他方式生成这些 ID。
|
||||
- Decision: 对不存在、为空或 `fidelity=false` 的引用隐藏对应跳转,禁止按名称、时间、摘要或相邻记录猜测缺失关系。
|
||||
- Decision: 资源搜索严格使用 `resource_type + keyword` 精确查询,并把选中项的 `resource_type/resource_id` 原样传给资源时间线。`historical=true` 只作为历史快照命中提示。
|
||||
- Decision: 列表和时间线统一消费 `page`、`page_size`、`total` 并保留 `retention` 语义。时间筛选发送含时区的 RFC3339 值,`created_to` 按接口定义为不包含该时刻;页面不展示全局在线窗口提示,也不提供归档查询假入口。
|
||||
- Decision: 所有枚举筛选提交稳定 code,并优先展示后端 `*_name`。`action`、Integration `operation` 等开放编码必须直接来自响应,不能从中文文案反推。
|
||||
- Decision: 资金金额按分展示转换,权威性只认 `amount_authority.authoritative=true` 指向的业务字段;前端不得合并冲突金额或自行计算余额。
|
||||
- Decision: 代理与企业活动共用展示外壳但使用独立 API。企业页面只展示主体安全投影,不引入平台操作者、风险、内部原因或 before/after 字段。
|
||||
- Decision: 通知目标仅在 `available=true`、`target_type=integration_log` 且 `target_key` 非空时跳转,并将 `target_key` 原样作为 Integration 详情的 `integration_id`。其他情况保留通知正文并提示目标不可用。
|
||||
- Decision: 权限以最终菜单/按钮权限编码和服务端鉴权共同控制。平台、代理、企业不展示不属于其主体的审计入口,`401/403` 继续走共享认证与无权处理。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 最终菜单与按钮权限编码尚未体现在 OpenAPI 中;实施前必须确认,否则只能依赖服务端 `403`,无法做到准确的入口隐藏。
|
||||
- 审计事件和 Integration 模型字段较多;通过共享详情/时间线组件和严格类型避免各业务页重复实现,但不抽象为可以执行任意端点的动态页面。
|
||||
- 在线保留窗口外的数据不可由这些接口查询;空状态使用“当前查询无记录”的中性表达,避免将空数据误报为无历史事件。
|
||||
- 活跃通知中心变更也会修改通知导航;实施时需在其最新状态上追加 `integration_log` 规则,避免覆盖既有白名单映射。
|
||||
- 旧资产操作日志与新审计中心含义相邻但数据源不同;两个入口并存并清晰命名,避免误将旧日志能力删除。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 确认平台、代理、企业的菜单和按钮权限编码,以及审计中心路由归属。
|
||||
2. 建立 OpenAPI 对齐的类型、API 模块和共享只读展示组件。
|
||||
3. 按平台审计、资金、风险、Integration、主体活动顺序接入页面。
|
||||
4. 在业务页面与通知导航中增加稳定引用入口。
|
||||
5. 完成角色、数据隔离、空引用、保留窗口、错误和跨视角跳转验收。
|
||||
6. 若上线异常,隐藏新增路由与入口;现有业务接口和旧操作日志不受影响。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 平台审计中心、风险中心、Integration、代理资源活动和企业资源活动的最终菜单及按钮权限编码分别是什么?
|
||||
- 审计中心是作为一级菜单,还是归入现有系统管理/运维菜单?
|
||||
- OpenAPI 未包含 `GET /api/admin/notifications/{id}/target` 的完整响应 schema;是否继续以活跃通知中心变更定义的 `available/target_type/target_id/target_key` 为最终契约?
|
||||
@@ -0,0 +1,38 @@
|
||||
# Change: 新增审计链路前端接入能力
|
||||
|
||||
## Why
|
||||
|
||||
八月迭代新增了审计事件、请求与业务链路、资金调查、风险调查、外部集成交互以及代理/企业资源活动共 16 个只读接口。当前前端尚无统一的审计调查页面、接口类型和业务入口,无法可靠消费后端返回的稳定调查引用,也容易错误地由名称、时间或页面数据自行拼接链路标识。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增平台审计事件列表、详情、操作者时间线、资源精确搜索和资源时间线能力。
|
||||
- 新增请求链路与业务关联链路时间线,并只使用接口返回或用户从 Access Log 粘贴的稳定 `request_id`、`correlation_id`。
|
||||
- 新增资金调查时间线、风险总览与明细、Integration 总览/列表/详情页面。
|
||||
- 新增代理和企业资源活动入口,并按主体支持范围使用稳定业务标识和后端安全投影。
|
||||
- 在卡、设备、店铺、企业、订单、退款和钱包相关列表/详情页增加角色匹配的「审计记录」入口。
|
||||
- 接入通知目标到 Integration 详情的受控跳转:仅接受可用的 `integration_log` 目标。
|
||||
- 统一使用后端返回的名称、状态、保留窗口语义和调查引用;禁止前端猜测或生成 `request_id`、`correlation_id`、`integration_id`。
|
||||
- 所有新增能力均为只读调查能力,不增加恢复、修改、删除、处置、封禁或导出操作。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `audit-chain-frontend-integration`
|
||||
- Affected code:
|
||||
- `src/api/modules/` 下新增审计接口模块
|
||||
- `src/types/api/` 下新增审计接口类型
|
||||
- `src/views/` 下审计中心、风险中心、Integration 和时间线页面
|
||||
- 卡、设备、店铺、企业、订单、退款、钱包相关列表/详情页
|
||||
- 路由、菜单、权限控制及通知目标导航
|
||||
- API contracts:
|
||||
- `GET /api/admin/audit/*`
|
||||
- `GET /api/admin/agent/resource-activities/{resource_type}/{identifier}`
|
||||
- `GET /api/admin/enterprise/resource-activities/{resource_type}/{identifier}`
|
||||
- `GET /api/admin/notifications/{id}/target`
|
||||
- Dependencies:
|
||||
- 与活跃变更 `update-admin-notification-center-api` 的受控通知目标协议保持一致
|
||||
- 与活跃变更 `update-admin-asset-device-signal-and-audit-logs` 的旧资产操作日志展示并存;本变更不替换旧日志接口
|
||||
- Source of truth:
|
||||
- `docs/产品迭代8月份/审计链路接口变更整理文档.md`
|
||||
- `docs/产品迭代8月份/默认模块.openapi.json`
|
||||
- Breaking changes: 无;现有业务接口路径保持不变
|
||||
@@ -0,0 +1,207 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Platform Audit Event Investigation
|
||||
|
||||
The admin frontend SHALL provide platform audit event list and detail views using `GET /api/admin/audit/events` and `GET /api/admin/audit/events/{event_id}`. It SHALL preserve the documented event, actor, scope, resource, result, risk, request and investigation-reference fields, use stable codes for filters, and prefer backend display names.
|
||||
|
||||
#### Scenario: Filter and inspect audit events
|
||||
|
||||
- **WHEN** an authorized platform user filters audit events by documented time, action, category, actor, source, result, risk, scope, resource or linkage parameters
|
||||
- **THEN** the frontend MUST send the documented parameter names and stable code values
|
||||
- **AND** it MUST render the paginated `items`, `total`, `page`, `page_size` and `retention` response
|
||||
|
||||
#### Scenario: Open an event detail
|
||||
|
||||
- **WHEN** the user opens an event returned by the list or another investigation reference
|
||||
- **THEN** the frontend MUST pass its `event_id` unchanged to the detail endpoint
|
||||
- **AND** it MUST display backend snapshots and names without replacing historical values with current account or resource names
|
||||
|
||||
### Requirement: Stable Investigation Reference Navigation
|
||||
|
||||
The frontend SHALL navigate between audit views only through stable identifiers returned by the APIs. `investigation_refs.actor_ref`, `resource_refs`, `request_id`, `correlation_id`, `integration_refs`, Integration `linkage`, and stable Integration `resource` references SHALL be the authoritative navigation sources.
|
||||
|
||||
#### Scenario: Navigate through a returned reference
|
||||
|
||||
- **WHEN** an audit or Integration response contains a non-empty supported investigation reference
|
||||
- **THEN** the frontend MUST pass the returned identifier and type unchanged to the corresponding actor, resource, request, correlation or Integration view
|
||||
|
||||
#### Scenario: A reference is unavailable or unreliable
|
||||
|
||||
- **WHEN** the required reference is empty, absent, unsupported, or its linkage `fidelity` indicates that a relationship is unavailable
|
||||
- **THEN** the frontend MUST hide or disable the related navigation action
|
||||
- **AND** it MUST NOT infer a relationship from names, timestamps, summaries, adjacent rows or resource text
|
||||
|
||||
#### Scenario: Link identifiers are not generated by the frontend
|
||||
|
||||
- **WHEN** the frontend needs a `correlation_id` or `integration_id`
|
||||
- **THEN** it MUST use a value returned by an API
|
||||
- **AND** it MUST NOT generate, concatenate or guess the identifier
|
||||
|
||||
### Requirement: Actor, Resource, and Link Timelines
|
||||
|
||||
The admin frontend SHALL provide actor-event, resource-event, request-link and correlation-link timelines through the documented endpoints. It SHALL support an explicitly pasted Access Log `request_id`, while all other navigation values SHALL come from returned stable references.
|
||||
|
||||
#### Scenario: Inspect actor behavior
|
||||
|
||||
- **WHEN** a user follows `actor_ref.kind/id` or opens an account by its stable ID
|
||||
- **THEN** the frontend MUST call `/api/admin/audit/actors/{kind}/{id}/events`
|
||||
- **AND** action and resource filters MUST use stable values returned by audit data
|
||||
|
||||
#### Scenario: Select an exact resource result
|
||||
|
||||
- **WHEN** a user searches with a supported `resource_type` and exact `keyword` and selects a result
|
||||
- **THEN** the frontend MUST pass `items[].resource_type/resource_id` unchanged to the resource timeline
|
||||
- **AND** it MUST identify `historical=true` as a historical-snapshot match
|
||||
|
||||
#### Scenario: Query a request copied from Access Log
|
||||
|
||||
- **WHEN** a platform user explicitly pastes a request ID from Access Log
|
||||
- **THEN** the frontend MAY query `/api/admin/audit/requests/{request_id}/timeline` with that exact value
|
||||
- **AND** it MUST NOT claim that the endpoint scans Access Log or archived object storage
|
||||
|
||||
### Requirement: Retention, Pagination, and Time Semantics
|
||||
|
||||
All audit list and timeline views SHALL use the documented pagination and `retention` contract. Time filters SHALL be RFC3339 timestamps with timezone information, and `created_to` SHALL be treated as an exclusive upper bound.
|
||||
|
||||
#### Scenario: Respect the online retention window without a global prompt
|
||||
|
||||
- **WHEN** a response contains `retention.online_from`, `archived_before` and `timezone`
|
||||
- **THEN** the frontend MUST preserve the retention semantics in its data contract without displaying a global online-window banner
|
||||
- **AND** it MUST NOT interpret an empty online result as proof that no historical event exists
|
||||
|
||||
#### Scenario: Page through a timeline
|
||||
|
||||
- **WHEN** the user changes page or page size
|
||||
- **THEN** the frontend MUST use `page` and `page_size`, respect the maximum page size of 100, and preserve the active filters
|
||||
|
||||
### Requirement: Finance Investigation Timeline
|
||||
|
||||
The admin frontend SHALL query `GET /api/admin/audit/finance/timeline` with any documented stable finance condition, including shop, wallet, order, payment, refund, recharge, approval, third-party trade, actor or correlation identifiers. Monetary values SHALL remain integer fen in application data, and authority SHALL follow `amount_authority`.
|
||||
|
||||
#### Scenario: Open finance history from a business record
|
||||
|
||||
- **WHEN** a user opens finance history from an order, refund, recharge, wallet or shop with a stable backend ID
|
||||
- **THEN** the frontend MUST send the matching documented query parameter
|
||||
- **AND** it MUST allow the server to complete related facts instead of assembling a local timeline
|
||||
|
||||
#### Scenario: Display an authoritative amount
|
||||
|
||||
- **WHEN** a finance node returns an amount and `amount_authority.authoritative=true`
|
||||
- **THEN** the frontend MUST treat the referenced table and field as authoritative
|
||||
- **AND** it MUST only convert integer fen for presentation and MUST NOT reconcile conflicting facts locally
|
||||
|
||||
### Requirement: Risk Investigation
|
||||
|
||||
The admin frontend SHALL provide risk overview and event-detail views using `/api/admin/audit/risks/overview` and `/api/admin/audit/risks/events`. Filters SHALL use codes returned in overview collections, and the selected time range SHALL not exceed 31 days.
|
||||
|
||||
#### Scenario: Drill down from a risk summary
|
||||
|
||||
- **WHEN** a user selects a risk, result, action, source or signal represented by the overview
|
||||
- **THEN** the frontend MUST use the returned stable code for the supported event-list filter
|
||||
- **AND** backend `name` values MUST be used only for display
|
||||
|
||||
#### Scenario: Select a range longer than 31 days
|
||||
|
||||
- **WHEN** the user attempts to query more than 31 days
|
||||
- **THEN** the frontend MUST prevent submission and explain the maximum range
|
||||
|
||||
### Requirement: External Integration Investigation
|
||||
|
||||
The admin frontend SHALL provide Integration overview, list and detail views through the documented endpoints. It SHALL preserve provider, direction, operation, raw result, derived result category, duration, state-change, trigger, resource, linkage, attempt, content-summary, fidelity and retention fields.
|
||||
|
||||
#### Scenario: Apply overview filters to the list
|
||||
|
||||
- **WHEN** a user selects an overview provider, direction or result
|
||||
- **THEN** the frontend MUST map `providers[].code` to `provider`, `directions[].code` to `direction`, `results[].code` to `result`, and `results[].category` to `result_category`
|
||||
- **AND** it MUST use `name` only as display text
|
||||
|
||||
#### Scenario: Display Integration trend categories
|
||||
|
||||
- **WHEN** the overview returns trend points
|
||||
- **THEN** the frontend MUST preserve the five categories `processing`, `succeeded`, `indeterminate`, `failed` and `not_sent`
|
||||
- **AND** it MUST use only the documented `hour` or `day` bucket
|
||||
|
||||
#### Scenario: Inspect an Integration detail
|
||||
|
||||
- **WHEN** a user opens an `integration_id` returned by a list, event reference or notification target
|
||||
- **THEN** the frontend MUST query the detail with that value unchanged
|
||||
- **AND** it MUST present the capability as read-only without recovery, modification, deletion or export actions
|
||||
|
||||
### Requirement: Role-Specific Resource Activity
|
||||
|
||||
The frontend SHALL use the agent and enterprise resource-activity endpoints according to the authenticated subject. Agent activity SHALL support `iot_card`, `device`, `asset_allocation_record`, `exchange_order`, `shop` and `enterprise`; enterprise activity SHALL support only authorized `iot_card` and `device` resources.
|
||||
|
||||
#### Scenario: Open an agent resource activity
|
||||
|
||||
- **WHEN** an agent opens activity for a supported resource
|
||||
- **THEN** the frontend MUST use ICCID for a card, VirtualNo for a device, or the documented stable business number for another supported resource
|
||||
- **AND** it MUST NOT send or infer the agent identity or shop scope as query data
|
||||
|
||||
#### Scenario: Open enterprise asset activity
|
||||
|
||||
- **WHEN** an enterprise user opens an authorized card or device activity
|
||||
- **THEN** the frontend MUST use ICCID or VirtualNo with the enterprise endpoint
|
||||
- **AND** it MUST render only the subject-safe projection without platform actor, risk, internal reason or before/after fields
|
||||
|
||||
#### Scenario: A stable subject identifier is missing
|
||||
|
||||
- **WHEN** a business response does not contain the required ICCID, VirtualNo or stable business number
|
||||
- **THEN** the frontend MUST hide the activity entry
|
||||
- **AND** it MUST NOT substitute a display name or internal identifier intended for another subject
|
||||
|
||||
### Requirement: Business Audit Entries
|
||||
|
||||
The frontend SHALL add role-appropriate audit entries to card, device, shop, enterprise, order, refund and wallet list/detail contexts without changing existing business API URLs. Platform entries SHALL use backend internal IDs; agent and enterprise entries SHALL use their documented stable business identifiers.
|
||||
|
||||
#### Scenario: Open platform asset or business history
|
||||
|
||||
- **WHEN** a platform user opens audit history from a card, device, shop, enterprise, order or refund record
|
||||
- **THEN** the frontend MUST use the corresponding `resource_type` and backend `response.data.id` with the resource timeline
|
||||
|
||||
#### Scenario: Open wallet or transaction history
|
||||
|
||||
- **WHEN** a user opens audit history for a wallet, order or refund with a stable ID
|
||||
- **THEN** the frontend MUST offer the applicable finance timeline query
|
||||
- **AND** the resource timeline MAY also be offered only when a stable resource reference is available
|
||||
|
||||
#### Scenario: Preserve existing operation logs
|
||||
|
||||
- **WHEN** new audit entries are introduced on asset pages
|
||||
- **THEN** existing asset operation-log features MUST remain available
|
||||
- **AND** the UI MUST distinguish the existing operation logs from the new cross-system audit investigation
|
||||
|
||||
### Requirement: Controlled Notification Integration Target
|
||||
|
||||
The frontend SHALL resolve a notification through `GET /api/admin/notifications/{id}/target` before opening an Integration detail. It SHALL open the detail only when the target is available, has `target_type=integration_log`, and contains a non-empty `target_key`.
|
||||
|
||||
#### Scenario: Open an Integration notification
|
||||
|
||||
- **WHEN** target resolution returns `available=true`, `target_type=integration_log`, and a non-empty `target_key`
|
||||
- **THEN** the frontend MUST pass `target_key` unchanged as the Integration `integration_id`
|
||||
- **AND** it MUST open the controlled internal Integration detail route
|
||||
|
||||
#### Scenario: Notification target cannot be used
|
||||
|
||||
- **WHEN** the target is unavailable, has another type, lacks `target_key`, or maps to no registered route
|
||||
- **THEN** the frontend MUST not navigate or execute an arbitrary URL
|
||||
- **AND** it MUST preserve the notification content and show a safe unavailable-target message
|
||||
|
||||
### Requirement: Audit Authorization and Read-Only Boundary
|
||||
|
||||
The frontend SHALL enforce the final platform, agent and enterprise route and action permissions, while preserving backend authentication, authorization and data-isolation enforcement. All capabilities in this change SHALL remain read-only.
|
||||
|
||||
#### Scenario: A subject lacks audit permission
|
||||
|
||||
- **WHEN** the current subject lacks the configured permission for an audit page or business entry
|
||||
- **THEN** the frontend MUST hide or disable that page or entry and MUST NOT call the endpoint as a fallback
|
||||
|
||||
#### Scenario: An audit request is rejected
|
||||
|
||||
- **WHEN** an endpoint returns `400`, `401`, `403` or `500`
|
||||
- **THEN** the frontend MUST use shared validation, authentication, authorization and server-error handling
|
||||
- **AND** it MUST preserve the current investigation state when retrying would be unsafe or misleading
|
||||
|
||||
#### Scenario: A user inspects an audit record
|
||||
|
||||
- **WHEN** any audit, risk, finance, Integration or subject-activity view is displayed
|
||||
- **THEN** the UI MUST NOT provide mutation, recovery, deletion, risk-disposition, blocking or export actions
|
||||
@@ -0,0 +1,44 @@
|
||||
## 1. Contract and Shared Infrastructure
|
||||
|
||||
- [x] 1.1 根据 `默认模块.openapi.json` 建立审计事件、调查引用、资源、保留窗口、链路节点、资金节点、风险和 Integration 的 TypeScript 类型。
|
||||
- [x] 1.2 新增平台审计、主体资源活动、资金、风险、Integration 和链路时间线 API 方法,保持文档参数名、枚举和 nullable 语义。
|
||||
- [x] 1.3 建立共享的分页、RFC3339 时间范围、保留窗口、枚举名称和 API 错误展示能力。
|
||||
- [x] 1.4 建立只读事件详情、资源摘要、调查引用和时间线节点组件,不提供写操作或导出能力。
|
||||
|
||||
## 2. Platform Audit Center
|
||||
|
||||
- [x] 2.1 实现审计事件列表及文档定义的时间、动作、类别、操作者、来源、结果、风险、范围、资源和链路筛选。
|
||||
- [x] 2.2 实现事件详情,展示事件、操作者、资源快照、结果、风险和元数据,并按非空 `investigation_refs` 提供跳转。
|
||||
- [x] 2.3 实现操作者行为时间线,使用 `actor_ref.kind/id` 和稳定 code 筛选。
|
||||
- [x] 2.4 实现资源精确搜索及资源时间线,原样使用选中项的 `resource_type/resource_id` 并提示历史快照命中。
|
||||
- [x] 2.5 实现请求和业务关联时间线,支持从返回引用进入,以及明确粘贴 Access Log `request_id` 的查询入口。
|
||||
|
||||
## 3. Specialized Investigations
|
||||
|
||||
- [x] 3.1 实现资金调查时间线和全部文档筛选条件,以分为数据单位并展示金额权威来源。
|
||||
- [x] 3.2 实现风险总览和风险事件明细,按总览返回的稳定 code 回填筛选,并限制最长 31 天时间范围。
|
||||
- [x] 3.3 实现 Integration 总览、列表和详情,覆盖 provider、direction、result、result_category、趋势、尝试、内容摘要、保真度和关联字段。
|
||||
- [x] 3.4 实现各调查视角之间基于 `investigation_refs`、`linkage` 和稳定资源引用的受控跳转。
|
||||
|
||||
## 4. Subject Activity and Business Entries
|
||||
|
||||
- [x] 4.1 实现代理资源活动页面,支持卡、设备、资产分配记录、换货单、店铺和企业的稳定业务标识。
|
||||
- [x] 4.2 实现企业资源活动页面,仅支持当前授权卡和设备并只渲染主体安全投影。
|
||||
- [x] 4.3 在卡、设备、店铺、企业、订单、退款和钱包列表/详情增加角色匹配的「审计记录」入口。
|
||||
- [x] 4.4 缺少内部 ID、ICCID、VirtualNo 或业务编号时隐藏入口,不使用页面文本或其他字段推断。
|
||||
- [x] 4.5 保留现有资产操作日志入口,并通过命名与说明区分旧操作日志和新审计调查能力。
|
||||
|
||||
## 5. Notification, Routes, and Permissions
|
||||
|
||||
- [x] 5.1 增加审计中心、风险中心、Integration 和共享时间线的路由与菜单配置。
|
||||
- [x] 5.2 接入最终确认的平台、代理、企业菜单/按钮权限编码,隐藏越权页面和业务入口。
|
||||
- [x] 5.3 在通知目标导航中仅对可用 `integration_log` 目标开放 Integration 详情,并原样使用 `target_key`。
|
||||
- [x] 5.4 对未知、不可用或缺失目标保留安全提示,不执行任意 URL 或推测跳转。
|
||||
|
||||
## 6. Verification
|
||||
|
||||
- [ ] 6.1 为 API 参数序列化、枚举、nullable 字段、分页和 RFC3339 时间范围增加单元测试。
|
||||
- [ ] 6.2 为稳定引用跳转、空引用隐藏、`fidelity=false`、通知 Integration 目标和禁止生成链路 ID 增加测试。
|
||||
- [ ] 6.3 验证平台、代理、企业角色可见性、服务端数据隔离、企业安全投影以及 `401/403/400/500` 处理。
|
||||
- [ ] 6.4 验证保留窗口、空数据、最长 31 天风险查询、资金金额单位和 Integration 五类趋势状态。
|
||||
- [ ] 6.5 完成 16 个接口的联调回归,并确认现有业务 URL、通知中心和旧资产操作日志未被破坏。
|
||||
65
openspec/changes/add-bulk-purchase-upload-task/design.md
Normal file
65
openspec/changes/add-bulk-purchase-upload-task/design.md
Normal file
@@ -0,0 +1,65 @@
|
||||
## Context
|
||||
|
||||
批量订购包含文件上传、异步任务处理、任务恢复和逐行失败查看四个阶段。任务创建需要绑定一个代理商和一种支付方式,线下支付还需要上传整批凭证;任务处理过程中可能出现部分成功和钱包余额不足,前端必须展示后端结果而不能把整批操作当成原子事务。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: 提供批量订单 Excel 上传、支付方式选择、任务进度展示、任务恢复和逐行失败明细。
|
||||
- Goals: 使用 `request_id` 防止重复提交,并按任务 ID 查询服务端真实状态。
|
||||
- Goals: 复用公共异步任务的五态语义和终态规则。
|
||||
- Non-Goals: 不在前端解析 Excel 业务行、不执行订单创建、不计算订单金额、不回滚已成功订单。
|
||||
- Non-Goals: 不改造现有单笔订单创建和单笔支付凭证上传流程。
|
||||
- Non-Goals: 不新增后端模板下载接口。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 批量订购页面使用独立任务视图,订单列表只提供入口,不把逐行结果嵌入订单列表表格。
|
||||
- Rationale: 批量任务有独立生命周期和大量逐行结果,独立页面更适合恢复、轮询和分页查看。
|
||||
|
||||
- Decision: `payment_method` 在创建表单中为单选值,并在请求中对整批固定;线下支付时才允许提交 `voucher_file`。
|
||||
- Rationale: 产品明确一个批次不能混合支付方式,前端应避免生成含混请求。
|
||||
|
||||
- Decision: 使用前端静态 Excel 模板资源。
|
||||
- Rationale: 产品明确模板下载不依赖后端动态生成,减少接口依赖。
|
||||
|
||||
- Decision: 使用 `request_id` 作为客户端幂等键,并在创建前生成一次、提交重试时复用同一值。
|
||||
- Rationale: 防止网络重试或重复点击创建多个相同批次。
|
||||
|
||||
- Decision: 部分成功、钱包余额不足和逐行业务失败均由后端任务结果表达;前端只展示计数和失败明细,不自行推断或回滚。
|
||||
- Rationale: 钱包扣款和订单事务边界属于后端职责,前端不能可靠重建。
|
||||
|
||||
## Data Model
|
||||
|
||||
- Create request: `shop_id`、`payment_method`、`file`、可选 `voucher_file`、`request_id`。
|
||||
- Task identity: `task_id`、`task_no`。
|
||||
- Task status: `1=待处理`、`2=处理中`、`3=已完成`、`4=已失败`、`5=已取消`;部分成功仍属于已完成终态。
|
||||
- Task summary: status, total count, success count, failed count, amount summary, timestamps and safe error summary when returned.
|
||||
- Item result: row number, asset identifier, package code, row status and safe error reason.
|
||||
- Item query: task ID, page, size and optional row status filter.
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- Risk: 后端金额字段名称或单位未在产品文档中明确。
|
||||
- Mitigation: API 类型和页面以接口实际返回字段为准,统一标注金额单位;实施前补齐字段契约,前端不自行计算汇总。
|
||||
|
||||
- Risk: 文件或凭证上传成功但任务创建请求失败,可能留下孤立对象。
|
||||
- Mitigation: 创建失败时保留用户选择和错误提示;对象清理策略由后端存储生命周期或接口约定处理。
|
||||
|
||||
- Risk: 任务详情恢复时任务已过期、删除或用户失去权限。
|
||||
- Mitigation: 按页面权限和接口错误处理展示对应状态,不重复创建原任务。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 确认批量订购任务摘要、金额和逐行结果字段契约。
|
||||
2. 新增 API、类型、权限和静态模板资源。
|
||||
3. 实现批量订购入口、文件上传、线下凭证上传和幂等提交。
|
||||
4. 实现任务详情、公共状态展示、轮询和 `task_id` 恢复。
|
||||
5. 实现逐行结果分页、状态筛选和失败明细展示。
|
||||
6. 验证钱包余额不足、部分成功、重复提交、刷新恢复和权限组合。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 批量订购任务摘要中的金额字段名称、金额单位和金额分类需要以后端接口文档确认。
|
||||
- 失败明细中的资产字段是统一 `asset_identifier`,还是按资产类型返回 `iccid` / `virtual_no`,需要以后端确认。
|
||||
- `voucher_file` 是单文件、文件数组还是已上传对象存储 key,需要与 multipart 接口契约确认。
|
||||
- 批量订购入口的最终路由、菜单名称和权限编码需要产品/后端确认。
|
||||
38
openspec/changes/add-bulk-purchase-upload-task/proposal.md
Normal file
38
openspec/changes/add-bulk-purchase-upload-task/proposal.md
Normal file
@@ -0,0 +1,38 @@
|
||||
# Change: 新增批量订购任务与逐行结果
|
||||
|
||||
## Why
|
||||
|
||||
运营需要为同一个代理商批量导入套餐订单,并统一指定整批支付方式。当前订单页面只支持单笔创建,无法上传批量订单文件、跟踪处理进度或定位逐行失败原因,批量操作也无法安全处理线下支付凭证和钱包余额不足场景。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增批量订购套餐入口,支持选择代理商、整批支付方式和上传 Excel 文件。
|
||||
- 支持线下支付时上传整批支付凭证;一个批次禁止混合支付方式。
|
||||
- 模板下载使用前端静态文件,不依赖后端模板接口。
|
||||
- 新增批量订购任务 API,提交 multipart 字段 `shop_id`、`payment_method`、`file`、`voucher_file` 和 `request_id`。
|
||||
- 创建成功后展示任务号、任务状态、总数、成功数、失败数和金额汇总。
|
||||
- 支持按 `task_id` 恢复任务详情,并轮询进行中的任务。
|
||||
- 新增逐行结果查询,支持分页和状态筛选。
|
||||
- 失败明细展示行号、资产、套餐编码和错误原因。
|
||||
- 部分成功作为任务终态;钱包余额不足只影响对应行或后续行,不回滚已经成功的订单。
|
||||
- 接入现有 RBAC 权限体系,批量订购创建、任务详情、逐行结果和模板下载权限独立控制。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `bulk-purchase-task`
|
||||
- `order-management`
|
||||
- `async-task-interaction`(复用现有公共异步任务状态与恢复规则)
|
||||
- Affected code:
|
||||
- `src/api/modules/bulkPurchase.ts`
|
||||
- `src/types/api/bulkPurchase.ts`
|
||||
- `src/views/order-management/bulk-purchase/index.vue`
|
||||
- `src/components/business/BulkPurchaseCreateDialog.vue`(如采用独立弹窗)
|
||||
- `src/views/order-management/order-list/index.vue`(批量入口)
|
||||
- 静态 Excel 模板资源、路由、菜单、权限和国际化配置
|
||||
- Dependencies:
|
||||
- 后端提供三个批量订购接口及 multipart 鉴权契约。
|
||||
- 对象存储上传能力支持批量订单文件和线下支付凭证上传。
|
||||
- 需要确认批量订购任务的完整响应字段和并发轮询策略与公共异步任务规范一致。
|
||||
- Breaking changes:
|
||||
- 无。新增 API、页面、权限和任务能力,不修改单笔订单创建接口。
|
||||
@@ -0,0 +1,133 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Bulk Purchase Creation Form
|
||||
|
||||
The admin frontend SHALL provide a bulk purchase form that binds one uploaded batch to one shop and one payment method.
|
||||
|
||||
#### Scenario: Select batch purchase inputs
|
||||
|
||||
- **GIVEN** 用户打开批量订购入口
|
||||
- **WHEN** 用户填写批量订购表单
|
||||
- **THEN** 页面 MUST require a target shop, one payment method, and an Excel file
|
||||
- **AND** 页面 MUST NOT provide a way to mix payment methods within the same batch
|
||||
|
||||
#### Scenario: Show voucher upload for offline payment
|
||||
|
||||
- **GIVEN** 用户选择线下支付
|
||||
- **WHEN** 页面渲染批量订购表单
|
||||
- **THEN** 页面 MUST show the batch voucher upload control
|
||||
- **AND** 页面 MUST require a completed voucher upload before task creation
|
||||
|
||||
#### Scenario: Hide voucher upload for wallet payment
|
||||
|
||||
- **GIVEN** 用户选择代理预存款支付
|
||||
- **WHEN** 页面渲染或提交批量订购表单
|
||||
- **THEN** 页面 MUST NOT submit a voucher file
|
||||
- **AND** 页面 MUST clear or ignore a voucher selected before switching to wallet payment
|
||||
|
||||
### Requirement: Bulk Purchase File Upload And Creation
|
||||
|
||||
The admin frontend SHALL create a bulk purchase task through `POST /api/admin/bulk-purchases` using multipart form data.
|
||||
|
||||
#### Scenario: Create bulk purchase task
|
||||
|
||||
- **GIVEN** 用户已选择代理商、支付方式并完成文件上传
|
||||
- **WHEN** 用户确认创建批量订购任务
|
||||
- **THEN** 系统 MUST submit multipart fields `shop_id`, `payment_method`, `file`, and `request_id`
|
||||
- **AND** 系统 MUST submit `voucher_file` when the payment method is offline
|
||||
- **AND** 系统 MUST save the returned `task_id` and `task_no`
|
||||
|
||||
#### Scenario: Prevent creation during upload
|
||||
|
||||
- **GIVEN** Excel 文件或线下支付凭证仍在上传
|
||||
- **WHEN** 用户点击创建任务
|
||||
- **THEN** 页面 MUST prevent task creation
|
||||
- **AND** 页面 MUST show the upload-in-progress state until all required uploads finish
|
||||
|
||||
#### Scenario: Download static template
|
||||
|
||||
- **GIVEN** 用户打开批量订购表单
|
||||
- **WHEN** 用户点击模板下载
|
||||
- **THEN** 页面 MUST download the packaged frontend static Excel template
|
||||
- **AND** 页面 MUST NOT require a template-generation API request
|
||||
|
||||
### Requirement: Bulk Purchase Task Summary And Status
|
||||
|
||||
The admin frontend SHALL display the server-provided bulk purchase task summary and use the shared five-state async task semantics.
|
||||
|
||||
#### Scenario: Display task summary
|
||||
|
||||
- **GIVEN** 批量订购任务创建成功或详情接口返回任务
|
||||
- **WHEN** 页面展示任务详情
|
||||
- **THEN** 页面 MUST display task ID or task number, status, total count, success count, failed count, and returned amount summaries
|
||||
- **AND** 页面 MUST use server-provided values without recalculating amounts or counts from the uploaded file
|
||||
|
||||
#### Scenario: Treat partial success as terminal completion
|
||||
|
||||
- **GIVEN** 任务已处理完成且同时存在成功行和失败行
|
||||
- **WHEN** 页面展示任务状态
|
||||
- **THEN** 页面 MUST display the task as a completed terminal task
|
||||
- **AND** 页面 MUST display success and failed counts separately
|
||||
- **AND** 页面 MUST NOT introduce a separate partial-success status
|
||||
|
||||
#### Scenario: Handle wallet insufficiency without rollback
|
||||
|
||||
- **GIVEN** 代理钱包余额不足导致部分或后续行无法创建订单
|
||||
- **WHEN** 页面展示任务结果
|
||||
- **THEN** 页面 MUST show the affected rows as failed with their returned reasons
|
||||
- **AND** 页面 MUST preserve and display rows that were already successful
|
||||
- **AND** 页面 MUST NOT attempt a frontend rollback
|
||||
|
||||
### Requirement: Bulk Purchase Task Recovery And Polling
|
||||
|
||||
The admin frontend SHALL recover a bulk purchase task by `task_id` and poll its summary while it is active.
|
||||
|
||||
#### Scenario: Query task summary
|
||||
|
||||
- **GIVEN** 用户需要加载批量订购任务
|
||||
- **WHEN** 页面查询任务摘要
|
||||
- **THEN** 系统 MUST call `GET /api/admin/bulk-purchases/{task_id}`
|
||||
- **AND** 页面 MUST update the task summary from the response
|
||||
|
||||
#### Scenario: Recover task after refresh
|
||||
|
||||
- **GIVEN** 页面存在已保存的 active `task_id`
|
||||
- **WHEN** 用户刷新页面或重新进入批量订购任务页
|
||||
- **THEN** 页面 MUST query the existing task by `task_id`
|
||||
- **AND** 页面 MUST NOT create another bulk purchase task
|
||||
|
||||
#### Scenario: Stop polling at terminal state
|
||||
|
||||
- **GIVEN** 批量订购任务状态为已完成、已失败或已取消
|
||||
- **WHEN** 页面收到任务摘要
|
||||
- **THEN** 页面 MUST stop automatic polling
|
||||
- **AND** 页面 MUST retain the terminal summary and failure counts for viewing
|
||||
|
||||
### Requirement: Bulk Purchase Item Results
|
||||
|
||||
The admin frontend SHALL provide paginated and status-filterable row results for a bulk purchase task.
|
||||
|
||||
#### Scenario: Query item results
|
||||
|
||||
- **GIVEN** 用户打开批量订购任务结果
|
||||
- **WHEN** 页面加载逐行结果
|
||||
- **THEN** 系统 MUST call `GET /api/admin/bulk-purchases/{task_id}/items`
|
||||
- **AND** 系统 MUST support `page`, `size`, and optional `status` query parameters
|
||||
|
||||
#### Scenario: Display failed item details
|
||||
|
||||
- **GIVEN** 逐行结果接口返回失败行
|
||||
- **WHEN** 页面渲染结果表格
|
||||
- **THEN** 页面 MUST display row number, asset identifier, package code, and safe error reason
|
||||
- **AND** 页面 MUST NOT expose raw backend stack traces or technical error details
|
||||
|
||||
### Requirement: Bulk Purchase Permissions
|
||||
|
||||
The admin frontend SHALL gate bulk purchase creation, task viewing, item-result viewing, and template download with explicit permissions.
|
||||
|
||||
#### Scenario: Hide unauthorized bulk purchase operations
|
||||
|
||||
- **GIVEN** 当前用户缺少某项批量订购权限
|
||||
- **WHEN** 页面渲染对应入口或操作
|
||||
- **THEN** 页面 MUST NOT display or enable that operation
|
||||
- **AND** direct API failure MUST NOT be treated as permission to continue
|
||||
46
openspec/changes/add-bulk-purchase-upload-task/tasks.md
Normal file
46
openspec/changes/add-bulk-purchase-upload-task/tasks.md
Normal file
@@ -0,0 +1,46 @@
|
||||
## 1. Contract And Types
|
||||
|
||||
- [ ] 1.1 确认 `POST /api/admin/bulk-purchases` 的 multipart 字段类型、文件字段格式和响应结构。
|
||||
- [ ] 1.2 确认 `GET /api/admin/bulk-purchases/{task_id}` 的任务摘要字段、状态值、金额字段和错误字段。
|
||||
- [ ] 1.3 确认 `GET /api/admin/bulk-purchases/{task_id}/items` 的逐行字段、分页结构和状态筛选参数。
|
||||
- [x] 1.4 新增批量订购 API service、请求类型、任务摘要类型和逐行结果类型。
|
||||
- [x] 1.5 明确 `request_id` 的生成、保存和重复提交响应处理规则。
|
||||
|
||||
## 2. Upload And Create
|
||||
|
||||
- [x] 2.1 新增批量订购入口和表单,支持选择代理商、支付方式和 Excel 文件。
|
||||
- [x] 2.2 提供前端静态 Excel 模板下载,并限制上传文件类型和必要的文件状态。
|
||||
- [x] 2.3 线下支付时显示整批支付凭证上传,预存款支付时隐藏或清理凭证字段。
|
||||
- [x] 2.4 复用订单列表已有 `VoucherUpload` 组件展示凭证上传进度,上传未完成时禁止创建任务。
|
||||
- [x] 2.5 创建请求携带 `shop_id`、`payment_method`、`file`、必要的 `voucher_file` 和 `request_id`。
|
||||
- [x] 2.6 防止重复点击和重复提交,创建成功后保存 `task_id` 并进入任务详情。
|
||||
|
||||
## 3. Task Progress And Recovery
|
||||
|
||||
- [x] 3.1 展示任务号、状态、总数、成功数、失败数、金额汇总和安全错误摘要。
|
||||
- [x] 3.2 按公共异步任务规则轮询待处理和处理中的任务,并在终态停止。
|
||||
- [x] 3.3 页面刷新或通过任务 ID 重新进入时恢复任务详情,不重复创建批次。
|
||||
- [x] 3.4 将部分成功展示为已完成终态,并同时展示成功数和失败数。
|
||||
- [x] 3.5 展示钱包余额不足导致的逐行或后续行失败,不回滚已成功订单。
|
||||
|
||||
## 4. Item Results
|
||||
|
||||
- [x] 4.1 新增逐行结果表格,展示行号、资产、套餐编码、状态和错误原因。
|
||||
- [x] 4.2 支持按逐行状态筛选和分页查询。
|
||||
- [x] 4.3 失败原因优先展示后端安全错误文案,不直接展示底层技术错误。
|
||||
- [x] 4.4 任务详情和逐行结果保持当前任务 ID、筛选条件和分页状态。
|
||||
|
||||
## 5. Permissions And Verification
|
||||
|
||||
- [x] 5.1 为批量订购创建、任务详情、逐行结果和模板下载配置独立权限。
|
||||
- [ ] 5.2 验证一个批次只能提交一种支付方式,线下支付缺少凭证时不能提交。
|
||||
- [ ] 5.3 验证重复提交复用 `request_id`,不会创建重复任务。
|
||||
- [ ] 5.4 验证空文件、上传失败、任务失败、部分成功和钱包余额不足场景。
|
||||
- [ ] 5.5 验证页面刷新恢复、任务终态停止轮询和逐行失败筛选。
|
||||
- [x] 5.6 运行 `openspec validate add-bulk-purchase-upload-task --strict`、类型检查、lint 和构建。
|
||||
|
||||
## Implementation Notes
|
||||
|
||||
- 后端接口文档未随仓库提供,1.1、1.2、1.3 仍需联调确认精确金额字段、逐行字段和 multipart 文件格式;当前类型使用可选兼容字段。
|
||||
- 5.2 至 5.5 需要接入真实后端后进行手工回归,当前已完成前端校验、权限、幂等键、恢复、轮询和筛选逻辑。
|
||||
- 支付凭证复用 `src/components/business/VoucherUpload.vue`,提交 `voucher_file` 时使用该组件上传后返回的文件 key。
|
||||
@@ -0,0 +1,41 @@
|
||||
## Context
|
||||
|
||||
三个后台业务列表都需要展示相同的审批摘要,但各自保留既有退款、充值或换货操作。审批来源和业务处理状态均由后端列表接口返回,前端不请求单条审批详情来填充表格。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals:
|
||||
- 统一展示提交人、审批状态、当前审批人摘要和业务处理状态。
|
||||
- 正确区分无审批、历史本地审批和企微审批。
|
||||
- 在不增加逐行请求的前提下支持长摘要完整查看。
|
||||
- Non-Goals:
|
||||
- 不创建、修改或撤回审批流程。
|
||||
- 不增加历史本地审批操作按钮。
|
||||
- 不以 `approval_status` 推断 `processing_status`,或反向推断。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 三个列表项模型复用相同名称和语义的审批摘要字段,字段由各自的列表接口直接返回。
|
||||
- Decision: `approval_source=none` 时审批状态与当前审批人摘要均显示 `-`;`legacy` 时审批状态固定显示“历史审批”,当前审批人摘要显示 `-`;`wecom` 时直接展示 `approval_status_name` 和 `current_approver_summary`。
|
||||
- Decision: 审批人摘要仅负责展示,使用表格溢出省略与 tooltip 呈现完整文本。
|
||||
- Decision: 业务处理状态单独读取 `processing_status_name`,不与审批状态混合或映射。
|
||||
- Decision: 列表分页和刷新仅调用现有列表 API,禁止为每条记录请求审批详情。
|
||||
- Alternatives considered: 从单条详情或企微审批 API 批量补齐摘要。未采用,因为会引入 N+1 请求并与列表响应已提供的摘要字段重复。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 后端遗漏摘要字段时信息不可用 -> 统一显示稳定占位,不影响原有列表和业务操作。
|
||||
- 审批状态名称可能为空 -> 企微来源显示稳定占位,不自行翻译状态码。
|
||||
- 审批人摘要长度不受控 -> 表格列使用溢出省略和 hover 完整文本。
|
||||
|
||||
## Migration Plan
|
||||
|
||||
1. 扩展三个列表项类型以保留审批摘要字段。
|
||||
2. 在三个列表中添加四个展示列并遵循审批来源规则。
|
||||
3. 验证 `none`、`legacy`、`wecom` 和处理状态为空的响应。
|
||||
4. 验证刷新、分页未出现逐行审批详情请求。
|
||||
5. 如需回滚,移除列表列与附加类型字段;不涉及数据迁移。
|
||||
|
||||
## Open Questions
|
||||
|
||||
- 无。
|
||||
@@ -0,0 +1,36 @@
|
||||
# Change: 新增业务列表提交人与审批摘要
|
||||
|
||||
## Why
|
||||
|
||||
退款、代理充值和换货列表当前无法直接显示提交人、企微审批进度及业务处理进度。运营人员需要进入详情或依赖额外沟通才能判断记录由谁发起、审批进行到哪一步以及后续业务是否完成。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在退款列表、代理充值列表和换货列表增加“提交人”“审批状态”“当前审批人摘要”“业务处理状态”四列。
|
||||
- 三个列表接口项统一支持 `submitter_name`、`approval_source`、`approval_status`、`approval_status_name`、`current_approver_summary`、`processing_status`、`processing_status_name`。
|
||||
- `approval_source=none` 时审批状态和当前审批人摘要显示 `-`。
|
||||
- `approval_source=legacy` 时审批状态显示“历史审批”,作为只读历史信息,不新增审批操作按钮。
|
||||
- `approval_source=wecom` 时显示后端返回的企微审批状态及当前审批人摘要;超长审批人摘要使用省略显示并在悬浮时展示完整文本。
|
||||
- 业务处理状态直接展示后端 `processing_status_name`,与审批状态分列展示。
|
||||
- 列表仅使用列表响应中的审批摘要字段,翻页和刷新时不得为每行额外请求审批详情。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs:
|
||||
- `order-management`
|
||||
- `agent-recharge`
|
||||
- `exchange-management`
|
||||
- Affected code:
|
||||
- `src/types/api/refund.ts`
|
||||
- `src/types/api/agentRecharge.ts`
|
||||
- `src/api/modules/exchange.ts`
|
||||
- `src/views/finance/refund/index.vue`
|
||||
- `src/views/finance/agent-recharge/index.vue`
|
||||
- `src/views/asset-management/exchange-management/index.vue`
|
||||
- API contracts:
|
||||
- `GET /api/admin/refunds`
|
||||
- `GET /api/admin/agent-recharges`
|
||||
- `GET /api/admin/exchanges`
|
||||
- Out of scope:
|
||||
- 审批发起、撤回、审批操作或企微审批详情页。
|
||||
- 前端根据业务状态或审批步骤推导审批结果和业务处理状态。
|
||||
@@ -0,0 +1,51 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Agent Recharge List Approval Summary Contract
|
||||
|
||||
The `GET /api/admin/agent-recharges` list-item contract SHALL support `submitter_name`, `approval_source`, `approval_status`, `approval_status_name`, `current_approver_summary`, `processing_status`, and `processing_status_name`.
|
||||
|
||||
#### Scenario: Receive agent recharge approval summary fields
|
||||
|
||||
- **GIVEN** 后台代理充值列表接口返回充值记录
|
||||
- **WHEN** 前端解析列表响应
|
||||
- **THEN** 代理充值列表项类型 MUST preserve all approval and processing summary fields
|
||||
- **AND** 页面 MUST NOT request an individual approval-detail API to populate the row
|
||||
|
||||
### Requirement: Agent Recharge List Approval And Processing Display
|
||||
|
||||
The agent recharge list SHALL display `提交人`, `审批状态`, `当前审批人摘要`, and `业务处理状态` as distinct columns based on backend summary fields.
|
||||
|
||||
#### Scenario: Display recharge with no approval source
|
||||
|
||||
- **GIVEN** 代理充值记录的 `approval_source=none`
|
||||
- **WHEN** 页面渲染代理充值列表行
|
||||
- **THEN** `审批状态` MUST display `-`
|
||||
- **AND** `当前审批人摘要` MUST display `-`
|
||||
|
||||
#### Scenario: Display legacy recharge approval read-only
|
||||
|
||||
- **GIVEN** 代理充值记录的 `approval_source=legacy`
|
||||
- **WHEN** 页面渲染代理充值列表行
|
||||
- **THEN** `审批状态` MUST display `历史审批`
|
||||
- **AND** 页面 MUST NOT add an approval operation button for that historical approval
|
||||
|
||||
#### Scenario: Display WeCom recharge approval summary
|
||||
|
||||
- **GIVEN** 代理充值记录的 `approval_source=wecom`
|
||||
- **WHEN** 页面渲染代理充值列表行
|
||||
- **THEN** `审批状态` MUST display backend `approval_status_name`
|
||||
- **AND** `当前审批人摘要` MUST display backend `current_approver_summary`
|
||||
- **AND** `业务处理状态` MUST independently display backend `processing_status_name`
|
||||
|
||||
#### Scenario: View long recharge approver summary
|
||||
|
||||
- **GIVEN** 代理充值记录的 `current_approver_summary` exceeds its table cell width
|
||||
- **WHEN** 页面渲染当前审批人摘要列
|
||||
- **THEN** 摘要 MUST be visually truncated in the cell
|
||||
- **AND** 用户 MUST be able to view the complete backend text on hover
|
||||
|
||||
#### Scenario: Paginate recharges without per-row approval requests
|
||||
|
||||
- **WHEN** 用户切换代理充值列表页码或刷新列表
|
||||
- **THEN** 页面 MUST use the agent recharge list API response for approval summaries
|
||||
- **AND** 页面 MUST NOT issue approval-detail requests per recharge row
|
||||
@@ -0,0 +1,51 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Exchange List Approval Summary Contract
|
||||
|
||||
The `GET /api/admin/exchanges` list-item contract SHALL support `submitter_name`, `approval_source`, `approval_status`, `approval_status_name`, `current_approver_summary`, `processing_status`, and `processing_status_name`.
|
||||
|
||||
#### Scenario: Receive exchange approval summary fields
|
||||
|
||||
- **GIVEN** 后台换货列表接口返回换货记录
|
||||
- **WHEN** 前端解析列表响应
|
||||
- **THEN** 换货列表项类型 MUST preserve all approval and processing summary fields
|
||||
- **AND** 页面 MUST NOT request an individual approval-detail API to populate the row
|
||||
|
||||
### Requirement: Exchange List Approval And Processing Display
|
||||
|
||||
The exchange management list SHALL display `提交人`, `审批状态`, `当前审批人摘要`, and `业务处理状态` as distinct columns based on backend summary fields.
|
||||
|
||||
#### Scenario: Display exchange with no approval source
|
||||
|
||||
- **GIVEN** 换货记录的 `approval_source=none`
|
||||
- **WHEN** 页面渲染换货列表行
|
||||
- **THEN** `审批状态` MUST display `-`
|
||||
- **AND** `当前审批人摘要` MUST display `-`
|
||||
|
||||
#### Scenario: Display legacy exchange approval read-only
|
||||
|
||||
- **GIVEN** 换货记录的 `approval_source=legacy`
|
||||
- **WHEN** 页面渲染换货列表行
|
||||
- **THEN** `审批状态` MUST display `历史审批`
|
||||
- **AND** 页面 MUST NOT add an approval operation button for that historical approval
|
||||
|
||||
#### Scenario: Display WeCom exchange approval summary
|
||||
|
||||
- **GIVEN** 换货记录的 `approval_source=wecom`
|
||||
- **WHEN** 页面渲染换货列表行
|
||||
- **THEN** `审批状态` MUST display backend `approval_status_name`
|
||||
- **AND** `当前审批人摘要` MUST display backend `current_approver_summary`
|
||||
- **AND** `业务处理状态` MUST independently display backend `processing_status_name`
|
||||
|
||||
#### Scenario: View long exchange approver summary
|
||||
|
||||
- **GIVEN** 换货记录的 `current_approver_summary` exceeds its table cell width
|
||||
- **WHEN** 页面渲染当前审批人摘要列
|
||||
- **THEN** 摘要 MUST be visually truncated in the cell
|
||||
- **AND** 用户 MUST be able to view the complete backend text on hover
|
||||
|
||||
#### Scenario: Paginate exchanges without per-row approval requests
|
||||
|
||||
- **WHEN** 用户切换换货列表页码或刷新列表
|
||||
- **THEN** 页面 MUST use the exchange list API response for approval summaries
|
||||
- **AND** 页面 MUST NOT issue approval-detail requests per exchange row
|
||||
@@ -0,0 +1,51 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Refund List Approval Summary Contract
|
||||
|
||||
The `GET /api/admin/refunds` list-item contract SHALL support `submitter_name`, `approval_source`, `approval_status`, `approval_status_name`, `current_approver_summary`, `processing_status`, and `processing_status_name`.
|
||||
|
||||
#### Scenario: Receive refund approval summary fields
|
||||
|
||||
- **GIVEN** 后台退款列表接口返回退款记录
|
||||
- **WHEN** 前端解析列表响应
|
||||
- **THEN** 退款列表项类型 MUST preserve all approval and processing summary fields
|
||||
- **AND** 页面 MUST NOT request an individual approval-detail API to populate the row
|
||||
|
||||
### Requirement: Refund List Approval And Processing Display
|
||||
|
||||
The refund management list SHALL display `提交人`, `审批状态`, `当前审批人摘要`, and `业务处理状态` as distinct columns based on backend summary fields.
|
||||
|
||||
#### Scenario: Display refund with no approval source
|
||||
|
||||
- **GIVEN** 退款记录的 `approval_source=none`
|
||||
- **WHEN** 页面渲染退款列表行
|
||||
- **THEN** `审批状态` MUST display `-`
|
||||
- **AND** `当前审批人摘要` MUST display `-`
|
||||
|
||||
#### Scenario: Display legacy refund approval read-only
|
||||
|
||||
- **GIVEN** 退款记录的 `approval_source=legacy`
|
||||
- **WHEN** 页面渲染退款列表行
|
||||
- **THEN** `审批状态` MUST display `历史审批`
|
||||
- **AND** 页面 MUST NOT add an approval operation button for that historical approval
|
||||
|
||||
#### Scenario: Display WeCom refund approval summary
|
||||
|
||||
- **GIVEN** 退款记录的 `approval_source=wecom`
|
||||
- **WHEN** 页面渲染退款列表行
|
||||
- **THEN** `审批状态` MUST display backend `approval_status_name`
|
||||
- **AND** `当前审批人摘要` MUST display backend `current_approver_summary`
|
||||
- **AND** `业务处理状态` MUST independently display backend `processing_status_name`
|
||||
|
||||
#### Scenario: View long refund approver summary
|
||||
|
||||
- **GIVEN** 退款记录的 `current_approver_summary` exceeds its table cell width
|
||||
- **WHEN** 页面渲染当前审批人摘要列
|
||||
- **THEN** 摘要 MUST be visually truncated in the cell
|
||||
- **AND** 用户 MUST be able to view the complete backend text on hover
|
||||
|
||||
#### Scenario: Paginate refunds without per-row approval requests
|
||||
|
||||
- **WHEN** 用户切换退款列表页码或刷新列表
|
||||
- **THEN** 页面 MUST use the refund list API response for approval summaries
|
||||
- **AND** 页面 MUST NOT issue approval-detail requests per refund row
|
||||
@@ -0,0 +1,33 @@
|
||||
## 1. List Contracts
|
||||
|
||||
- [x] 1.1 扩展退款、代理充值和换货列表项类型,支持 `submitter_name`、`approval_source`、`approval_status`、`approval_status_name`、`current_approver_summary`、`processing_status`、`processing_status_name`。
|
||||
- [x] 1.2 确认三个列表 API 使用列表响应直接提供上述字段,不新增逐条审批详情查询。
|
||||
|
||||
## 2. Shared Summary Behavior
|
||||
|
||||
- [x] 2.1 实现审批来源展示规则:`none` 显示 `-`,`legacy` 显示“历史审批”且只读,`wecom` 显示后端审批状态名称。
|
||||
- [x] 2.2 将当前审批人摘要限制为单行省略,并提供完整文本悬浮提示。
|
||||
- [x] 2.3 将业务处理状态独立显示为后端 `processing_status_name`,缺失时显示稳定占位内容。
|
||||
|
||||
## 3. Refund List
|
||||
|
||||
- [x] 3.1 在退款列表增加提交人、审批状态、当前审批人摘要、业务处理状态列。
|
||||
- [x] 3.2 保留退款既有审批与业务操作,不为历史审批记录增加新操作按钮。
|
||||
|
||||
## 4. Agent Recharge List
|
||||
|
||||
- [x] 4.1 在代理充值列表增加提交人、审批状态、当前审批人摘要、业务处理状态列。
|
||||
- [x] 4.2 保留代理充值既有确认支付、拒绝等操作,不为历史审批记录增加新操作按钮。
|
||||
|
||||
## 5. Exchange List
|
||||
|
||||
- [x] 5.1 在换货列表增加提交人、审批状态、当前审批人摘要、业务处理状态列。
|
||||
- [x] 5.2 保留换货既有流程和资产筛选逻辑,不为历史审批记录增加新操作按钮。
|
||||
|
||||
## 6. Verification
|
||||
|
||||
- [x] 6.1 验证三类列表在 `approval_source=none` 时审批状态和当前审批人摘要均显示 `-`。
|
||||
- [x] 6.2 验证 `approval_source=legacy` 时显示“历史审批”且没有新增审批操作,`wecom` 时显示后端审批状态和当前审批人摘要。
|
||||
- [x] 6.3 验证长当前审批人摘要会省略显示并能通过悬浮查看完整文本。
|
||||
- [x] 6.4 验证三个列表的业务处理状态独立显示,分页和刷新不触发逐行审批详情请求。
|
||||
- [x] 6.5 运行相关类型检查、lint 或构建验证。
|
||||
@@ -0,0 +1,54 @@
|
||||
# Change: 业务用户组管理与店铺批量交接/导入(AUG26-003)
|
||||
|
||||
## Why
|
||||
|
||||
后台需要把平台用户账号按业务线归入"业务用户组",并基于组对店铺做筛选、批量交接负责人与 CSV 导入负责人。当前前端只有单个店铺设置平台业务员的能力,缺少业务用户组维护、成员归属、按组筛选、批量交接与导入入口;且现有 11 个新端点仅超管与平台账号可访问。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增业务用户组管理模块(API 层 + 维护页面 + 成员管理):
|
||||
- GET/POST /api/admin/business-user-groups、GET/PUT/DELETE /api/admin/business-user-groups/{id}
|
||||
- PUT /api/admin/business-user-groups/{id}/members、DELETE /api/admin/business-user-groups/members
|
||||
- 编码创建后不可改;删除需 {"confirm": true} 且仅无成员组可删;更新支持部分字段,business_line 三态(缺省=不改 / ""=清空 / 枚举=设置)。
|
||||
- 成员归属整批校验(全部启用平台用户 + 目标组启用),任一无效整批不生效;一账号至多一组。
|
||||
- 店铺列表/详情读取侧扩展:
|
||||
- GET /api/admin/shops 新增 business_user_group_id / business_line / ungrouped 筛选。
|
||||
- 列表/详情响应新增 5 个只读推导字段(组 ID/编码/名称/启用/业务线);组停用仍返回组且 enabled=false(不算未分组);前端不缓存、不回写,改组后重新拉列表。
|
||||
- 勾选批量交接:
|
||||
- PUT /api/admin/shops/business-owner/batch:shop_ids(1-500,去重)+ business_owner_account_id;字段缺失=400,null=清空,ID=换绑;任一店铺无效或目标非启用业务员 -> 整批不写入,统一按 1005 提示。
|
||||
- CSV 导入:
|
||||
- 复用 StorageService.getUploadUrl + 预签名 PUT 直传(FilePurpose 增加 shop_import)。
|
||||
- POST /api/admin/shops/business-owner-imports 创建异步任务,轮询详情、展示行级结果;前端自带模板(表头 店铺编码,操作类型,业务员登录账号,备注,换绑/清空)。
|
||||
- 入口与权限(代理/企业不渲染入口):
|
||||
- 路由 meta roles ['R_SUPER', 'R_ADMIN'];按钮权限码:
|
||||
- business_user_group:page / business_user_group:create / business_user_group:update / business_user_group:delete / business_user_group:members
|
||||
- shop:business_owner_batch
|
||||
- shop:business_owner_import
|
||||
|
||||
## Not In Scope
|
||||
|
||||
- 不实现后端接口、不改数据库。
|
||||
- 业务用户组不承载角色权限/数据范围语义;前端不引入组层级与组管理员概念。
|
||||
- 导入结果不支持导出,仅在页面展示行级明细。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: business-user-group-management(新增)、shop-management(扩展)
|
||||
- Affected code:
|
||||
- src/types/api/businessUserGroup.ts(新增)
|
||||
- src/api/modules/businessUserGroup.ts(新增)
|
||||
- src/types/api/shop.ts、src/api/modules/shop.ts
|
||||
- src/api/modules/storage.ts(FilePurpose 增加 shop_import)
|
||||
- src/views/shop-management/business-user-groups/index.vue(新增页面)
|
||||
- src/views/shop-management/list/index.vue
|
||||
- src/router/routes/asyncRoutes.ts、src/router/routesAlias.ts、src/locales/langs/{zh,en}.json
|
||||
- src/template/批量换绑业务员模板.csv(前端自带模板)
|
||||
- API contracts: 11 个端点(7 个业务用户组 + 店铺筛选/字段 + 批量交接 + 导入三步)
|
||||
- Dependencies:
|
||||
- docs/产品迭代8月份/业务用户组.md(7 个组端点 OpenAPI)
|
||||
- AUG26-003 前端对接说明(店铺侧端点)
|
||||
|
||||
## 待确认
|
||||
|
||||
- 成员选择器复用 GET /api/admin/shops/business-owner-candidates(启用平台账号);若组成员可包含非业务员平台账号,需后端补充平台账号列表端点。
|
||||
- 导入任务与行级结果字段名(file_key、status、items[] 等)以生成文档为准,提案按对接说明先行对齐。
|
||||
@@ -0,0 +1,73 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 业务用户组维护
|
||||
|
||||
后台 MUST 提供业务用户组列表、详情、创建、更新与删除能力(GET/POST /api/admin/business-user-groups、GET/PUT/DELETE /api/admin/business-user-groups/{id})。列表 MUST 支持 page/page_size/enabled/keyword/business_line 筛选,且每项 MUST 返回 business_line_name。创建时 code(1-64)与 name 必填,编码未删除组内唯一且创建后不可修改;business_line 可空(standard/smart/other),sort/enabled/remark 可选。更新 MUST 仅允许名称、业务线、排序、启停与备注,且 business_line 支持三态:字段缺失不修改、传 "" 清空、传枚举设置;删除 MUST 携带 {"confirm": true},仅无成员组可删除。
|
||||
|
||||
#### Scenario: 查询业务用户组列表
|
||||
|
||||
- **GIVEN** 用户进入业务用户组维护页
|
||||
- **WHEN** 前端以 page/page_size/enabled/keyword/business_line 发起列表查询
|
||||
- **THEN** 前端 MUST 展示分页结果且每项显示 business_line_name
|
||||
- **AND** 下拉数据源复用该列表接口
|
||||
|
||||
#### Scenario: 创建时编码不可变
|
||||
|
||||
- **GIVEN** 用户填写名称与稳定编码创建用户组
|
||||
- **WHEN** 提交成功或编码重复被后端拒绝
|
||||
- **THEN** 编码在创建后 MUST NOT 出现在编辑表单中
|
||||
- **AND** 编码重复时 MUST 展示后端返回的"业务用户组编码已存在"
|
||||
|
||||
#### Scenario: 业务线三态更新
|
||||
|
||||
- **GIVEN** 用户编辑某组的业务线
|
||||
- **WHEN** 表单传 ""、传枚举或省略该字段
|
||||
- **THEN** 前端 MUST 分别按"清空 / 设置 / 不修改"构造请求体
|
||||
|
||||
#### Scenario: 删除需二次确认
|
||||
|
||||
- **GIVEN** 用户点击删除某组
|
||||
- **WHEN** 确认弹窗提交
|
||||
- **THEN** 前端 MUST 携带 {"confirm": true}
|
||||
- **AND** 有成员时 MUST 提示"用户组仍有成员,只能停用或先移走成员"且不做物理删除
|
||||
- **AND** 无成员时删除成功并刷新列表
|
||||
|
||||
### Requirement: 成员归属批量维护
|
||||
|
||||
后台 MUST 支持按平台用户账号把成员批量设置进组(PUT /api/admin/business-user-groups/{id}/members)与批量清空(DELETE /api/admin/business-user-groups/members,携带 body account_ids)。两种操作 MUST 复用同一校验:所有账号必须是启用平台用户且目标组启用,任一账号无效则整批不生效;清空后账号回到未分组;一账号至多一组。
|
||||
|
||||
#### Scenario: 批量设置成员
|
||||
|
||||
- **GIVEN** 用户在成员管理中选择多个启用平台账号
|
||||
- **WHEN** 保存成员归属
|
||||
- **THEN** 前端 MUST 以 account_ids 数组整体替换每个账号原归属
|
||||
- **AND** 刷新后成员关系与最新分组一致
|
||||
|
||||
#### Scenario: 批量清空成员
|
||||
|
||||
- **GIVEN** 用户选择若干账号执行清空
|
||||
- **WHEN** 提交清空
|
||||
- **THEN** 前端 MUST 调用 DELETE /api/admin/business-user-groups/members 并携带 account_ids body
|
||||
- **AND** 清空成功的账号回到未分组
|
||||
|
||||
#### Scenario: 停用组的成员展示
|
||||
|
||||
- **GIVEN** 某组被停用但仍有成员
|
||||
- **WHEN** 用户在成员管理或店铺列表看到该组
|
||||
- **THEN** 前端 MUST 展示"已停用"标记并提供改组/清空入口
|
||||
|
||||
### Requirement: 访问控制与入口
|
||||
|
||||
业务用户组维护入口 MUST 仅对超级管理员与平台账号可见,代理/企业账号 MUST NOT 渲染入口;所有按钮 MUST 受权限码控制。
|
||||
|
||||
#### Scenario: 菜单按角色隐藏
|
||||
|
||||
- **GIVEN** 代理或企业账号登录
|
||||
- **WHEN** 系统渲染菜单
|
||||
- **THEN** MUST NOT 展示业务用户组菜单项
|
||||
|
||||
#### Scenario: 按钮权限控制
|
||||
|
||||
- **GIVEN** 平台账号具备部分业务用户组权限
|
||||
- **WHEN** 渲染操作按钮
|
||||
- **THEN** 前端 MUST 按 business_user_group:create/update/delete/members 控制显隐
|
||||
@@ -0,0 +1,75 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 店铺列表/详情业务用户组字段与筛选
|
||||
|
||||
店铺列表查询 MUST 支持 business_user_group_id、business_line、ungrouped 三个新筛选;列表与详情响应 MUST 提供 5 个只读推导字段:business_user_group_id(可空)、business_user_group_code、business_user_group_name、business_user_group_enabled、business_user_group_business_line。组停用仍返回组且 enabled=false(不算未分组);店铺不存组,字段实时推导,前端 MUST NOT 缓存或回写,改动组成员后重新拉取列表。
|
||||
|
||||
#### Scenario: 按业务用户组筛选
|
||||
|
||||
- **GIVEN** 用户在店铺列表选择业务用户组、业务线或勾选"未分组"
|
||||
- **WHEN** 发起列表查询
|
||||
- **THEN** 前端 MUST 提交 business_user_group_id/business_line/ungrouped 参数
|
||||
- **AND** ungrouped=true 表示无负责人或负责人无分组
|
||||
|
||||
#### Scenario: 展示组字段
|
||||
|
||||
- **GIVEN** 店铺属于某启用或停用的业务用户组
|
||||
- **WHEN** 渲染列表或详情
|
||||
- **THEN** 前端 MUST 展示组名称/编码/业务线
|
||||
- **AND** 组停用时 MUST 标记"已停用"且仍展示组归属
|
||||
|
||||
### Requirement: 勾选批量交接平台业务员
|
||||
|
||||
店铺列表 MUST 支持勾选店铺批量交接平台业务员(PUT /api/admin/shops/business-owner/batch,body shop_ids 1-500 去重 + business_owner_account_id)。字段缺失 MUST 按参数错误处理(400);传 null 表示清空负责人;传 ID 表示换绑。任一店铺不存在/已删除/越权或目标非启用业务员时整批不写入,前端 MUST 统一提示"无权限操作该资源或资源不存在";成功响应含 batch_key/shop_count/cleared。
|
||||
|
||||
#### Scenario: 批量换绑
|
||||
|
||||
- **GIVEN** 用户勾选 1-500 家店铺并选择启用业务员
|
||||
- **WHEN** 提交批量交接
|
||||
- **THEN** 前端 MUST 提交 shop_ids(去重)与 business_owner_account_id
|
||||
- **AND** 成功后展示 shop_count 并刷新列表
|
||||
|
||||
#### Scenario: 批量清空负责人
|
||||
|
||||
- **GIVEN** 用户勾选店铺并选择"清空负责人"
|
||||
- **WHEN** 提交批量交接
|
||||
- **THEN** 前端 MUST 显式提交 business_owner_account_id: null
|
||||
- **AND** MUST NOT 省略该字段
|
||||
|
||||
#### Scenario: 整批失败统一提示
|
||||
|
||||
- **GIVEN** 批量交接请求因任一店铺或目标账号不满足条件而被后端拒绝
|
||||
- **WHEN** 前端收到 1005
|
||||
- **THEN** 前端 MUST 展示统一文案且不写入任何店铺
|
||||
|
||||
### Requirement: 业务负责人 CSV 导入
|
||||
|
||||
店铺列表 MUST 支持通过 CSV 导入批量交接/清空业务负责人。流程 MUST 为:前端自带模板(表头 店铺编码,操作类型,业务员登录账号,备注,操作类型仅"换绑"或"清空")-> POST /api/admin/storage/upload-url(purpose=shop_import)拿预签名 URL 直传(15 分钟有效)-> POST /api/admin/shops/business-owner-imports(file_key)创建异步任务 -> 轮询 GET /api/admin/shops/business-owner-imports/{id} 展示结果。行级失败不等于任务失败:任务 status=3 也可能有失败行,MUST 按 items[] 展示明细;表头/编码不符为任务级失败,items 为空数组,只展示 error_message。
|
||||
|
||||
#### Scenario: 下载模板并上传
|
||||
|
||||
- **GIVEN** 用户进入导入界面
|
||||
- **WHEN** 点击下载模板或选择文件
|
||||
- **THEN** 前端 MUST 提供表头完全一致的模板文件
|
||||
- **AND** 上传后 MUST 以 purpose=shop_import 获取上传地址并直传
|
||||
|
||||
#### Scenario: 创建任务并轮询
|
||||
|
||||
- **GIVEN** 文件上传成功拿到 file_key
|
||||
- **WHEN** 提交创建导入任务
|
||||
- **THEN** 前端 MUST 携带 file_key 调用创建接口
|
||||
- **AND** MUST 轮询任务详情直到 status 为已完成(3)或失败(4)
|
||||
|
||||
#### Scenario: 展示行级失败明细
|
||||
|
||||
- **GIVEN** 任务完成但存在失败行
|
||||
- **WHEN** 前端渲染结果
|
||||
- **THEN** 前端 MUST 展示 total_count/success_count/fail_count
|
||||
- **AND** MUST 按 items[] 展示各行的 line/shop_code/operation_type/status/reason
|
||||
- **AND** 失败行保留原负责人
|
||||
|
||||
#### Scenario: 任务级失败提示
|
||||
|
||||
- **GIVEN** 表头或编码不符导致任务级失败
|
||||
- **WHEN** 前端渲染结果
|
||||
- **THEN** 前端 MUST 只展示 error_message 且明细为空
|
||||
34
openspec/changes/add-business-user-group-management/tasks.md
Normal file
34
openspec/changes/add-business-user-group-management/tasks.md
Normal file
@@ -0,0 +1,34 @@
|
||||
## 1. API Contract 层
|
||||
|
||||
- [x] 1.1 新增 src/types/api/businessUserGroup.ts:组项/分页/创建/更新/删除/成员设置与结果类型
|
||||
- [x] 1.2 新增 src/api/modules/businessUserGroup.ts:封装 7 个组端点(DELETE 带 body,需请求层支持)
|
||||
- [x] 1.3 扩展 src/types/api/shop.ts:列表筛选 business_user_group_id/business_line/ungrouped,响应只读组字段,批量交接与导入任务/行级结果类型
|
||||
- [x] 1.4 扩展 src/api/modules/shop.ts:batchUpdateBusinessOwner、createBusinessOwnerImport、getBusinessOwnerImportDetail、getBusinessOwnerImportList
|
||||
- [x] 1.5 扩展 src/api/modules/storage.ts:FilePurpose 增加 shop_import
|
||||
|
||||
## 2. 业务用户组页面
|
||||
|
||||
- [x] 2.1 新增 src/views/shop-management/business-user-groups/index.vue:列表(筛选/分页/启停/业务线)
|
||||
- [x] 2.2 新建/编辑弹窗:code 创建后不可改、business_line 三态、名称/排序/备注/启停
|
||||
- [x] 2.3 删除:二次确认(confirm=true),有成员时按后端提示处理
|
||||
- [x] 2.4 成员管理(对话框/抽屉):成员选择器(复用 business-owner-candidates)+ 批量设置 + 批量清空;停用组保留成员并标记"已停用"
|
||||
|
||||
## 3. 店铺列表扩展
|
||||
|
||||
- [x] 3.1 列表搜索区新增业务用户组下拉与业务线筛选、ungrouped 勾选(数据源来自组列表接口)
|
||||
- [x] 3.2 列表/详情展示组字段(停用组标记,不缓存不回写)
|
||||
- [x] 3.3 批量交接弹窗:勾选店铺 + 选择业务员/清空(显式 null),整批失败统一 1005 文案
|
||||
- [x] 3.4 导入入口:模板下载、文件校验/上传(purpose=shop_import)、创建任务、轮询并展示行级明细
|
||||
- [x] 3.5 导入任务列表(状态筛选)
|
||||
|
||||
## 4. 路由/菜单/权限/i18n
|
||||
|
||||
- [x] 4.1 新增 /shop-management/business-user-groups 路由与菜单,roles ['R_SUPER', 'R_ADMIN']
|
||||
- [x] 4.2 按钮权限编码落地(business_user_group*/shop:business_owner_batch/shop:business_owner_import)
|
||||
- [x] 4.3 中英文案 menus.shopManagement.businessUserGroups 等
|
||||
|
||||
## 5. 验证
|
||||
|
||||
- [x] 5.1 运行 npm run build(含 vue-tsc --noEmit)
|
||||
- [x] 5.2 运行 npm run check:encoding
|
||||
- [x] 5.3 运行 openspec validate add-business-user-group-management --strict
|
||||
@@ -0,0 +1,22 @@
|
||||
## Context
|
||||
|
||||
现有前端没有运营商通道阈值命中记录页面或对应 API 类型。后端已提供只读分页查询接口,页面需忠实呈现不可变的命中时快照和周期恢复状态。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
- Goals: 提供受限于平台账号的筛选、分页和证据查询;不丢失空值的历史语义。
|
||||
- Non-Goals: 修改通道阈值、发起停复机、导出记录、查看卡片详情,或查询上游响应。
|
||||
|
||||
## Decisions
|
||||
|
||||
- Decision: 在系统管理路径下新增独立隐藏查询页,由运营商管理页提供入口;路由使用 `allowedUserTypes: [1, 2]`,页面自身也在请求前检查平台账号。
|
||||
- Rationale: 接口只允许超级管理员和平台账号。前端隐藏/保护页面入口,后端仍是最终授权及卡数据范围过滤边界。
|
||||
- Decision: 精确 ID 筛选使用数值输入,计费周期起点使用日期时间选择器,判定时间使用日期时间范围选择器;时间序列化为带时区 RFC3339 秒级字符串。
|
||||
- Rationale: 与接口的精确匹配和闭区间语义一致,避免按日期截断或丢失时区。
|
||||
- Decision: 页面仅展示响应快照,不再查询通道配置或根据当前阈值重算历史值。
|
||||
- Rationale: 命中值冻结于判定时;历史缺失值必须保留接口规定的空值含义。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- 查询页不依赖后端菜单节点;前端入口仅对平台账号显示,页面路由限制用户类型,API 仍执行最终授权和数据范围过滤。
|
||||
- 表格包含多列证据字段,采用现有可横向滚动的管理台表格以保持信息完整。
|
||||
@@ -0,0 +1,24 @@
|
||||
# Change: 新增运营商通道阈值命中记录查询
|
||||
|
||||
## Why
|
||||
|
||||
达量停机与周期恢复需要可追溯的数字证据。运营人员需要查询每次停机判定时冻结的累计流量、实际阈值、计费周期、触发来源,以及周期解锁和复机结果;通道阈值后续变更不能影响历史记录。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 在运营商管理页提供“通道阈值命中记录”入口,打开独立只读查询页并接入 `GET /api/admin/carrier-traffic-threshold-hits`。
|
||||
- 支持按运营商通道 ID、IoT 卡 ID、计费周期起点精确匹配,并按判定时间闭区间筛选。
|
||||
- 展示命中时的流量和阈值快照、判定/触发信息、锁状态、解锁时间、复机结果及安全失败原因。
|
||||
- 仅超级管理员与平台账号可访问;数据范围过滤及越权资源不可区分由后端强制执行,前端不替代后端授权。
|
||||
- 对接口定义的空历史值使用明确的“无”或“未处理/历史记录”展示,不发起额外的通道阈值或上游接口查询。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `carrier-traffic-threshold-hits`
|
||||
- Affected code:
|
||||
- `src/api/modules/carrierTrafficThresholdHit.ts`
|
||||
- `src/types/api/carrierTrafficThresholdHit.ts`
|
||||
- `src/views/system/carrier-traffic-threshold-hits/index.vue`
|
||||
- `src/router/routesAlias.ts`, `src/router/routes/staticRoutes.ts`, `src/views/system/carrier-management/index.vue`
|
||||
- `src/locales/langs/zh.json`, `src/locales/langs/en.json`
|
||||
- Breaking changes: 无;仅新增只读查询接口消费与页面入口。
|
||||
@@ -0,0 +1,35 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Carrier Traffic Threshold Hit Record Query
|
||||
|
||||
The admin frontend SHALL provide a read-only paginated view of carrier traffic threshold hit records using `GET /api/admin/carrier-traffic-threshold-hits`.
|
||||
|
||||
#### Scenario: Restrict page access to platform accounts
|
||||
|
||||
- **GIVEN** a user is not a super administrator or platform account
|
||||
- **WHEN** the user navigates to the carrier traffic threshold hit page
|
||||
- **THEN** the frontend MUST deny access and MUST NOT issue the hit-record query
|
||||
- **AND** backend authorization and card data-scope filtering MUST remain authoritative
|
||||
|
||||
#### Scenario: Filter hit records
|
||||
|
||||
- **GIVEN** an authorized platform user opens the hit-record page
|
||||
- **WHEN** the user searches by optional carrier ID, card ID, billing period start, or judged-at time range
|
||||
- **THEN** the frontend MUST send `carrier_id`, `card_id`, `period_start`, `start_time`, and `end_time` only when provided
|
||||
- **AND** period and judged-at timestamps MUST be timezone-qualified RFC3339 values with second precision
|
||||
- **AND** `start_time` and `end_time` MUST represent the API's inclusive time interval
|
||||
|
||||
#### Scenario: Display immutable hit evidence and recovery result
|
||||
|
||||
- **GIVEN** the query returns threshold-hit records
|
||||
- **WHEN** the frontend renders the table
|
||||
- **THEN** it MUST display record/card/carrier IDs, hit traffic, frozen threshold value and unit, billing period start, judged time, trigger source, lock status, unlock time, resume result, failure reason, and creation time
|
||||
- **AND** it MUST NOT recompute hit traffic or threshold from current channel configuration
|
||||
- **AND** it MUST display nullable historical traffic/threshold values as “无”, blank resume results as “未处理或历史记录”, and missing unlock/failure details as “无”
|
||||
|
||||
#### Scenario: Preserve server ordering and pagination
|
||||
|
||||
- **GIVEN** the user queries hit records
|
||||
- **WHEN** the frontend loads or changes the page
|
||||
- **THEN** it MUST send `page` and `page_size` (never exceeding 100)
|
||||
- **AND** it MUST render the server-provided page, size, total, and item order without client-side re-sorting
|
||||
@@ -0,0 +1,10 @@
|
||||
## 1. API Contract
|
||||
|
||||
- [x] 1.1 增加命中记录查询参数、记录项及分页响应类型。
|
||||
- [x] 1.2 增加 `GET /api/admin/carrier-traffic-threshold-hits` 服务方法并统一导出。
|
||||
|
||||
## 2. Admin UI
|
||||
|
||||
- [x] 2.1 新增超级管理员/平台账号可访问的隐藏路由、运营商管理页入口及中英文标题。
|
||||
- [x] 2.2 实现筛选、分页和命中/周期恢复快照表格,按接口约定展示空值。
|
||||
- [x] 2.3 运行 OpenSpec 校验、ESLint 与生产构建。
|
||||
60
openspec/changes/add-commission-clawback-records/proposal.md
Normal file
60
openspec/changes/add-commission-clawback-records/proposal.md
Normal file
@@ -0,0 +1,60 @@
|
||||
# Change: 退款佣金回扣改为独立回溯明细(前端适配)
|
||||
|
||||
## Why
|
||||
|
||||
后端调整了退款佣金回扣口径:退款不再把原佣金整单置为「已失效」,而是原佣金行保持「已发放」不变,另新增一条独立负数、不可提现的「回溯明细」行。对应前端接口说明(简短版)要求:
|
||||
|
||||
- 佣金记录列表新增 `status` 查询参数(含 5 回溯)与行级 `source` 字段(`original` / `clawback`)。
|
||||
- 新增佣金记录详情接口 `GET /api/admin/shops/{shop_id}/commission-records/{id}?source=clawback`。
|
||||
- 新增导出场景 `scene=commission_record`(后端已进白名单)。
|
||||
- 两个必改点:列表行 key 必须用 `source + ':' + id`(原佣金与回溯 ID 空间独立,同一页会重复);渲染需支持负数金额(标红)与「不可提现」标识。
|
||||
|
||||
前端当前实现基于旧语义(`ShopCommissionRecordItem` 无 `source`,列表行 key 直接用 `id`,退款后原行被视为已失效),需按新口径适配。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 类型层:`ShopCommissionRecordItem` 新增 `source`、`original_commission_id`、`refund_id`、`refund_no`、`withdrawable`、`clawback_records`、`clawback_total_amount`;新增回溯摘要与详情类型;`CommissionRecordQueryParams.status` 支持 5(回溯)。
|
||||
- API 层:新增 `getShopCommissionRecordDetail(shopId, id, source?)`,`source` 省略时按原佣金处理。
|
||||
- 列表页(代理侧「我的佣金」与管理侧「代理资金概览 > 佣金明细」):行 key 改为 `source + ':' + id`;回溯行展示「回溯」状态与「不可提现」标识;负数金额与可为负的 `balance_after` 标红;`status` 筛选项新增「回溯」;详情入口必须携带该行 `source`。
|
||||
- 详情展示:原佣金详情展示 `clawback_records` 摘要与 `clawback_total_amount`;回溯详情展示来源 `original_commission`;越权/不存在统一提示「佣金明细不存在」,不做存在性判断。
|
||||
- 导出:`ExportTaskScene` 增加 `commission_record`;新增导出佣金记录场景页、路由、菜单与 i18n;佣金记录列表导出入口只提交受支持的筛选 key(`shop_id` / `status` / `commission_source` / `order_no`)。
|
||||
- 字段兜底:后端新增字段为 `omitempty`,前端取 `?? []` / `?? 0`,金额单位为分。
|
||||
|
||||
## Not In Scope
|
||||
|
||||
- 不实现后端接口、不改数据库、不改审批实例数据。
|
||||
- 既有字段无改名/改类型;`commission-stats`、`commission-daily-stats` 口径未变,本次不动。
|
||||
- 时间筛选属另一 Change(`add-export-time-filter-standards`),本次不涉及。
|
||||
- 语义提醒:退款不再写 `status=4`,旧假设「退款后原行变已失效」已失效,需在文案/注释体现。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `commission-management`、`export-task-management`
|
||||
- Affected code:
|
||||
- `src/types/api/commission.ts`
|
||||
- `src/api/modules/commission.ts`
|
||||
- `src/views/commission-management/my-commission/index.vue`
|
||||
- `src/views/commission-management/agent-fund-overview/index.vue`
|
||||
- `src/types/api/exportTask.ts`
|
||||
- `src/config/constants/exportTask.ts`
|
||||
- `src/views/asset-management/export-task-management/export-commission-record/index.vue`
|
||||
- `src/router/routes/asyncRoutes.ts`、`src/router/routesAlias.ts`、`src/locales/langs/{zh,en}.json`
|
||||
- Dependencies:
|
||||
- `docs/产品迭代8月份/frontend-api-simple.md`(后端契约)
|
||||
- 后端已把 `scene=commission_record` 加入导出场景白名单
|
||||
- 需确认导出场景权限编码与场景页是否必需(见 Open Questions)
|
||||
- Breaking changes:
|
||||
- 列表行 key 由 `id` 改为 `source + ':' + id`;未携带 `source` 的详情请求会命中原佣金行。
|
||||
|
||||
## 接口确认结果(来自 OpenAPI)
|
||||
|
||||
- 详情响应 `DtoShopCommissionRecordDetailResp`:`source`、`record`(`DtoShopCommissionRecordItem`)、`clawback_records`(仅原佣金返回)、`original_commission`(仅回溯详情返回)。
|
||||
- `DtoShopCommissionRecordItem` 新增 `source`、`released_at`、`withdrawable`(boolean,nullable,仅回溯行返回且恒 false)、`original_commission_id`、`refund_id`、`refund_no`、`clawback_records`、`clawback_total_amount`。
|
||||
- `DtoShopCommissionClawbackItem`:`id`、`amount`(恒负)、`balance_after`(可为负)、`original_commission_id`、`refund_id`、`refund_no`、`status`(5 回溯)、`status_name`、`withdrawable`、`created_at`。
|
||||
- 详情接口越权与不存在返回同一结果,前端统一提示「佣金明细不存在」。
|
||||
- 已确认需要新增「导出佣金记录」菜单页。
|
||||
|
||||
## 待确认(已按仓库既有约定实现,如需调整请告知)
|
||||
|
||||
1. 导出场景权限编码:按既有约定实现为 `export_task:commission_record_detail` / `export_task:commission_record_download`。
|
||||
2. 佣金记录列表导出按钮权限:按 `agent_wallet_transaction:export` 的同级约定实现为 `commission_record:export`。
|
||||
@@ -0,0 +1,48 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 佣金记录列表回溯行与状态筛选
|
||||
佣金记录列表(`GET /api/admin/shops/{shop_id}/commission-records`)MUST 支持 `status` 查询参数(1 已冻结 / 2 解冻中 / 3 已发放 / 4 已失效 / 5 回溯 / 99 待人工修正),且 MUST NOT 提供 `source` 查询参数;`status=5` 即等价于只看回溯行。
|
||||
|
||||
#### Scenario: 只看回溯行
|
||||
- **GIVEN** 用户在佣金记录列表选择状态「回溯」
|
||||
- **WHEN** 前端发起列表查询
|
||||
- **THEN** 前端 MUST 只传 `status=5`
|
||||
- **AND** 前端 MUST NOT 传 `source` 参数
|
||||
|
||||
### Requirement: 佣金记录行新增字段与兜底
|
||||
列表响应的每一行 MUST 支持 `source`(`original` / `clawback`);回溯行 MUST 支持 `original_commission_id`、`refund_id`、`refund_no`、`withdrawable`(恒 `false`)与可为负数的 `amount`、`balance_after`;原佣金行 MUST 支持 `clawback_records` 摘要与 `clawback_total_amount`(负值)。后端 `omitempty` 缺省字段前端 MUST 以 `?? []` / `?? 0` 兜底,金额单位为分。
|
||||
|
||||
#### Scenario: 缺省字段兜底
|
||||
- **GIVEN** 列表响应中的原佣金行未返回 `clawback_records`
|
||||
- **WHEN** 前端渲染该行
|
||||
- **THEN** 前端 MUST 按空数组处理并正常渲染
|
||||
- **AND** 前端 MUST NOT 因缺省字段报错或渲染 `undefined`
|
||||
|
||||
### Requirement: 列表行标识与负数渲染
|
||||
列表 MUST 使用 `source + ':' + id` 作为行 key(原佣金与回溯 ID 空间独立,同一页可能出现相同 `id`);回溯行 MUST 展示「不可提现」标识;负数 `amount` 与 `balance_after` MUST 标红显示;任何跳转详情的入口 MUST 携带该行的 `source`,缺省按原佣金处理。
|
||||
|
||||
#### Scenario: 同一页出现重复 id
|
||||
- **GIVEN** 同一页列表中同时存在原佣金行与回溯行且 `id` 相同
|
||||
- **WHEN** 前端渲染表格
|
||||
- **THEN** 前端 MUST 以 `source + ':' + id` 区分两行
|
||||
- **AND** 前端 MUST NOT 出现行复用或渲染错位
|
||||
|
||||
#### Scenario: 负数金额标红
|
||||
- **GIVEN** 某回溯行 `amount` 为负值
|
||||
- **WHEN** 前端渲染金额列
|
||||
- **THEN** 前端 MUST 标红展示该负值
|
||||
|
||||
### Requirement: 佣金记录详情接口封装
|
||||
前端 MUST 提供 `GET /api/admin/shops/{shop_id}/commission-records/{id}` 的详情封装,并支持可选 `source`:`source=clawback` 时返回回溯详情,`source` 省略时按原佣金处理。原佣金详情 MUST 返回 `clawback_records`;回溯详情 MUST 返回 `original_commission`;越权与不存在 MUST 返回同一结果(佣金明细不存在),前端 MUST NOT 用该接口做存在性判断。
|
||||
|
||||
#### Scenario: 打开回溯行详情
|
||||
- **GIVEN** 用户在列表点击某条回溯行
|
||||
- **WHEN** 前端请求详情
|
||||
- **THEN** 前端 MUST 携带 `source=clawback` 与该行 `id`
|
||||
- **AND** 详情 MUST 展示来源 `original_commission`
|
||||
|
||||
#### Scenario: 越权统一提示
|
||||
- **GIVEN** 详情接口返回「佣金明细不存在」
|
||||
- **WHEN** 前端渲染详情
|
||||
- **THEN** 前端 MUST 展示统一不存在提示
|
||||
- **AND** 前端 MUST NOT 区分越权与不存在两种原因
|
||||
@@ -0,0 +1,19 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 佣金记录导出场景
|
||||
前端 MUST 支持导出场景 `scene=commission_record`(后端已进白名单),并在导出管理中提供该场景的任务列表入口;创建导出任务时 MUST 提交固定 `scene=commission_record`。导出粒度为佣金记录:原佣金与回溯各占一行,金额与余额同样按分转元、负数带 `-` 展示。
|
||||
|
||||
#### Scenario: 场景页固定查询
|
||||
- **GIVEN** 用户打开导出佣金记录页面
|
||||
- **WHEN** 页面查询导出任务列表
|
||||
- **THEN** 前端 MUST 调用 `GET /api/admin/export-tasks` 且带 `scene=commission_record`
|
||||
- **AND** 用户 MUST NOT 能在该页面切换到其他场景
|
||||
|
||||
### Requirement: 佣金记录导出筛选受限
|
||||
佣金记录列表发起导出时,`query` MUST 只包含后端支持的筛选 key:`shop_id`、`status`、`commission_source`、`order_no`;MUST NOT 提交 `iccid`、`virtual_no` 及时间筛选,导出弹窗 MUST NOT 直接复用列表全部条件。
|
||||
|
||||
#### Scenario: 列表筛选含不支持的 key
|
||||
- **GIVEN** 佣金记录列表当前筛选包含 `iccid` 与时间范围
|
||||
- **WHEN** 用户确认创建导出任务
|
||||
- **THEN** 提交的 `query` MUST NOT 包含 `iccid`、`virtual_no` 或时间字段
|
||||
- **AND** 提交的 `query` MUST 仅保留 `shop_id`、`status`、`commission_source`、`order_no` 中已填写的项
|
||||
27
openspec/changes/add-commission-clawback-records/tasks.md
Normal file
27
openspec/changes/add-commission-clawback-records/tasks.md
Normal file
@@ -0,0 +1,27 @@
|
||||
## 1. 类型与 API 层(commission-api)
|
||||
- [x] 1.1 `CommissionStatus` 补充 5(回溯);修正 `CommissionRecordQueryParams.status` 过期注释并支持回溯值
|
||||
- [x] 1.2 `ShopCommissionRecordItem` 新增 `source`、`original_commission_id`、`refund_id`、`refund_no`、`withdrawable`、`clawback_records`、`clawback_total_amount`
|
||||
- [x] 1.3 新增回溯摘要与佣金记录详情类型(原佣金详情含 `clawback_records`,回溯详情含 `original_commission`)
|
||||
- [x] 1.4 `CommissionService` 新增 `getShopCommissionRecordDetail(shopId, id, source?)`
|
||||
|
||||
## 2. 列表页(commission-records-list)
|
||||
- [x] 2.1 行 key 改为 `source + ':' + id`(`my-commission` 与 `agent-fund-overview` 佣金明细)
|
||||
- [x] 2.2 回溯行展示「回溯」状态与「不可提现」标识
|
||||
- [x] 2.3 负数金额与可为负的 `balance_after` 标红渲染
|
||||
- [x] 2.4 `status` 筛选项新增「回溯」
|
||||
- [x] 2.5 列表新增详情入口,且请求必须携带该行 `source`
|
||||
|
||||
## 3. 详情展示(commission-record-detail)
|
||||
- [x] 3.1 原佣金详情展示 `clawback_records` 摘要与 `clawback_total_amount`
|
||||
- [x] 3.2 回溯详情展示来源 `original_commission`
|
||||
- [x] 3.3 越权/不存在统一提示「佣金明细不存在」,不作为存在性判断依据
|
||||
|
||||
## 4. 导出(commission-record-export)
|
||||
- [x] 4.1 `ExportTaskScene` 增加 `commission_record` 并补场景配置
|
||||
- [x] 4.2 新增导出佣金记录场景页、路由、菜单与中英文案
|
||||
- [x] 4.3 佣金记录列表新增导出入口,`query` 仅提交 `shop_id` / `status` / `commission_source` / `order_no`
|
||||
|
||||
## 5. 验证
|
||||
- [x] 5.1 运行 `npm run build`(含 `vue-tsc --noEmit`)
|
||||
- [x] 5.2 运行 `npm run check:encoding`
|
||||
- [x] 5.3 运行 `openspec.cmd validate add-commission-clawback-records --strict`
|
||||
88
openspec/changes/add-employee-collection/design.md
Normal file
88
openspec/changes/add-employee-collection/design.md
Normal file
@@ -0,0 +1,88 @@
|
||||
## Context
|
||||
|
||||
员工代收款是 8 月迭代新增的财务能力,普通员工与超级管理员共用同一套接口,靠登录态区分数据范围。后台管理端需要新增三类页面,并复用已有的表格、搜索、详情与上传组件。`docs/admin-openapi.yaml` 未随仓库提供,接口字段以后端契约(需求文档 + 创建订单接口 OpenAPI 片段)为准,类型集中在一个文件便于联调收敛。
|
||||
|
||||
## Goals / Non-Goals
|
||||
|
||||
**Goals**
|
||||
|
||||
- 在财务管理下提供收款方式、员工代收款账单、核销申请三类页面。
|
||||
- 复用 `ArtTableFullScreen`、`ArtSearchBar`、`ArtTableHeader`、`ArtTable`、`DetailPage`、`VoucherUpload`、`PaymentVoucherDialog`、`useCheckedColumns` 等既有组件与约定。
|
||||
- 复用既有企微审批场景配置能力,仅新增业务类型。
|
||||
|
||||
**Non-Goals**
|
||||
|
||||
- 不实现后端接口、数据库、Worker、企微回调。
|
||||
- 不实现 H5/C 端页面与支付流程。
|
||||
- 不新增导出任务场景(需求文档未要求)。
|
||||
|
||||
## Decisions
|
||||
|
||||
### 接口契约
|
||||
|
||||
| 能力 | 关键字段 |
|
||||
|---|---|
|
||||
| 统一响应 | `{ code, data, msg, timestamp }` |
|
||||
| 列表分页 | 账单列表返回 `{ items, total, page, size }`,取数处对 `items` / `list` / `records` 做兼容 |
|
||||
| 收款方式 | `{ id, code, name, sort, enabled, remark, created_at, updated_at }`,列表接口返回 `{ items, page, size, total }`,支持 `page` / `page_size` / `enabled` / `keyword` 筛选 |
|
||||
| 账单列表项 | `{ id, source_type, source_type_name, source_no, debtor_snapshot, customer_snapshot, receivable_amount, received_amount, reserved_amount, remaining_amount, status, status_name, approval_pending, closed_reason, created_at, updated_at }` |
|
||||
| 账单详情 | `data` 为 `{ bill, refunds, allocations, applications }`;`refunds` 为退款冲销(`refund_id`、`source_order_id`、`refund_amount`、`reduced_amount`、`bill_receivable_amount`、`outcome_name`),`allocations` 为账单侧分摊(含 `application_id` / `application_status_name` / `attempt_id`),`applications` 内嵌该申请的 `attempts` |
|
||||
| 账单统计 | `{ receivable_total, received_total, unsettled_total, pending_bill_count }` |
|
||||
| 账单筛选 | `page`、`page_size`、`source_type`、`source_no`、`status`、`debtor_account_id`、`customer_id`、`created_from`(`YYYY-MM-DD`)、`created_to`(`YYYY-MM-DD`) |
|
||||
| 核销申请请求体 | `{ payment_method_id, paid_amount, paid_at, payer_name, external_transaction_no, payment_voucher_keys, remark, allocations: [{ bill_id, amount }], acting_reason }` |
|
||||
| 核销申请列表项 | `{ id, applicant_account_id, acting_operator_id, payment_method_id, payment_method_name, paid_amount, payer_name, external_transaction_no, status, status_name, terminal_reason, decided_at, created_at, updated_at }` |
|
||||
| 核销申请详情 | `data` 为 `{ application, allocations, attempts }`,`attempts` 保存每次提交的完整材料快照,重新提交不清空历史 |
|
||||
|
||||
账单状态为数字枚举 `0` 待核销 / `1` 部分核销 / `2` 已核销 / `3` 已关闭;申请状态为数字枚举 `0` 审批中 / `1` 已通过 / `2` 已驳回 / `3` 已撤销或已关闭;两者展示均优先使用后端 `status_name`。
|
||||
|
||||
### 页面与路由组织
|
||||
|
||||
在 `/finance` 下新增:
|
||||
|
||||
| 路由 | 页面 | 说明 |
|
||||
|---|---|---|
|
||||
| `/finance/employee-collection/bills` | 员工代收款账单 | 统计 + 列表 |
|
||||
| `/finance/employee-collection/bills/detail/:id` | 账单详情 | 隐藏菜单 |
|
||||
| `/finance/employee-collection/applications` | 核销申请 | 列表 + 创建 |
|
||||
| `/finance/employee-collection/applications/detail/:id` | 核销申请详情 | 隐藏菜单 |
|
||||
| `/finance/employee-collection/payment-methods` | 收款方式管理 | 仅超管 |
|
||||
|
||||
账单与申请拆分为独立菜单,符合项目「列表页 + 详情页」的既有组织方式,避免单页堆叠过多交互。账单列表的「店铺」筛选用远程搜索复用 `ShopService.getShops`,与退款列表一致。
|
||||
|
||||
账单详情与核销申请详情保持只读:页面只在顶部保留「返回」导航,创建核销申请、关闭账单、修改并重新提交等操作入口统一放在列表页的操作列,详情页不出现业务操作按钮。
|
||||
|
||||
### 权限编码
|
||||
|
||||
新增 `src/config/constants/augustIteration.ts`,沿用 `模块:动作` 风格,例如 `employee_collection:bill_close`、`employee_collection:application_create`。页面级 `permissions` 用于菜单可见性,按钮级编码用于 `hasAuth()` / `v-permission`。
|
||||
|
||||
### 金额、时间与附件
|
||||
|
||||
- 金额统一以「分」传输,展示时通过 `fenToYuan` / `formatCurrency` 转换,与退款、代理充值保持一致。
|
||||
- 所有时间字段统一通过 `formatDateTime` 格式化为 `YYYY-MM-DD HH:mm:ss`,不在模板中直接输出后端原始时间字符串。
|
||||
- 附件仅返回对象 Key(`payment_voucher_keys`),展示复用 `PaymentVoucherDialog`,由预签名下载接口换取访问地址。
|
||||
|
||||
### 核销申请分摊
|
||||
|
||||
创建申请时按账单逐条录入核销金额,并填写付款事实(付款金额、付款方名称、付款时间、外部交易流水号),前端校验:
|
||||
|
||||
- 至少选择 1 张账单,最多 N 张;
|
||||
- 单张核销金额不得大于账单未核销金额,且大于 0;
|
||||
- 付款金额(`paid_amount`,分)不得小于各账单分摊之和(允许存在差额);
|
||||
- 超管代办时 `acting_reason` 必填;
|
||||
- 付款凭证至少 1 个 Key。
|
||||
|
||||
提交成功后自动发起企微审批;仅已驳回申请可再次进入弹窗修改并重新提交,重新提交生成新的审批实例,历史审批记录只读展示。未配置企微审批场景时后端返回 503,前端展示「企微审批场景未配置,请联系管理员」并保留已填内容。
|
||||
|
||||
### 企微审批场景
|
||||
|
||||
`WecomBusinessType` 增加 `employee_collection_approval`,企微审批场景页面下拉新增「员工代收款审批」。模板控件同步、字段查询、字段映射保存全部复用既有 `WecomService`。
|
||||
|
||||
### 订单付款凭证规则
|
||||
|
||||
线下订单创建时,满足「平台账号(`user_type` 为 1 或 2)操作 + 非赠送套餐 + 实际收款金额大于 0」条件的订单会生成员工代收款账单,此时 `payment_voucher_key` 非必填,字段结构不变,付款凭证改在核销申请中提交。前端以当前登录账号类型、所选套餐是否赠送、套餐有效价格(`effective_retail_price` / `suggested_retail_price` / `retail_price`)判断是否展示提示并放宽必填;赠送套餐或其他非平台账号的线下订单仍需上传凭证。
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
- **接口字段以契约文档为准**:`docs/admin-openapi.yaml` 未入库,字段来自需求文档与创建订单接口片段;类型集中在一个文件,便于联调时收敛修改。
|
||||
- **员工/超管同接口**:前端不做数据范围过滤,仅做展示与操作可见性控制,数据隔离以后端为准。
|
||||
- **关闭账单与审批中申请**:前端依据 `approval_pending` 与状态字段禁用关闭按钮,最终一致性以后端校验为准。
|
||||
25
openspec/changes/add-employee-collection/proposal.md
Normal file
25
openspec/changes/add-employee-collection/proposal.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Change: 员工代收款功能前端对接
|
||||
|
||||
## Why
|
||||
|
||||
8 月产品迭代新增「员工代收款」能力:员工线下代收款项后,通过创建核销申请、经企业微信审批完成账单核销;超级管理员可维护收款方式、查看全部账单并关闭账单。后端接口已按 `docs/产品迭代8月份/员工代收款功能简介.md` 落地,后台管理端目前缺少收款方式管理、账单列表与核销申请页面,普通员工与超级管理员的分类视图、以及线下订单付款凭证规则尚未接入。
|
||||
|
||||
本次已按后端实际契约对齐字段:列表响应统一使用 `items` / `total` / `page` / `size`;账单状态(`0` 待核销 / `1` 部分核销 / `2` 已核销 / `3` 已关闭)与申请状态(`0` 审批中 / `1` 已通过 / `2` 已驳回 / `3` 已撤销或已关闭)为数字枚举;收款方式列表返回 `{ items, page, size, total }` 并支持 `enabled` / `keyword` 筛选;核销申请请求体使用 `paid_amount`、`paid_at`、`payer_name`、`external_transaction_no`、`payment_voucher_keys` 与 `allocations`。
|
||||
|
||||
## What Changes
|
||||
|
||||
- 新增 `employee-collection` 能力的前端类型与服务封装:收款方式 4 个接口、员工代收款账单 4 个接口、核销申请 4 个接口。
|
||||
- 新增「收款方式管理」页面(仅超级管理员):列表 + 新增/编辑弹窗 + 删除;已被核销申请引用的方式不可删除、不可修改 `code`(未被引用时可改),可停用。
|
||||
- 新增「员工代收款账单」页面:应收/已核销/未核销/待处理账单统计 + 列表 + 详情;普通员工仅见本人账单,超级管理员可见全部;存在审批中申请时账单不可关闭,关闭必须填写原因。
|
||||
- 新增「核销申请」页面:列表 + 详情(含分摊账单、付款凭证、付款信息与全部审批尝试记录)+ 创建/重新提交弹窗;一笔线下收款可核销 1~N 张账单,填写付款金额、付款方名称、付款时间、外部交易流水号、选择收款方式并上传付款凭证;提交后自动发起企微审批;仅已驳回申请可修改并重新提交,重新提交生成新的审批实例且历史记录不被覆盖。
|
||||
- 扩展企业微信审批场景:新增 `employee_collection_approval` 业务类型,复用既有企微应用列表、模板控件同步与业务字段查询接口。
|
||||
- 调整订单创建:由平台账号操作、实际收款金额大于 0 且非赠送的线下订单会生成员工代收款账单,该场景 `payment_voucher_key` 改为非必填,付款凭证改在核销申请中提交,字段结构保持不变。
|
||||
- 附件接口仅返回对象 Key,统一通过系统既有预签名下载接口展示。
|
||||
- **不实现后端接口、数据库、Worker、企微回调**;**不实现 H5/C 端页面**。
|
||||
|
||||
## Impact
|
||||
|
||||
- Affected specs: `employee-collection`
|
||||
- Affected code: `src/types/api/employeeCollection.ts`、`src/api/modules/employeeCollection.ts`、`src/views/finance/employee-collection/*`、`src/router/routes/asyncRoutes.ts`、`src/router/routesAlias.ts`、`src/config/constants/augustIteration.ts`、`src/types/api/wecom.ts`、`src/views/settings/wecom/scenes/index.vue`、`src/views/order-management/order-list/index.vue`、`src/locales/langs/{zh,en}.json`
|
||||
- Dependencies: `docs/产品迭代8月份/员工代收款功能简介.md`
|
||||
- Contract note: `docs/admin-openapi.yaml` 未随仓库提供,字段以需求文档描述的后端契约与创建订单接口的 OpenAPI 片段为准;类型集中在单一文件,联调时便于收敛。
|
||||
@@ -0,0 +1,155 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: 收款方式管理
|
||||
超级管理员 MUST 能够维护线下收款方式,包括名称、编码、排序、状态与备注;普通员工只能看到启用的收款方式。收款方式列表接口 MUST 返回 `{ items, page, size, total }`,并 MUST 支持 `enabled` 与 `keyword` 筛选。已被核销申请引用的收款方式 MUST NOT 被删除;引用后修改稳定编码 MUST 被后端拒绝,前端 MUST 展示错误提示。
|
||||
|
||||
#### Scenario: 超级管理员新增收款方式
|
||||
- **GIVEN** 超级管理员已登录并拥有收款方式新增权限
|
||||
- **WHEN** 其填写名称、唯一编码、排序、状态与备注并提交
|
||||
- **THEN** 系统 MUST 调用新增接口并在成功后刷新列表
|
||||
- **AND** 新增成功后 MUST 清空并关闭弹窗
|
||||
|
||||
#### Scenario: 删除被引用的收款方式
|
||||
- **GIVEN** 某收款方式已被业务引用
|
||||
- **WHEN** 超级管理员尝试删除该方式
|
||||
- **THEN** 前端 MUST 阻止删除或展示后端返回的业务错误
|
||||
- **AND** MUST 提示改为停用
|
||||
|
||||
#### Scenario: 修改收款方式编码
|
||||
- **GIVEN** 超级管理员打开编辑弹窗
|
||||
- **WHEN** 其修改稳定编码并提交
|
||||
- **THEN** 前端 MUST 提交最新编码
|
||||
- **AND** 若该方式已被核销申请引用,后端拒绝时前端 MUST 展示错误提示
|
||||
|
||||
### Requirement: 员工代收款账单统计
|
||||
账单页面 MUST 展示应收金额、已核销金额、未核销金额与待处理账单数量四项统计,数据 MUST 来自 `GET /api/admin/employee-collection-bills/statistics`,字段为 `receivable_total`、`received_total`、`unsettled_total`、`pending_bill_count`;前端 MUST NOT 通过遍历当前分页数据自行计算。
|
||||
|
||||
#### Scenario: 加载账单统计
|
||||
- **GIVEN** 用户进入员工代收款账单页面
|
||||
- **WHEN** 页面初始化或筛选条件变化
|
||||
- **THEN** 前端 MUST 调用账单统计接口
|
||||
- **AND** MUST 将后端返回的「分」按元格式化后展示应收、已核销与未核销金额
|
||||
|
||||
### Requirement: 员工代收款账单列表与详情
|
||||
账单列表响应 MUST 为 `{ items, total, page, size }`,前端 MUST 兼容 `items` / `list` / `records` 等列表字段。列表 MUST 支持按来源(`source_type`)、来源单号(`source_no`)、账单状态、客户/店铺(`customer_id`)与创建时间(`created_from` / `created_to`,`YYYY-MM-DD`)筛选,并展示账单编号、来源、关联单号、负责员工、客户/店铺、应收金额、已核销金额、未核销金额与状态。账单状态 MUST 为数字枚举:`0` 待核销、`1` 部分核销、`2` 已核销、`3` 已关闭,展示 MUST 优先使用后端 `status_name`。账单详情响应 MUST 为 `{ bill, refunds, allocations, applications }`:`refunds` MUST 展示退款金额、冲减应收、冲销前应收与处理结果,`applications` MUST 可展开查看该申请的审批尝试记录。
|
||||
|
||||
#### Scenario: 普通员工查看账单
|
||||
- **GIVEN** 普通员工已登录
|
||||
- **WHEN** 其打开账单列表
|
||||
- **THEN** 列表 MUST 只展示后端返回的本人账单数据
|
||||
- **AND** MUST NOT 展示仅超管可见的操作入口
|
||||
|
||||
#### Scenario: 打开账单详情
|
||||
- **GIVEN** 用户拥有账单详情权限
|
||||
- **WHEN** 其点击账单号或详情操作
|
||||
- **THEN** 前端 MUST 跳转账单详情页并加载对应账单(详情数据取自 `data.bill`)
|
||||
- **AND** 详情 MUST 展示退款冲销、核销分摊与关联核销申请
|
||||
|
||||
### Requirement: 关闭账单
|
||||
超级管理员 MUST 能够关闭账单,且关闭原因必填(最多 500 字符)。仅待核销或部分核销账单可关闭;存在审批中的核销申请(`approval_pending` 为真)时,账单 MUST NOT 被关闭。
|
||||
|
||||
#### Scenario: 存在审批中申请时关闭账单
|
||||
- **GIVEN** 账单存在审批中的核销申请
|
||||
- **WHEN** 用户查看该账单操作
|
||||
- **THEN** 关闭入口 MUST 被禁用或不可见
|
||||
- **AND** MUST 展示不可关闭的原因提示
|
||||
|
||||
#### Scenario: 关闭原因必填
|
||||
- **GIVEN** 账单可关闭
|
||||
- **WHEN** 超级管理员打开关闭弹窗并留空原因提交
|
||||
- **THEN** 前端 MUST 阻止提交并提示填写原因
|
||||
|
||||
### Requirement: 创建核销申请
|
||||
员工 MUST 能够使用一笔线下收款核销 1~N 张账单。创建申请 MUST 提交收款方式 `payment_method_id`、付款金额 `paid_amount`(分,大于 0)、付款方名称 `payer_name`、付款时间 `paid_at`(带时区 RFC3339)、外部交易流水号 `external_transaction_no`、付款凭证 `payment_voucher_keys`(1~5 个对象 Key)与账单分摊 `allocations`。超级管理员代办时 MUST 填写 `acting_reason`,本人办理 MUST NOT 提交该字段。提交成功后系统 MUST 自动发起企业微信审批。
|
||||
|
||||
#### Scenario: 一笔收款核销多张账单
|
||||
- **GIVEN** 用户选择了多张可核销账单
|
||||
- **WHEN** 其录入各账单核销金额、选择收款方式并填写付款事实后提交
|
||||
- **THEN** 前端 MUST 校验各账单核销金额大于 0 且不超过账单未核销余额
|
||||
- **AND** MUST 以 `allocations: [{ bill_id, amount }]` 提交账单分摊明细
|
||||
|
||||
#### Scenario: 付款金额小于核销合计
|
||||
- **GIVEN** 用户已录入各账单核销金额
|
||||
- **WHEN** 其填写的付款金额小于核销合计即提交
|
||||
- **THEN** 前端 MUST 阻止提交并提示付款金额不能小于核销合计
|
||||
|
||||
#### Scenario: 缺少付款凭证
|
||||
- **GIVEN** 用户已选择账单与收款方式
|
||||
- **WHEN** 其未上传任何付款凭证即提交
|
||||
- **THEN** 前端 MUST 阻止提交并提示上传付款凭证
|
||||
|
||||
#### Scenario: 缺少付款事实
|
||||
- **GIVEN** 用户已选择账单与收款方式
|
||||
- **WHEN** 其未填写付款方名称、付款时间或外部交易流水号即提交
|
||||
- **THEN** 前端 MUST 阻止提交并提示补齐必填项
|
||||
|
||||
#### Scenario: 超管代办未填写原因
|
||||
- **GIVEN** 超级管理员以代办身份创建申请
|
||||
- **WHEN** 其未填写 `acting_reason` 即提交
|
||||
- **THEN** 前端 MUST 阻止提交并提示填写代办原因
|
||||
|
||||
#### Scenario: 企微审批场景未配置
|
||||
- **GIVEN** 企业微信审批场景尚未配置
|
||||
- **WHEN** 用户提交核销申请
|
||||
- **THEN** 前端 MUST 展示后端返回的 503 提示「企微审批场景未配置,请联系管理员」
|
||||
- **AND** MUST 保留用户已填写的内容且不产生申请数据
|
||||
|
||||
### Requirement: 核销申请列表与详情
|
||||
核销申请列表响应 MUST 为 `{ items, page, size, total }`,MUST 支持按状态、收款方式与创建时间筛选;列表项 MUST 包含 `payment_method_name`、`paid_amount`、`status`、`status_name` 与 `created_at`,状态 MUST 优先展示后端 `status_name`。申请详情响应 MUST 为 `{ application, allocations, attempts }`;`attempts` MUST 按提交顺序展示全部审批尝试记录,包含付款金额、付款方、流水号、付款凭证与审批意见。
|
||||
|
||||
#### Scenario: 查看审批历史
|
||||
- **GIVEN** 申请存在多次审批尝试记录
|
||||
- **WHEN** 用户打开申请详情
|
||||
- **THEN** 详情 MUST 按提交顺序展示每次尝试的提交材料与审批状态
|
||||
- **AND** 历史材料 MUST NOT 因重新提交而被覆盖
|
||||
|
||||
### Requirement: 核销申请重新提交
|
||||
仅已驳回(`status` 为 `2`)的申请 MUST 允许修改并重新提交;重新提交 MUST 生成新的企业微信审批实例,且历史审批记录 MUST NOT 被覆盖。重新提交入口 MUST 位于核销申请列表的操作列,详情页 MUST 只读且 MUST NOT 展示业务操作按钮(仅保留返回导航)。
|
||||
|
||||
#### Scenario: 重新提交被驳回申请
|
||||
- **GIVEN** 申请状态为已驳回
|
||||
- **WHEN** 用户在核销申请列表点击「修改并重新提交」并修改账单分摊、收款方式、付款事实或付款凭证后提交
|
||||
- **THEN** 前端 MUST 调用修改接口重新提交
|
||||
- **AND** 成功后 MUST 刷新详情并展示新的审批实例状态
|
||||
|
||||
#### Scenario: 非驳回申请不可修改
|
||||
- **GIVEN** 申请处于审批中或已通过
|
||||
- **WHEN** 用户查看核销申请列表
|
||||
- **THEN** 修改并重新提交入口 MUST 不可见或不可用
|
||||
|
||||
#### Scenario: 详情页只读
|
||||
- **GIVEN** 用户打开账单详情或核销申请详情
|
||||
- **WHEN** 页面渲染完成
|
||||
- **THEN** 页面 MUST NOT 展示创建核销申请、关闭账单或修改并重新提交等业务操作按钮
|
||||
- **AND** MUST 只保留返回导航
|
||||
|
||||
### Requirement: 企业微信审批场景配置
|
||||
企业微信审批场景 MUST 支持 `employee_collection_approval` 业务类型,复用既有的应用列表、模板控件同步、业务字段查询与字段映射保存接口。
|
||||
|
||||
#### Scenario: 配置员工代收款审批场景
|
||||
- **GIVEN** 超级管理员打开企微审批场景页面
|
||||
- **WHEN** 其选择业务类型「员工代收款审批」
|
||||
- **THEN** 前端 MUST 使用 `employee_collection_approval` 调用模板同步、字段查询与保存接口
|
||||
|
||||
### Requirement: 附件预签名展示
|
||||
附件接口 MUST 只返回对象存储 Key(`payment_voucher_keys`);前端 MUST 通过系统既有的预签名下载接口获取实际访问地址后再展示。
|
||||
|
||||
#### Scenario: 查看付款凭证
|
||||
- **GIVEN** 申请包含付款凭证 Key
|
||||
- **WHEN** 用户点击查看付款凭证
|
||||
- **THEN** 前端 MUST 先批量换取预签名地址
|
||||
- **AND** 图片 MUST 支持预览,非图片 MUST 支持查看或下载
|
||||
|
||||
### Requirement: 订单付款凭证规则调整
|
||||
由平台账号(`user_type` 为 1 或 2)操作、实际收款金额大于 0 且非赠送的线下订单会生成员工代收款账单;该场景 `payment_voucher_key` MUST 变为非必填,付款凭证改在核销申请中提交,订单字段结构 MUST 保持不变。其余线下订单 MUST 继续要求付款凭证。
|
||||
|
||||
#### Scenario: 线下订单生成代收款账单
|
||||
- **GIVEN** 当前登录账号为平台账号,所选套餐非赠送且实际收款金额大于 0,支付方式为线下支付
|
||||
- **WHEN** 用户创建该订单
|
||||
- **THEN** 前端 MUST 不再强制要求上传付款凭证
|
||||
- **AND** MUST 提示付款凭证将在核销申请中提交
|
||||
|
||||
#### Scenario: 赠送套餐或非平台账号的线下订单
|
||||
- **GIVEN** 所选套餐为赠送套餐,或当前账号非平台账号,或实际收款金额为 0
|
||||
- **WHEN** 用户以线下支付方式创建订单
|
||||
- **THEN** 前端 MUST 继续要求上传付款凭证
|
||||
48
openspec/changes/add-employee-collection/tasks.md
Normal file
48
openspec/changes/add-employee-collection/tasks.md
Normal file
@@ -0,0 +1,48 @@
|
||||
## 1. Contract and API Types
|
||||
|
||||
- [x] 1.1 新增 `src/types/api/employeeCollection.ts`:收款方式、账单、核销申请、统计、查询参数与请求/响应类型;列表统一使用 `items` / `total` / `page` / `size`。
|
||||
- [x] 1.2 定义账单状态(`0` 待核销 / `1` 部分核销 / `2` 已核销 / `3` 已关闭)与申请状态(`0` 审批中 / `1` 已通过 / `2` 已驳回 / `3` 已撤销或已关闭)数字枚举,并保留后端 `*_name` 展示字段。
|
||||
- [x] 1.3 金额字段以「分」传输;附件字段使用 `payment_voucher_keys` 对象存储 Key 数组,展示复用预签名下载接口。
|
||||
- [x] 1.4 新增 `src/api/modules/employeeCollection.ts` 并在 `src/api/modules/index.ts`、`src/types/api/index.ts` 导出。
|
||||
- [x] 1.5 按后端实际契约收敛字段:账单详情为 `{ bill, refunds, allocations, applications }`,核销申请详情为 `{ application, allocations, attempts }`,付款金额/付款方/付款时间/外部交易流水号以 `paid_amount` / `payer_name` / `paid_at` / `external_transaction_no` 提交。
|
||||
|
||||
## 2. Permissions, Routes, and Menu
|
||||
|
||||
- [x] 2.1 新增 `src/config/constants/augustIteration.ts`,集中声明页面与按钮权限编码。
|
||||
- [x] 2.2 在 `src/router/routesAlias.ts` 与 `src/router/routes/asyncRoutes.ts` 的财务管理下新增账单、核销申请、收款方式路由。
|
||||
- [x] 2.3 在 `src/locales/langs/zh.json`、`en.json` 的 `menus.financialManagement` 下补充菜单文案。
|
||||
|
||||
## 3. Payment Methods Page
|
||||
|
||||
- [x] 3.1 实现收款方式列表(名称、编码、排序、状态、备注、创建时间);接口返回 `{ items, page, size, total }`,复用 `ArtTableFullScreen` / `ArtSearchBar` / `ArtTableHeader` / `ArtTable`。
|
||||
- [x] 3.2 实现新增/编辑弹窗;编辑时允许提交 `code`,被核销申请引用时由后端拒绝并提示。
|
||||
- [x] 3.3 实现删除操作,被引用的方式给出提示并引导停用。
|
||||
|
||||
## 4. Bills Pages
|
||||
|
||||
- [x] 4.1 实现账单统计卡片(应收、已核销、未核销、待处理账单数量),数据来自 `GET /api/admin/employee-collection-bills/statistics`。
|
||||
- [x] 4.2 实现账单列表与筛选(来源、来源单号、状态、客户/店铺、创建时间范围),展示账单号、来源、关联单号、负责员工、客户/店铺、应收/已核销/未核销金额与状态。
|
||||
- [x] 4.3 实现账单详情,展示账单信息、退款冲销、核销分摊与关联核销申请(关联申请可展开查看审批尝试记录)。
|
||||
- [x] 4.4 实现超管关闭账单弹窗,关闭原因必填;存在审批中申请时禁用关闭并给出说明。
|
||||
- [x] 4.5 列表「创建核销申请」入口按权限与账单状态控制可用性。
|
||||
|
||||
## 5. Applications Pages
|
||||
|
||||
- [x] 5.1 实现核销申请列表与筛选(状态、收款方式、创建时间),展示申请编号、收款方式、付款金额、状态与提交时间。
|
||||
- [x] 5.2 实现创建/重新提交弹窗:选择 1~N 张可核销账单、按账单录入分摊金额、填写付款金额/付款方名称/付款时间/外部交易流水号、选择收款方式并上传付款凭证。
|
||||
- [x] 5.3 超管代办时必须填写 `acting_reason`,否则禁止提交。
|
||||
- [x] 5.4 实现申请详情,展示申请信息、分摊账单、付款凭证与全部审批尝试记录;历史记录只读,不被重新提交覆盖。
|
||||
- [x] 5.5 仅已驳回申请展示「修改并重新提交」,提交成功后生成新的审批实例并刷新详情。
|
||||
- [x] 5.6 统一处理 503「企微审批场景未配置」等业务错误,保留用户已填内容。
|
||||
|
||||
## 6. WeCom Scene and Order Rule
|
||||
|
||||
- [x] 6.1 扩展 `WecomBusinessType` 增加 `employee_collection_approval`,并在企微审批场景页面新增可选业务类型。
|
||||
- [x] 6.2 场景保存复用既有 `inspectTemplate`、`getBusinessFields`、`saveScene` 接口,无需新增企微接口。
|
||||
- [x] 6.3 调整线下订单创建:平台账号操作、非赠送且实际收款金额大于 0 时 `payment_voucher_key` 非必填,字段结构不变。
|
||||
|
||||
## 7. Verification
|
||||
|
||||
- [x] 7.1 运行 `npm run build`(含 `vue-tsc --noEmit`)与 `npm run check:encoding`,确保类型与编码通过。
|
||||
- [x] 7.2 校验普通员工与超管的菜单、列与操作可见性差异。 — 已核验:应用/账单/收款方式页 v-permission 按钮、bills 关闭操作 hasAuth(billClose)+canCloseBill、表单 isActing=isSuperAdmin 控制代办字段
|
||||
- [x] 7.3 校验金额分/元转换、附件预签名展示与 503 错误兜底。 — 已核验:ApplicationFormDialog 用 fenToYuan/yuanToFen;detail.vue 用 PaymentVoucherDialog 预览凭证;getErrorMessage 提取后端 msg(含 503 未配置场景)兜底
|
||||
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 模块和类型均为增量能力。
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user