spikerj/spikersoft-issues
1
0 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases Wiki Activity

[Enhancement] Playground: show historical graded output when revisiting completed lessons #21

New Issue
Closed
opened 2026-04-28 22:41:46 +00:00 by spikerj · 1 comment
spikerj commented 2026-04-28 22:41:46 +00:00
Owner
Copy link
Copy source

Summary

Related to clearing the output pane on lesson change ([Bug] behavior). For lessons already completed, users should be able to review the graded output (e.g. test run that certified a pass) when they navigate back to that lesson.

Scenario

If the user has completed lessons 100, 101, and 102 and uses Back (or lesson picker) to open lesson 100 again, the output pane should show the results of the test run that ran when they passed (or their last successful graded submission), not empty UI and not another lesson’s output.

Relationship to bug fix

  • Default / in-progress lesson: hide or clear the pane until the next submit for the current lesson (no cross-lesson leakage).
  • Revisit completed lesson: populate the pane from stored historical submission/grade data for that lesson id, if available.

Possible implementation notes

  • Persist last graded result (or pass certification run) per lesson + user; load when route targets a completed lesson.
  • UX: optional “Submitted answer / Grading history” affordance if full automation is deferred.
## Summary Related to clearing the output pane on lesson change ([Bug] behavior). For **lessons already completed**, users should be able to **review the graded output** (e.g. test run that certified a pass) when they **navigate back** to that lesson. ## Scenario If the user has completed lessons **100, 101, and 102** and uses **Back** (or lesson picker) to open **lesson 100** again, the output pane should show the **results of the test run that ran when they passed** (or their last successful graded submission), not empty UI and not another lesson’s output. ## Relationship to bug fix - **Default / in-progress lesson:** hide or clear the pane until the next **submit** for the **current** lesson (no cross-lesson leakage). - **Revisit completed lesson:** populate the pane from **stored historical submission/grade data** for that lesson id, if available. ## Possible implementation notes - Persist last graded result (or pass certification run) per lesson + user; load when route targets a completed lesson. - UX: optional “Submitted answer / Grading history” affordance if full automation is deferred.
spikerj commented 2026-08-07 13:52:10 +00:00
Author
Owner
Copy link
Copy source

Migrated as part of the umbrella-tracker breakup.

This ticket needed changes in more than one repo, so it became one issue per repo:

Verified 2026-08-07 against spikersoft-backend@98102023 and spikersoft-angular@8e5a4048: UserLessonProgress.lastTestResults is written (UserLessonProgressService.cs:121) but has zero read sites and no endpoint exposes it; the SPA has no grading-history code at all.

Status: not started — the underlying snapshot is already persisted server-side, which shortens the backend half considerably.

Closing here. Work now lives in the repo that holds the fix, so fixes #<N> in a PR will
auto-close it on merge. The umbrella tracker keeps cross-repo epics only.

— Opus 5 Agent

Migrated as part of the umbrella-tracker breakup. This ticket needed changes in more than one repo, so it became one issue per repo: - Backend: spikerj/spikersoft-backend#577 - Angular: spikerj/spikersoft-angular#690 Verified 2026-08-07 against `spikersoft-backend@98102023` and `spikersoft-angular@8e5a4048`: `UserLessonProgress.lastTestResults` is written (`UserLessonProgressService.cs:121`) but has zero read sites and no endpoint exposes it; the SPA has no grading-history code at all. Status: not started — the underlying snapshot is already persisted server-side, which shortens the backend half considerably. Closing here. Work now lives in the repo that holds the fix, so `fixes #<N>` in a PR will auto-close it on merge. The umbrella tracker keeps cross-repo epics only. — Opus 5 Agent
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 epic
Cross-repo epic — children live in per-repo trackers
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#21