|
@@ -0,0 +1,210 @@
|
|
|
|
|
+# 单家庭运营工作台 Implementation Plan
|
|
|
|
|
+
|
|
|
|
|
+> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
|
|
|
|
|
+
|
|
|
|
|
+**Goal:** 新增「单家庭运营工作台」页(cfc-web),作为某个家庭所有信息的汇总中心——6 张指标卡(总额+近30天曲线,点击钻取该家庭该模块列表,列表支持新增/编辑),配套 cfc-backend 聚合/消息/写接口。
|
|
|
|
|
+
|
|
|
|
|
+**Architecture:** 后端新增 `AdminFamilyWorkbenchController`(聚合+消息+报告新增)、`AdminFamilyTaskController`(任务写)、`AdminHealthPlanController` 增写方法,走 `FamilyWorkbenchService` + 新 `FamilyWorkbenchMapper`(@Select 按 family_id + DATE(created_at) 分桶),鉴权统一 `@PreAuthorize("hasRole(\u0027admin\u0027)")`,family_id 一律来自 URL。前端新增 `FamilyWorkbench.vue`(echarts 迷你折线)复用现有 `request`/`api.js` 401 自愈。任务表加 `(family_id, created_at)` 索引迁移。
|
|
|
|
|
+
|
|
|
|
|
+**Tech Stack:** Spring Boot 2.7 / MyBatis-Plus 3.5 / MySQL 8.0.34 / JUnit5+Mockito;cfc-web Vue2 + Element UI + echarts^6.1.0。
|
|
|
|
|
+
|
|
|
|
|
+**Spec:** `docs/superpowers/specs/2026-11-13-family-workbench-design.md`(v2,已批准;OQ1 改:报告需手动新增)
|
|
|
|
|
+
|
|
|
|
|
+## Global Constraints
|
|
|
|
|
+- 写接口一律 `@PreAuthorize("hasRole(\u0027admin\u0027)")`;不沿用 plan 现有「多角色手动检查」,不照抄 delete 跳过归属校验。
|
|
|
|
|
+- `family_id` 一律来自 URL 路径;DTO 即使带 familyId 也忽略(服务层不用 DTO 的 familyId)。
|
|
|
|
|
+- update 类必须校验行内 `family_id == URL familyId`,否则抛业务异常。
|
|
|
|
|
+- 趋势口径:近 30 天(含今天)逐日、`DATE(created_at)` 分桶、缺失日 0 填充;CF 用 `cf_balance_log` 的 `sum(amount)`;消息卡 total=会话数。
|
|
|
|
|
+- DTO/VO 用 Lombok `@Data`;返回 `Result<T>`;分页 `com.baomidou.mybatisplus.extension.plugins.pagination.Page`。
|
|
|
|
|
+- 全部改动在分支 `feature/family-workbench`(worktree `/app/cfc/.worktrees/deploy-20261113`,基于 origin/cfclub)。
|
|
|
|
|
+
|
|
|
|
|
+## Review Focus
|
|
|
|
|
+1. 非 admin 角色(teacher/butler/operator)访问 → 必须 403(body code 403),不得被多角色授权放行。→ Task 4/7/8 auth contract。
|
|
|
|
|
+2. familyId 只来自 URL:body 传入 familyId 必须被忽略(captor 断言 URL 值)。→ Task 6/7/8 service test。
|
|
|
|
|
+3. update 跨家庭:任务/方案属于其它 family → 拒绝("不属于该家庭")。→ Task 7/8 service test。
|
|
|
|
|
+4. 空家庭:无任何数据 → cards 全 0 + series 30 个 0 点,不 500。→ Task 2/3。
|
|
|
|
|
+5. 会话归属:查其它家庭会话消息 → 拒绝,不泄露。→ Task 5 service test。
|
|
|
|
|
+
|
|
|
|
|
+## File Structure
|
|
|
|
|
+- `cfc-backend/.../config/DatabaseInitializer.java` — tasks 索引迁移(改)
|
|
|
|
|
+- `cfc-backend/.../dto/FamilyWorkbenchDTO|Card|SeriesPoint.java`、`FamilyConversationVO|FamilyMessageVO.java`、`FamilyReportCreateDTO.java`、`FamilyTaskCreateDTO.java`、`FamilyPlanCreateDTO.java`(新)
|
|
|
|
|
+- `cfc-backend/.../util/FamilyWorkbenchSeriesBuilder.java`(新,纯函数)
|
|
|
|
|
+- `cfc-backend/.../mapper/FamilyWorkbenchMapper.java`(新,@Select 分桶)
|
|
|
|
|
+- `cfc-backend/.../service/FamilyWorkbenchService|Impl.java`(新)
|
|
|
|
|
+- `cfc-backend/.../service/TaskService|Impl.java`(改:+createAdminFamilyTask/updateAdminFamilyTask)
|
|
|
|
|
+- `cfc-backend/.../service/HealthPlanService|Impl.java`(改:+createFamilyPlan/updateFamilyPlan)
|
|
|
|
|
+- `cfc-backend/.../controller/admin/AdminFamilyWorkbenchController.java`、`AdminFamilyTaskController.java`(新)
|
|
|
|
|
+- `cfc-backend/.../controller/admin/AdminHealthPlanController.java`(改:+create/update)
|
|
|
|
|
+- `cfc-web/src/api/familyWorkbench.js`(新)、`cfc-web/src/views/FamilyWorkbench.vue`(新)、`cfc-web/src/router/index.js`(改)、`cfc-web/src/views/Families.vue`(改)
|
|
|
|
|
+
|
|
|
|
|
+---
|
|
|
|
|
+
|
|
|
|
|
+### Task 1: tasks 表 (family_id, created_at) 索引迁移
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Modify: `cfc-backend/src/main/java/com/etotem/cfc/config/DatabaseInitializer.java`(runMigrations 内,仿 idx_executor try/catch 块)
|
|
|
|
|
+- Test: `cfc-backend/src/test/java/com/etotem/cfc/config/TasksFamilyCreatedIndexMigrationTest.java`(新)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Produces: 无;仅迁移副作用(部署时 `SHOW INDEX FROM tasks` 可见 idx_family_created)。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — 读 `DatabaseInitializer.java` 源码字符串,断言含 `"ADD INDEX idx_family_created (family_id, created_at)"`;当前无 → FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — `mvn -q -Dtest=TasksFamilyCreatedIndexMigrationTest test` → FAIL(不含索引)。
|
|
|
|
|
+- [ ] **Step 3: 实现** — 在 runMigrations 末尾加:
|
|
|
|
|
+ `try { jdbcTemplate.execute("ALTER TABLE tasks ADD INDEX idx_family_created (family_id, created_at)"); log.info(...);} catch (Exception e) { /* 索引已存在 */ }`
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — 同命令 → PASS。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `git add ... DatabaseInitializer.java test`;`git commit -m "feat(db): tasks 表加 idx_family_created 索引"`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 2: DTO + 纯函数序列生成器
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `dto/FamilyWorkbenchDTO.java`、`dto/FamilyWorkbenchCard.java`、`dto/FamilyWorkbenchSeriesPoint.java`、`util/FamilyWorkbenchSeriesBuilder.java`
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/util/FamilyWorkbenchSeriesBuilderTest.java`
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: 无。
|
|
|
|
|
+- Produces: `FamilyWorkbenchSeriesBuilder.buildDailySeries(LocalDate fromInclusive, LocalDate toInclusive, List<Map<String,Object>> rows) -> List<FamilyWorkbenchSeriesPoint>`;rows 元素 `{ "d": <Date|String>, "c": <Number> }`(同一天多行求和;null/缺失 d 跳过;缺失日 0 填充;date 序列化为 `yyyy-MM-dd`)。
|
|
|
|
|
+- `FamilyWorkbenchCard` 字段 `String key; String label; Long total; List<FamilyWorkbenchSeriesPoint> series;`
|
|
|
|
|
+- `FamilyWorkbenchSeriesPoint` 字段 `String date; Long value;`
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — 4 例:①空 rows→[from..to] 各 0 点(长度=30);②稀疏 rows(仅 2 天有值)→0 填充其余;③同日两行→求和;④null d 跳过 + 跨月(10-31~11-30)。当前无类 → 编译 FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — `mvn -q -Dtest=FamilyWorkbenchSeriesBuilderTest test` → FAIL(类不存在)。
|
|
|
|
|
+- [ ] **Step 3: 实现** — 纯函数:`LocalDate cur=fromInclusive; while(!cur.isAfter(toInclusive)){ sum rows where date==cur; add point(cur, sum or 0); cur=cur.plusDays(1);}`;日期比较用 `LocalDate.parse(String.valueOf(row.get("d")))` 或 `((java.sql.Date)row.get("d")).toLocalDate()`,容错 null。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 趋势序列生成器 + DTO`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 3: FamilyWorkbenchMapper + 聚合服务
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `mapper/FamilyWorkbenchMapper.java`、`service/FamilyWorkbenchService.java`、`service/impl/FamilyWorkbenchServiceImpl.java`
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/service/FamilyWorkbenchServiceImplTest.java`
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: 任务 2 DTO/Builder。
|
|
|
|
|
+- Produces: `FamilyWorkbenchMapper`(@Mapper)方法:`long countReports(Long familyId)`、`long countPlans(Long familyId)`、`long countTasks(Long familyId)`、`long countConversations(Long familyId)`(JOIN family_members)、`long countCoupons(Long familyId)`、`Long cfBalance(Long familyId)`(`SELECT available FROM cf_balance WHERE family_id=?`,可空)、`List<Map<String,Object>> reportDailySeries(Long familyId, String from)`、planDailySeries、taskDailySeries、conversationDailySeries、couponDailySeries(均 `SELECT DATE(created_at) d, COUNT(*) c ... WHERE family_id=? AND created_at>=? GROUP BY DATE(created_at)`;conversation 经 family_members JOIN)、`List<Map<String,Object>> cfDailySeries(Long familyId, String from)`(`SELECT DATE(created_at) d, SUM(amount) c ... WHERE family_id=? AND created_at>=? GROUP BY DATE(created_at)`)。
|
|
|
|
|
+- `FamilyWorkbenchService.aggregate(Long familyId) -> FamilyWorkbenchDTO`(family 不存在→throw RuntimeException("家庭不存在");6 卡:reports/plans/tasks/messages/cf/coupons,series=buildDailySeries(今天-29, 今天, mapper.daily(...));cf total=cfBalance ?? 0)。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — mock FamilyMapper+FamilyWorkbenchMapper:①family null→throw "家庭不存在";②有 family→cards.size()==6、keys 顺序含 6、cf total=cfBalance 返回、series 长度 30、totals=各 count;③conversationDailySeries 的 from=今天-29 字符串传入(ArgumentCaptor)。当前无类→FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — `mvn -q -Dtest=FamilyWorkbenchServiceImplTest test` → FAIL。
|
|
|
|
|
+- [ ] **Step 3: 实现** — 注入 `FamilyMapper`(BaseMapper<Family>,selectById)+ `FamilyWorkbenchMapper`;聚合 6 卡;family map(id/name/inviteCode/creatorId/createdAt/...仿 FamilyAdminOverviewService)。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 家庭聚合服务`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 4: AdminFamilyWorkbenchController(聚合端点 + 鉴权契约)
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `controller/admin/AdminFamilyWorkbenchController.java`
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/controller/admin/AdminWorkbenchAuthContractTest.java`(新,反射)、`test/java/com/etotem/cfc/controller/FamilyWorkbenchContractTest.java`(新,@SpringBootTest MockMvc,CI 用)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: Task 3 service。
|
|
|
|
|
+- Produces: `POST /api/admin/families/{id}/workbench` → `Result<FamilyWorkbenchDTO>`,`@PreAuthorize("hasRole(\u0027admin\u0027)")`,body 无。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — 反射契约:`AdminFamilyWorkbenchController` 每个 `@PostMapping` 方法必须带 `@PreAuthorize`(值含 `admin`)+ 路径以 `/api/admin/families/` 开头;无 → FAIL。CI 版:`post("/api/admin/families/1/workbench")` 无 token → HTTP 401;非 admin → HTTP 200 + `$.code==403`;admin → 200 + `$.data.cards.length()==6`。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — 反射测试无类→FAIL;CI 版不在此环境跑(dev 库不可达),只确保编译。
|
|
|
|
|
+- [ ] **Step 3: 实现** — controller 注入 service;方法签名 `public Result<FamilyWorkbenchDTO> workbench(@PathVariable Long id, @RequestAttribute("role") String role)`(role 参数仅为与现有风格一致,实际以 @PreAuthorize 为准);try/catch RuntimeException→Result.error。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — 反射测试 PASS;`mvn -q -Dtest=AdminWorkbenchAuthContractTest,FamilyWorkbenchServiceImplTest,FamilyWorkbenchSeriesBuilderTest test` 全绿。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 工作台聚合端点`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 5: 消息(聊天)接口
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `dto/FamilyConversationVO.java`、`dto/FamilyMessageVO.java`
|
|
|
|
|
+- Modify: `mapper/FamilyWorkbenchMapper.java`(+消息分页 @Select)、`service/FamilyWorkbenchService|Impl.java`(+pageConversations/pageConversationMessages)
|
|
|
|
|
+- Modify: `controller/admin/AdminFamilyWorkbenchController.java`(+2 端点)
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/service/FamilyWorkbenchMessageServiceTest.java`(新)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: Task 4 controller。
|
|
|
|
|
+- Produces: `POST /api/admin/families/{id}/messages` → `Result<Page<FamilyConversationVO>>`(body {page,size});`POST /api/admin/families/{id}/messages/items` → `Result<Page<FamilyMessageVO>>`(body {conversationId,page,size})。
|
|
|
|
|
+- `pageConversations(Long familyId, long page, long size)`:JOIN family_members(user_id=conversation.user_id) WHERE family_id;VO{id,title,assistantType,lastMessageAt,messageCount,lastMessagePreview}。
|
|
|
|
|
+- `pageConversationMessages(Long familyId, Long conversationId, long page, long size)`:会话必须属于该家庭(conversation.user_id 在该 family_members 中),否则 throw "会话不属于该家庭";VO{id,role,content,createdAt},content 裁剪 2000 字。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — ①pageConversations 用 mock mapper 返回会话行→VO 正确映射+preview 截断;②conversation 不属于家庭→throw;③items 翻页+content 裁剪。无方法→FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — FAIL。
|
|
|
|
|
+- [ ] **Step 3: 实现** — mapper 加 `List<Map<String,Object>> conversationsByFamily(Long familyId)`、`Long conversationMessageCount(Long convId)`、`List<Map<String,Object>> messagesOfConversation(Long convId, long offset, long size)`、`Boolean conversationInFamily(Long convId, Long familyId)`(`SELECT COUNT(*) FROM chat_conversations c JOIN family_members fm ON fm.user_id=c.user_id WHERE c.id=? AND fm.family_id=?`)。service 组装 + 校验。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS;反射契约测试同步加 2 方法断言(@PreAuthorize admin)。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 家庭聊天列表接口`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 6: 报告手动新增
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `dto/FamilyReportCreateDTO.java`
|
|
|
|
|
+- Modify: `service/FamilyWorkbenchService|Impl.java`(+createFamilyReport)、`controller/admin/AdminFamilyWorkbenchController.java`(+端点)
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/service/FamilyWorkbenchReportCreateTest.java`(新)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: Task 4/5。
|
|
|
|
|
+- Produces: `POST /api/admin/families/{id}/reports/create` → `Result<Long>`;`FamilyReportCreateDTO{String reportType; Date reportDate; Long subjectId; String personName; Integer overallScore; Integer gutHealthScore; String remark;}`。
|
|
|
|
|
+- `createFamilyReport(Long familyId, Long adminUserId, FamilyReportCreateDTO dto) -> Long`:校验 reportType ∈ {physical_exam, gut_flora} 否则 "报告类型不合法";insert HealthReport 固定 `user_id=adminUserId, family_id=familyId, status="active"`(DTO 无 familyId 字段,杜绝注入),reportDate 默认 today;personName 落 remark 或实体 personName 字段(若存在)。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — ①非法 reportType→throw;②合法→ArgumentCaptor<HealthReport> 断言 user_id=adminUserId、family_id=familyId、status=active、reportType/reportDate 来自 DTO;③reportDate null→默认当天。无方法→FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — FAIL。
|
|
|
|
|
+- [ ] **Step 3: 实现** — service 用 `HealthReportMapper.insert`(BaseMapper<HealthReport> 注入);校验白名单。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS;反射契约测试加 1 断言。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 报告手动新增`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 7: 任务新增/编辑(admin 写)
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `dto/FamilyTaskCreateDTO.java`、`controller/admin/AdminFamilyTaskController.java`
|
|
|
|
|
+- Modify: `service/TaskService.java`、`service/impl/TaskServiceImpl.java`
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/service/FamilyWorkbenchTaskWriteTest.java`(新)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: Task 4。
|
|
|
|
|
+- Produces: `POST /api/admin/families/{id}/tasks/create` → `Result<Long>`;`POST /api/admin/families/{id}/tasks/update`(body{taskId,...})→ `Result<Boolean>`;`FamilyTaskCreateDTO{title,description,category,points,duration,taskType,frequency,maxFrequency,needReview,reviewType,completeTypes,executorType,executorId,memberId,repeatType,deadline}`。
|
|
|
|
|
+- `TaskService.createAdminFamilyTask(Long familyId, Long adminUserId, FamilyTaskCreateDTO dto) -> Long`(family_id 固定=familyId,creator_id=adminUserId,status 默认 "pending"(沿用常量),sourceType="admin")。
|
|
|
|
|
+- `TaskService.updateAdminFamilyTask(Long taskId, Long familyId, FamilyTaskCreateDTO dto) -> boolean`:task 存在 + `task.familyId == familyId`,否则 throw "任务不属于该家庭";应用可编辑字段。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — ①create:captor 断言 family_id=URL、creator_id=adminUserId、title/points 来自 DTO;②update 不匹配 family→throw;③update 匹配→字段更新+true。无方法→FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — FAIL。
|
|
|
|
|
+- [ ] **Step 3: 实现** — TaskServiceImpl 注入 TaskMapper(BaseMapper<Task>);create 仿 createSingleTask 但 pin family/creator/status;update selectById+updateById。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS;反射契约测试加 2 断言(新 controller 全 @PreAuthorize admin + /api/admin/families/ 前缀)。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 任务新增/编辑`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 8: 方案新增/编辑
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `dto/FamilyPlanCreateDTO.java`
|
|
|
|
|
+- Modify: `service/HealthPlanService.java`、`service/impl/HealthPlanServiceImpl.java`、`controller/admin/AdminHealthPlanController.java`(+2 方法)
|
|
|
|
|
+- Test: `test/java/com/etotem/cfc/service/FamilyWorkbenchPlanWriteTest.java`(新)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: Task 4。
|
|
|
|
|
+- Produces: `POST /api/admin/families/{id}/plans/create` → `Result<Long>`;`POST /api/admin/families/{id}/plans/update`(body{planId,...})→ `Result<Boolean>`;`FamilyPlanCreateDTO{planType,memberName,memberIds,dimensions,goal,planContent,planJson,totalDays,teacherId,status}`。
|
|
|
|
|
+- `HealthPlanService.createFamilyPlan(Long familyId, Long adminUserId, FamilyPlanCreateDTO dto) -> Long`(pin family_id;status 默认 "active";created/updated now)。
|
|
|
|
|
+- `HealthPlanService.updateFamilyPlan(Long planId, Long familyId, FamilyPlanCreateDTO dto) -> boolean`:plan 存在 + familyId 匹配,否则 throw "方案不属于该家庭"。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — ①create pin family_id;②update 不匹配→throw;③update 匹配→字段更新。无方法→FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — FAIL。
|
|
|
|
|
+- [ ] **Step 3: 实现** — HealthPlanServiceImpl 注入 HealthPlanMapper;create 构造 HealthPlan;update selectById+updateById 白名单字段。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS;反射契约测试加 2 断言。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(workbench): 方案新增/编辑`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 9: 前端 api + 工作台页面 + 路由 + 入口
|
|
|
|
|
+
|
|
|
|
|
+**Files:**
|
|
|
|
|
+- Create: `cfc-web/src/api/familyWorkbench.js`、`cfc-web/src/views/FamilyWorkbench.vue`
|
|
|
|
|
+- Modify: `cfc-web/src/router/index.js`(families 路由后加 `families/:id/workbench`,meta{title:"家庭工作台", perm:"family:list"})、`cfc-web/src/views/Families.vue`(操作列加「进入工作台」按钮)
|
|
|
|
|
+- Test: `cfc-web/tests/unit/FamilyWorkbench.spec.js`(若 Jest 体系存在;否则仅构建验证)
|
|
|
|
|
+
|
|
|
|
|
+**Interfaces:**
|
|
|
|
|
+- Consumes: Task 4-8 端点。
|
|
|
|
|
+- Produces: api 函数 `getFamilyWorkbench(id)`、`getFamilyMessages(id, params)`、`getConversationMessages(id, convId, params)`、`createFamilyReport(id, data)`、`createFamilyTask(id, data)`、`updateFamilyTask(id, data)`、`createFamilyPlan(id, data)`、`updateFamilyPlan(id, data)`(均 request post,url `/api/admin/families/${id}/...`)。
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 写失败测试** — FamilyWorkbench.vue:mock api 返回 {cards:[6 卡]} → 渲染 6 张卡片;点击任务卡 → 打开任务列表 drawer。当前无组件→FAIL。
|
|
|
|
|
+- [ ] **Step 2: 跑测试确认失败** — `npm test -- FamilyWorkbench`(或对应 Jest 命令)→ FAIL。
|
|
|
|
|
+- [ ] **Step 3: 实现** — 组件:family 头 + el-row/el-col 6 卡(echarts init/dispose per Dashboard),点卡开 drawer(任务/方案/报告列表+新增/编辑表单;消息只读会话→消息时间线;券卡跳 `/admin/family-coupon?familyId=`);api/familyWorkbench.js;路由;Families.vue 入口按钮。
|
|
|
|
|
+- [ ] **Step 4: 跑测试通过** — PASS(或构建 `npm run build` 通过作为替代)。
|
|
|
|
|
+- [ ] **Step 5: 提交** — `feat(web): 单家庭工作台页面`。
|
|
|
|
|
+
|
|
|
|
|
+### Task 10: 整体验证 + 分支收尾
|
|
|
|
|
+
|
|
|
|
|
+**Files:** 无(验证动作)
|
|
|
|
|
+
|
|
|
|
|
+- [ ] **Step 1: 后端全量测试** — `cd cfc-backend && mvn clean package -Dmaven.test.skip=false -Dmaven.compile.fork=true` → BUILD SUCCESS(含新测试全绿)。
|
|
|
|
|
+- [ ] **Step 2: 前端构建** — `cd cfc-web && npm run build` → 成功(bump 版本号产物按惯例处理:冲突取远程版本号)。
|
|
|
|
|
+- [ ] **Step 3: 检查未提交改动** — `git status`;提交构建产物(如有)+ `git log --oneline origin/cfclub..HEAD` 汇总。
|
|
|
|
|
+- [ ] **Step 4: 推送分支** — `git push -u origin feature/family-workbench`。
|
|
|
|
|
+- [ ] **Step 5: 部署决策** — 本轮**不自动部署**;向用户报告并等待「部署最新版」指令或显式批准(部署流程:备份→构建→部署→验证→推送,红线)。
|