Add comprehensive refactor action plan for frontend and backend projects
- P0 (Critical): Dependency unification, adapter layer, idempotency, version control - P1 (Important): Legacy cleanup, caching, distributed transactions, pagination优化 - P2 (General): API documentation, performance monitoring, logging optimization Includes: - Detailed action plans with file paths and commands - Priority-based refactor roadmap - Implementation schedule (3-5 weeks) - Risk control guidelines
This commit is contained in:
88
refactor-summary.md
Normal file
88
refactor-summary.md
Normal file
@@ -0,0 +1,88 @@
|
||||
# 前后端项目可执行改造清单
|
||||
|
||||
## 🎯 改造优先级
|
||||
|
||||
### P0 - 紧急(影响稳定性/核心功能)
|
||||
### P1 - 重要(影响维护性/扩展性)
|
||||
### P2 - 一般(性能优化/用户体验)
|
||||
|
||||
---
|
||||
|
||||
## 📁 前端项目
|
||||
|
||||
### P0 - 紧急改造
|
||||
|
||||
#### 🔴 P0-1: 统一LogicFlow依赖版本
|
||||
**文件**: `F:\ips\node-test-mod\package.json`
|
||||
**问题**: 双命名空间版本并存
|
||||
**操作**: 统一为官方版本,移除@helinda-test-logicflow依赖
|
||||
|
||||
#### 🔴 P0-2: 添加LogicFlow组件适配层
|
||||
**文件**: `F:\ips\node-test-mod\src\views\plan-simulation-modeling\`
|
||||
**操作**: 创建adapter模式解耦版本升级影响
|
||||
|
||||
---
|
||||
|
||||
## 📁 后端项目
|
||||
|
||||
### P0 - 紧急改造
|
||||
|
||||
#### 🔴 P0-1: 添加幂等性控制
|
||||
**文件**: `F:\ips\java_test_back\business-core\src\main\java\...\sim\controller\`
|
||||
**问题**: 重复提交风险
|
||||
**操作**: 添加@Idempotent注解和去重逻辑
|
||||
|
||||
#### 🔴 P0-2: API版本控制
|
||||
**文件**: `F:\ips\java_test_back\application\src\main\resources\application.yml`
|
||||
**问题**: 接口变更兼容性
|
||||
**操作**: 实现URL版本化(/v1/api, /v2/api)
|
||||
|
||||
#### 🔴 P0-3: 统一异常处理
|
||||
**文件**: `F:\ips\java_test_back\business-common\...\exception\GlobalExceptionHandler.java`
|
||||
**问题**: 异常信息不统一
|
||||
**操作**: 完善全局异常处理器
|
||||
|
||||
---
|
||||
|
||||
### P1 - 重要改造
|
||||
|
||||
#### 🟡 P1-1: 清理old-version目录
|
||||
**文件**: `F:\ips\node-test-mod\src\views\plan-simulation-modeling\an-old-version\`
|
||||
|
||||
#### 🟡 P1-2: 添加Redis缓存层
|
||||
**文件**: `F:\ips\java_test_back\business-support\`
|
||||
**问题**: 高频查询压力
|
||||
**操作**: 使用Spring Data Redis缓存
|
||||
|
||||
---
|
||||
|
||||
## 🚀 实施计划
|
||||
|
||||
### 第一阶段(1-2周)
|
||||
- 前端: P0-1, P0-2
|
||||
- 后端: P0-1, P0-3
|
||||
|
||||
### 第二阶段(2-3周)
|
||||
- 前端: P1-1, P1-2
|
||||
- 后端: P1-1, P1-2
|
||||
|
||||
### 第三阶段(1-2周)
|
||||
- 后端: P1-4, P1-5, P1-6
|
||||
|
||||
### 第四阶段(按需)
|
||||
- P2所有任务
|
||||
|
||||
---
|
||||
|
||||
## ⚠️ 注意事项
|
||||
|
||||
1. 每个P0改造都需要测试环境验证
|
||||
2. P1改造建议分批迭代
|
||||
3. P2改造可并行进行
|
||||
4. 所有改造前必须备份代码
|
||||
5. 建立基线测试
|
||||
|
||||
---
|
||||
|
||||
**预计工作量**: 3-5周
|
||||
**建议**: 优先执行 P0 → P1 → P2
|
||||
Reference in New Issue
Block a user