Show problem difficulty in past attempt labels
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
Motivation
Candidates reviewing Past attempts can see the date and time, problem title, programming language, and verdict, but each row does not show the problem difficulty. Displaying the saved difficulty beside the title would help candidates distinguish attempts across difficulty levels without changing the existing filter.
Initial analysis
Source inspection at revision 6972a92 shows that saveHistory() in web/interview.js already saves difficulty, and normalizeProgressEntry() in web/progress.js preserves recognized values. However, renderAttemptHistory() in web/app.js does not include difficulty in the row label. This proposal concerns individual attempt labels.
Proposed change and validation
I propose displaying the saved Easy, Medium, or Hard value beside the problem title, with "Difficulty not recorded" for entries whose difficulty is missing or unrecognized. The change would use existing history data without changing storage, filtering, sorting, report contents, or retry behavior.
I will extend tests/browser/lobby.test.js to cover account and device history, including missing and invalid difficulty values, confirm that the regression checks fail before the change, and run ./scripts/test.sh with any skipped checks reported.
I will work on this change and its regression tests. Please assign this issue to me.
- Dominant language
- Rust
- Stars
- 160
- Forks
- 64
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 132
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sysprog21/codetrial
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Add a Copy code button to the final reportPossibly taken @yansawu claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
sysprog21/codetrial#318 · 5 comments · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
Add keyboard undo and redo to whiteboard interviewsPossibly taken @xuntla claimed this 1 day ago. Open
sysprog21/codetrial#352 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Let the candidate restore the starter codePossibly taken @RWong04 claimed this 1 day ago. Open
sysprog21/codetrial#348 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Run the live interviewer on a local speech pipelinePossibly taken @alanhc claimed this 2 days ago. Open
sysprog21/codetrial#330 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in sysprog21/codetrial
Similar issues
-
BASEPRI needs an ISBOpen
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
rust-embedded/cortex-m#702 · 1 comment ·
-
Make major, minor, and makedev safe on solarish targetsPossibly taken @xtqqczze claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
improvement/feedback improvement/workflow-project
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
higress-group/HiRoute#166 ·
Maintainers usually reply within 1 day
-
Proxy ignores l5d-retry-http and l5d-retry-grpc conditions that follow a comma and spacePossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 3 days
-
sncast panics when decoding a `u384` valuePossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
foundry-rs/starknet-foundry#4635 ·
Maintainers usually reply within 3 days