vr-shopxo-uniapp/plan.md

63 lines
2.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters!

This file contains ambiguous Unicode characters that may be confused with others in your current locale. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to highlight these characters.

# Council Plan — BackendReviewer
## Task
Review `vr-ticket-uniapp-supplement.md` from backend perspective: check API specs consistency with actual vr-shopxo-plugin implementation, identify missing details, and propose fixes.
## Files to Review
- `/Users/bigemon/WorkSpace/vr-shopxo-uniapp/docs/vr-ticket-uniapp-supplement.md`
- Backend code: `/Users/bigemon/WorkSpace/vr-shopxo-plugin/shopxo/app/plugins/vr_ticket/`
## Backend Review Checklist
- [ ] 1. Compare API spec (Section 2) with actual backend implementations
- [ ] 2.1 商品详情 API — seatSpecMap 返回方式
- [ ] 2.2 购物车提交 API — extension_data 传递链路
- [ ] 2.3 票夹 API — 响应字段对照
- [ ] 2. Check QR payload structure (Section 6.1)
- [ ] 3. Verify short_code format documentation
- [ ] 4. Document missing backend details:
- [ ] extension_data 在 order_detail 中的存储格式
- [ ] Auth 机制X-Token vs cookie
- [ ] 核销 API 完整响应码
- [ ] 5. Identify top 3 API gaps (must resolve before frontend dev)
## Phase Breakdown
### Phase 1: Analysis (current)
Read supplement doc + backend code, compare, identify gaps
### Phase 2: Report
Output detailed review report with:
- Document score (1-10)
- Found issues (specific)
- Key gaps (must-fix before dev)
- Improvement suggestions (actionable)
- 3 recommendations for frontend devs
### Phase 3: Finalize
Merge findings into main, coordinate with FrontendReviewer
## Status
| Task | Status |
|------|--------|
| Read supplement doc | Done |
| Analyze backend code | Done |
| Identify API gaps | Done |
| Write review report | Done |
| Merge to main | In Progress |
## Coordination
- FrontendReviewer: reviewing frontend implementation (goods-vr-ticket.vue, components)
- Need to sync on: seatSpecMap acquisition, extension_data format
## Key Findings (Top 3 API Gaps)
1. **Gap 1: seatSpecMap 返回方式P0** — 前端无法获取座位规格映射表
2. **Gap 2: CartSave extension_data 传递链路P0** — 多座位场景下 attendee 信息存储
3. **Gap 3: QR payload 结构错误P1** — 缺少 `code` 字段
## Review Report
- Document score: 7/10
- Critical issues: 5
- Must-fix before Phase 2: 2 (seatSpecMap, extension_data)