90 lines
3.2 KiB
Markdown
90 lines
3.2 KiB
Markdown
|
# lsfx-mock All 模式 SQL 对齐强命中 Frontend Implementation Plan
|
||
|
|
|
||
|
|
> **For agentic workers:** REQUIRED: Use superpowers:executing-plans to implement this plan. Steps use checkbox (`- [ ]`) syntax for tracking.
|
||
|
|
|
||
|
|
**Goal:** 确认本次 `lsfx-mock-server` all 模式强命中改造不要求前端代码改动，并完成联调展示面的最小核验。
|
||
|
|
|
||
|
|
**Architecture:** 本次需求只调整 Mock 样本与关联表基线，不改前端接口契约和页面逻辑。前端计划因此以“不改代码、做联调核验、必要时补记录”为主，防止误把本次后端改造扩散到 `ruoyi-ui`。
|
||
|
|
|
||
|
|
**Tech Stack:** Vue 2, 现有项目详情页与标签展示页、浏览器手工联调
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### Task 1: 核对前端是否存在配套改动需求
|
||
|
|
|
||
|
|
**Files:**
|
||
|
|
- Review: `ruoyi-ui/src/views/ccdiProject/components/detail/DetailQuery.vue`
|
||
|
|
- Review: `ruoyi-ui/src/views/ccdiProject/components/detail/RiskModelSection.vue`
|
||
|
|
- Review: `ruoyi-ui/src/views/ccdiProject/components/detail/RiskPeopleSection.vue`
|
||
|
|
- Reference: `docs/design/2026-03-25-lsfx-mock-all-hit-sql-alignment-design.md`
|
||
|
|
|
||
|
|
- [ ] **Step 1: 核对接口契约是否变化**
|
||
|
|
|
||
|
|
确认本次后端与 Mock 改造不会新增字段、不会更改命中标签结构、不会更改模型编码和规则编码。
|
||
|
|
|
||
|
|
Expected:
|
||
|
|
- 不需要前端 API 或组件适配
|
||
|
|
|
||
|
|
- [ ] **Step 2: 核对命中展示组件是否依赖旧样本文案**
|
||
|
|
|
||
|
|
重点确认页面只依赖：
|
||
|
|
- `modelCode`
|
||
|
|
- `ruleCode`
|
||
|
|
- `ruleName`
|
||
|
|
- `reasonDetail`
|
||
|
|
|
||
|
|
而不是绑定旧的样本文案词汇。
|
||
|
|
|
||
|
|
- [ ] **Step 3: 若确认无代码变更，保持前端零改动**
|
||
|
|
|
||
|
|
本次不新增前端提交。
|
||
|
|
|
||
|
|
### Task 2: 执行展示联调核验
|
||
|
|
|
||
|
|
**Files:**
|
||
|
|
- Review: `ruoyi-ui/src/views/ccdiProject/components/detail/DetailQuery.vue`
|
||
|
|
- Review: `ruoyi-ui/src/views/ccdiProject/components/detail/RiskModelSection.vue`
|
||
|
|
- Modify: `docs/reports/implementation/2026-03-25-lsfx-mock-all-hit-sql-alignment-record.md`
|
||
|
|
|
||
|
|
- [ ] **Step 1: 使用后端联调结果回查页面展示**
|
||
|
|
|
||
|
|
核验页面上能正常展示以下 5 条规则的命中标签或模型归类：
|
||
|
|
- `SPECIAL_AMOUNT_TRANSACTION`
|
||
|
|
- `MONTHLY_FIXED_INCOME`
|
||
|
|
- `SUSPICIOUS_INCOME_KEYWORD`
|
||
|
|
- `FIXED_COUNTERPARTY_TRANSFER`
|
||
|
|
- `LOW_INCOME_RELATIVE_LARGE_TRANSACTION`
|
||
|
|
|
||
|
|
- [ ] **Step 2: 核对 `reasonDetail` 展示是否正常**
|
||
|
|
|
||
|
|
Expected:
|
||
|
|
- 金额、月份、对手方等信息可正常展示
|
||
|
|
- 不因新样本文案变化导致空白或布局问题
|
||
|
|
|
||
|
|
- [ ] **Step 3: 若页面无异常，仅在实施记录中注明“前端无需改动”**
|
||
|
|
|
||
|
|
在实施记录中补一段简短说明：
|
||
|
|
- 本次接口结构无变化
|
||
|
|
- 前端展示正常
|
||
|
|
- 无需修改 `ruoyi-ui`
|
||
|
|
|
||
|
|
- [ ] **Step 4: 若启动了前端调试进程，结束后主动停止**
|
||
|
|
|
||
|
|
遵循仓库约定，测试结束后关闭本次启动的前端进程。
|
||
|
|
|
||
|
|
### Task 3: 收尾确认
|
||
|
|
|
||
|
|
**Files:**
|
||
|
|
- Review: `docs/plans/frontend/2026-03-25-lsfx-mock-all-hit-sql-alignment-frontend-implementation.md`
|
||
|
|
|
||
|
|
- [ ] **Step 1: 确认本计划未引入任何前端功能改造任务**
|
||
|
|
|
||
|
|
Expected:
|
||
|
|
- 前端计划只保留“核对无改动需求 + 联调验证”两类任务
|
||
|
|
|
||
|
|
- [ ] **Step 2: 若联调发现前端异常，再单独新开设计与实施计划**
|
||
|
|
|
||
|
|
约束：
|
||
|
|
- 不在本计划中顺带插入前端功能修复
|
||
|
|
- 避免业务范围偏移
|