Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Show problem difficulty in past attempt labels

Aperta
#357 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@yuen0428 ci sta già lavorando.

Dal 18/10/2026.

  • #363 di @yuen0428 — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.

Lingua principale
Rust
Stelle
177
Fork
100
Merge medio
1g 9h
PR unite (30g)
151

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 sysprog21/codetrial

Tutte le issue di sysprog21/codetrial

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.