Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

A host cannot see who won a quiz they already hosted

オープン
  • 何か問題がありますか？
#200 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
58/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
postgresql, react, typescript
領域
backend, databases, frontend, full-stack

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

enhancement good first issue help wanted UI & UX

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.

主要言語
TypeScript
スター
21
フォーク
7
平均マージ
4時間 31分
マージ済み PR（30日）
22

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

TheCodeHeist-Coder/Rexial のほかの issue

TheCodeHeist-Coder/Rexial の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。