practice: preserve attempt history when questions change
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- csharp, next.js, postgresql, react, typescript
- 领域
- backend, full-stack, testing
调研方向
Start with the question data and progress/session files listed in the issue, then read ADR 0001 and the question-versioning step in docs/product-roadmap.md. Trace how attempts are validated, persisted, and imported or exported in both TypeScript and backend code. Done means shared fixtures and both runtimes preserve historical reviews and results through corrections, retirement, reload, sync, and reset, with the listed compatibility tests passing.
由索引模型根据 Issue 内容生成。
描述
Related to #22 and the question-versioning step in docs/product-roadmap.md.
Problem
Saved attempts contain question IDs and selected option IDs. The frontend grades them against the current question bank. Changing an answer key can change a historical result; removing an ID can cause an attempt to be discarded during validation.
Scope
- Record the question-revision and compatibility strategy in an ADR, following ADR 0001.
- Keep reviewed definitions in the canonical shared question data. Identify the exact revision used by an attempt; do not accept browser-supplied answer keys or scores.
- Keep retired revisions available for historical review while excluding them from new sessions.
- Define a compatible interpretation or migration for existing unversioned browser and backend records.
- Update TypeScript validation, backend validation, persistence and import/export contracts together. Document rollout and rollback.
- Preserve the 100-attempt limit, payload bounds, account isolation and generation-based reset behavior.
- Keep this separate from the planned game-history contract in #69.
Starting files
shared/practice/questions.json, src/features/progress/, src/features/practice/domain/session.ts, backend/src/ProCoderJi.Api/Features/Practice/PracticeQuestionBank.cs, and backend/src/ProCoderJi.Api/Features/Progress/.
Done when
Shared fixtures and both runtimes demonstrate that correcting or retiring a question preserves the original attempt's review and result. Tests cover existing unversioned records, revision mismatches, retirement, reload/export/import, cloud synchronization and reset compatibility across supported storage providers.
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 1
- 平均合并
- 8 小时 58 分钟
- 30 天内合并 PR
- 37
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
难度 2/5 1-3 小时 新手友好度 62/100
procoderji-com/procoderji#104 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
procoderji-com/procoderji#36 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 85/100
procoderji-com/procoderji#35 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 79/100
procoderji-com/procoderji#34 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 90/100
procoderji-com/procoderji#33 ·
维护者通常 1 天内回复
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug platform-android
难度 2/5 1-3 小时 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 条评论 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复