bug: show the signed-in user display name in the navbar

Offen
  • Stimmt etwas nicht?
#102 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
nextjs, react, typescript
Bereich
authentication, frontend

Rechercherichtung

Start by finding the shared navbar component and the code that reads the signed-in session, then trace why the user menu shows "My account" instead of the display name. The issue says the cause is not yet investigated and that the work is backlog, so confirm scope with maintainers before coding. Done means the acceptance criteria hold: signed-in name shown, "Guest learner" restored on sign-out, a safe fallback, and no email or token exposed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:frontend bug

What happened?

After signing in, the shared navbar labels the user menu "My account" instead of showing the signed-in student's display name. This makes the current account harder to identify.

Reported by the owner on production with a screenshot of the signed-in menu. The root cause has not been investigated.

Steps to reproduce

  1. Open https://procoderji.com/ and sign in with Google.
  2. Look at the user menu on the right of the navbar.
  3. Observe that its label is "My account" rather than the signed-in user's display name.

Expected behavior

Show the authenticated user's display name in the shared navbar. Keep "Guest learner" for signed-out visitors and use a clear fallback when a display name is unavailable.

Acceptance criteria

  • Signed-in visitors see their display name consistently across pages using the shared header.
  • Signing out restores "Guest learner"; switching accounts updates the displayed name.
  • Loading or missing-name states use a sensible fallback without showing a previous account's name.
  • Long names fit on desktop and mobile without horizontal overflow or obscuring navigation controls.
  • The existing user-menu actions, keyboard access and brand styling remain usable.
  • Use the existing authenticated session data; do not expose email addresses or tokens as the menu label.

Planning

Backlog item. Investigation and implementation will be scheduled later; no implementation or pull request is requested now.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
1
Ø Merge
8 Std. 58 Min.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus procoderji-com/procoderji

Alle Issues in procoderji-com/procoderji

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.