[BUG]: Hardcoded text color in EmptyStateCard breaks light theme readability

未关闭
#460 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@Abhishek2005-ard 已经在做这个了。

开始于 2026年11月16日。

  • #463 来自 @Abhishek2005-ard —— 未关闭

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
javascript, react

调研方向

Read src/components/EmptyStateCard.jsx at the reported color style and check how var(--text2) is defined for the light theme. The issue proposes replacing the hardcoded color with that token; verify the description text on the light theme at /repositories or with an invalid search. The issue is already linked to open pull request #463.

由索引模型根据 Issue 内容生成。

描述

bug enhancement
Bug Description
Bug Description

In src/components/EmptyStateCard.jsx, the description text color is hardcoded to #D4C58A instead of using the theme design token var(--text2). When switching to the light theme, this muted gold/yellow color provides poor contrast and breaks visual consistency against light backgrounds.

Steps to Reproduce
  1. Open OrgExplorer and switch to Light Theme via the navbar toggle.
  2. Navigate to /repositories or search for an invalid term to trigger EmptyStateCard.
  3. Observe the subtitle/description text color ("No repositories match your search...").
  4. It renders in #D4C58A rather than adapting to the light theme's secondary text color.
Location
  • File: src/components/EmptyStateCard.jsx
  • Line: 64 (color: "#D4C58A")
Proposed Solution

Replace the hardcoded inline style:

- color: "#D4C58A",
+ color: "var(--text2)",
Impact

Low - Minor inconvenience / UI contrast bug

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Steps to Reproduce

No response

Logs and Screenshots

No response

Environment Details

No response

Impact

Critical - Application is unusable

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
主要语言
JavaScript
星标
53
派生
182
平均合并
18 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AOSSIE-Org/OrgExplorer 的其他 Issue

查看 AOSSIE-Org/OrgExplorer 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。