补充权限与物资实现计划
1、记录项目权限一致性实施计划,明确前后端权限矩阵以接口权限为准。 2、列出快捷入口、参与者操作、路由权限和权限契约测试的实施任务。 3、记录物资设备详情页实施计划,覆盖路由、详情页和列表导航入口。 4、保留验证步骤与约束说明,便于后续按计划复查实现范围。
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
# Material Equipment Detail Implementation Plan
|
||||
|
||||
> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.
|
||||
|
||||
**Goal:** Add a read-only detail page for material equipment records in the material management module.
|
||||
|
||||
**Architecture:** Reuse the existing material equipment API detail endpoint and the project detail-page layout conventions. Add one route, one detail view, and one list-page navigation entry without changing create/update/delete behavior.
|
||||
|
||||
**Tech Stack:** Vue 3, Vue Router, Element Plus, Vitest static source tests.
|
||||
|
||||
---
|
||||
|
||||
### Task 1: Route And Navigation Tests
|
||||
|
||||
**Files:**
|
||||
- Modify: `frontend/src/views/detailNavigation.test.ts`
|
||||
- Modify: `frontend/src/views/detailBreadcrumbContext.test.ts`
|
||||
- Modify: `frontend/src/views/ia/MaterialEquipment.test.ts`
|
||||
|
||||
**Steps:**
|
||||
1. Add the future equipment detail view to detail-navigation expectations.
|
||||
2. Add breadcrumb expectations for equipment detail page title.
|
||||
3. Add a list-page expectation for detail navigation.
|
||||
4. Run the focused tests and confirm they fail because the route/view/link do not exist yet.
|
||||
|
||||
### Task 2: Detail Page Implementation
|
||||
|
||||
**Files:**
|
||||
- Create: `frontend/src/views/materials/MaterialEquipmentDetail.vue`
|
||||
- Modify: `frontend/src/router/index.ts`
|
||||
- Modify: `frontend/src/views/ia/MaterialEquipment.vue`
|
||||
|
||||
**Steps:**
|
||||
1. Build a read-only detail view using `getMaterialEquipment`.
|
||||
2. Set breadcrumb context using the equipment name.
|
||||
3. Register `/materials/equipment/:equipmentId`.
|
||||
4. Add the list table detail link.
|
||||
5. Run focused frontend tests and type/build verification where feasible.
|
||||
Reference in New Issue
Block a user