practice: preserve attempt history when questions change

Offen
  • Stimmt etwas nicht?
#72 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
csharp, next.js, postgresql, react, typescript
Bereich
backend, full-stack, testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
1
Ø Merge
8 Std. 58 Min.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus procoderji-com/procoderji

Alle Issues in procoderji-com/procoderji

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.