A host cannot see who won a quiz they already hosted
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 58/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- postgresql, react, typescript
- Ambito
- backend, databases, frontend, full-stack
Direzione di ricerca
Read apps/http-server/src/controllers/quizController.ts first, especially how participated quizzes are included in getAllQuizesController; then inspect apps/frontend/src/screens/Dashboard.tsx and the existing live podium ranking and styling. Add the latest completed session’s top three to the hosted quiz response in one request, using score then total answer time for ties, and show no podium if there is no completed session. Done means each completed hosted quiz card shows ranked names and scores, the empty case is hidden, and the dashboard still loads without a query per card.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
When a quiz ends, the host sees the podium on the results screen. Once they leave that page it is gone — there is no way back to it.
A few days later, going to the dashboard to check who won, the hosted-quiz card shows only this:
[COMPLETED] 24/10/2026
Science Quiz
A quiz about the solar system
5 Qs 3 Sessions
Status, date, title, description, question count, session count. No winners, no scores, no players. Clicking the card opens the quiz builder, which is for editing questions, not for looking at results.
The data is still there
Nothing deletes it. endQuizSession only marks the session COMPLETED and clears the Redis cache — Participant rows and their scores stay in Postgres. Confirmed on production: a session from 17 October still has all 751 of its participants with their scores intact.
So this is purely about surfacing what already exists.
What is missing
getAllQuizesController in apps/http-server/src/controllers/quizController.ts returns only counts for hosted quizzes:
const organizedQuizes = await prisma.quiz.findMany({
where: { quizOrganizers: { some: { userId: req.userId, inviteStatus: "ACCEPTED" } } },
include: {
_count: { select: { questions: true, quizSessions: true } }
},
orderBy: { createdAt: "desc" }
});
No participants, no scores.
What to build
Show the top 3 on each completed hosted-quiz card — name and score, in rank order, the same gold/silver/bronze treatment the live podium already uses.
Three is the right number here: a dashboard card has little room, and "who won" is the question being asked. A full leaderboard belongs on its own page if anyone wants one later.
Points to decide, and worth saying which you chose in the PR:
- A quiz can have several sessions. The card shows a session count, so it has run more than once. Pick the most recent completed session, or let the host choose — the simplest version is the latest, and say so in the UI so it is not misleading.
- A quiz with no completed session yet should show nothing rather than an empty podium.
- Ties. The live leaderboard already ranks by score and then by total answer time. Reuse that ordering rather than inventing a second one, so the dashboard agrees with what people saw on the night.
Suggested shape
Backend: include the latest completed session's top 3 in the existing dashboard response. One query for the whole list rather than one per quiz — getAllQuizesController already does something similar for participated quizzes, which is worth reading first as a model.
Frontend: a small block at the bottom of the card in apps/frontend/src/screens/Dashboard.tsx, under the Qs/Sessions row.
Definition of done
- A completed hosted quiz shows its top 3 with names and scores
- A quiz that has never been played shows no podium
- Ranking matches what the live leaderboard showed
- The dashboard still loads in one request; no query-per-card
Good first issue: the data already exists and the podium styling already exists on the results screen — this is mostly connecting the two.
- Lingua principale
- TypeScript
- Stelle
- 21
- Fork
- 7
- Merge medio
- 4h 31m
- PR unite (30g)
- 22
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TheCodeHeist-Coder/Rexial
-
bug good first issue help wanted UI & UX
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
TheCodeHeist-Coder/Rexial#205 ·
I maintainer di solito rispondono entro 1 giorno
-
One PDF upload freezes the whole AI service, including its health checkForse già presa @Anshuu2004 l’ha presa 2 giorni fa. ApertaBackend first issue bug help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
TheCodeHeist-Coder/Rexial#193 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
The join endpoint returns an error shape the frontend cannot readForse già presa @Anshuu2004 l’ha presa 2 giorni fa. ApertaBackend first issue bug good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
TheCodeHeist-Coder/Rexial#192 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Registering without a password returns a 500 instead of telling you what is missingForse già presa @Anshuu2004 l’ha presa 2 giorni fa. ApertaBackend first issue bug good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
TheCodeHeist-Coder/Rexial#191 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
CI does not run the frontend testsForse già presa @nayan45633 l’ha presa 2 giorni fa. ApertaBackend first issue good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
TheCodeHeist-Coder/Rexial#188 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TheCodeHeist-Coder/Rexial
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
awslabs/visual-asset-management-system#804 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
restatedev/sdk-typescript#813 ·
-
bug desktop P1 session XS
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
Merit-Systems/x402scan#1312 ·
-
type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Azure/apiops-cli#331 ·
I maintainer di solito rispondono entro 3 giorni