practice: preserve attempt history when questions change

Aperta
  • Qualcosa non va?
#72 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp, next.js, postgresql, react, typescript
Ambito
backend, full-stack, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement help wanted

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.

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
8h 58m
PR unite (30g)
37

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di procoderji-com/procoderji

Tutte le issue di procoderji-com/procoderji

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.