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 天内回复