bug: show the signed-in user display name in the navbar
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- nextjs, react, typescript
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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
- Open https://procoderji.com/ and sign in with Google.
- Look at the user menu on the right of the navbar.
- 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.
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 1
- 平均合併
- 8 小時 58 分鐘
- 30 天內合併 PR
- 37
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
難度 2/5 1-3 小時 新手友好度 62/100
procoderji-com/procoderji#104 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100
procoderji-com/procoderji#36 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 85/100
procoderji-com/procoderji#35 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 79/100
procoderji-com/procoderji#34 ·
維護者通常 1 天內回覆
-
enhancement good first issue
難度 1/5 1-3 小時 新手友好度 90/100
procoderji-com/procoderji#33 ·
維護者通常 1 天內回覆
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
bug platform-android
難度 2/5 1-3 小時 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 則留言 ·
維護者通常 2 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
難度 1/5 1 小時以內 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆