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

Players outside the top 30 never find out how they did

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

I maintainer di solito rispondono entro 1 giorno

@chetna123-ch ci sta già lavorando.

Dal 19/10/2026.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
react, typescript
Ambito
frontend

Direzione di ricerca

Start in apps/frontend/src/screens/LiveQuiz.tsx: the mid-quiz list is cut by leaderboard.slice(0, 30) near line 556, and the final screen builds others from sortedLeaderboard.slice(3). Find where the client's participantId is available and how the rank could be computed from the full sorted list before slicing. Done when the participant's own score and rank always show on the final screen, the UI states when the list is truncated, and a participant inside the visible range has their row visually distinguished.

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

Descrizione

enhancement good first issue help wanted UI & UX

The mid-quiz leaderboard renders leaderboard.slice(0, 30)
(apps/frontend/src/screens/LiveQuiz.tsx:556). The final screen shows a podium
of 3 plus others, which is sortedLeaderboard.slice(3) — unbounded, but in
practice the earlier cap means the client may only ever hold a truncated list.

Two problems follow:

Nothing indicates the list was cut. A quiz with 200 players shows 30 rows and
stops. There is no "showing top 30 of 200", so the other 170 cannot tell whether
they were excluded or the app failed.

A player cannot find themselves. If you placed 47th, you finish the quiz
without ever seeing your score or rank. You answered every question and the app
never tells you how you did — which is the whole point of playing.

This matters because Rexial is built for classrooms and events, exactly the
setting where sessions exceed 30 people. The architecture notes mention 300 per
session as a design target.

Suggested fix:

  • Always show the current participant's own row, pinned, with their real rank —
    even when they fall outside the visible slice ("You: #47 · 320 pts")
  • Say how many are not shown, and ideally make the list scrollable or paginated
  • Highlight the participant's own row when they are in the visible range, so
    they can spot themselves without reading every name

The client knows its own participantId, so finding the row is straightforward.
Note the rank must come from the full sorted list, not from the sliced one.

Definition of done:

  • A participant always sees their own score and rank on the final screen
  • The UI states when the list is truncated
  • A participant inside the top 30 has their row visually distinguished

Good issue for someone who wants a UX-shaped problem rather than a pure bug fix.

Lingua principale
TypeScript
Stelle
21
Fork
7
Merge medio
5h 19m
PR unite (30g)
29

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 TheCodeHeist-Coder/Rexial

Tutte le issue di TheCodeHeist-Coder/Rexial

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.