Changed light mode icon because it was misleading

[dhirukumar]

Description

This PR updates the Light Mode toggle icon in the UI.

What Was Changed

Replaced the old sun/gear-style icon (which looked like a settings icon):
Added the new light bulb icon (more intuitive for Light Mode):

before

After

🧠 Why This Change

The previous icon was visually misleading and confused users as it closely resembled the settings icon.
The new icon provides clearer UX and better represents Light Mode functionality.

🧪 Testing

Verified UI behavior in both Light and Dark modes
Ensured toggle works with no functional regressions

📝 Checklist

I've read and followed the contributing guidelines
I've run make check-test locally; all checks and tests passed.

Issue:-#2713

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary by CodeRabbit

• Style
  • Updated the dark mode toggle icon to a lightbulb symbol for enhanced visual representation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

Updates the ModeToggle component to replace the Sun icon with a Lightbulb icon in the dark mode state. Modifies the import statement to include the new icon from the Font Awesome library while maintaining existing functionality.

Changes

Cohort / File(s)	Summary
Theme Toggle Icon Update frontend/src/components/ModeToggle.tsx	Replaces faSun icon with faLightbulb for dark-mode state; updates import to include faLightbulb; light-mode icon (faMoon) unchanged

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Simple icon replacement with minimal logic impact; primarily a cosmetic update to the ModeToggle component

Possibly related issues

• Light Mode Icon Is Misleading and Confusing #2713: Directly addresses theme toggle icon modifications in the same component, replacing misleading icon representations with clearer ones (lightbulb/sun pattern).

Possibly related PRs

• fix: dark mode toggle logic #1155: Also modifies frontend/src/components/ModeToggle.tsx and alters the dark-mode icon display, suggesting concurrent or related theme toggle refactoring work.

Suggested labels

frontend

Suggested reviewers

• arkid15r
• kasya

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1b39db3 and f81dbd6.

📒 Files selected for processing (1)

• frontend/src/components/ModeToggle.tsx (2 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Tip

✨ Issue Enrichment is now available!

CodeRabbit can now help you manage issues more effectively:

• Duplicate Detection — Identify similar or duplicate issues
• Related Issues & PRs — Find relevant issues and PR's from your repository
• Suggested Assignees — Find the best person to work on the issue
• Implementation Planning — Generate detailed coding plans for engineers and agents

Enable issue planning

To enable issue planning, add the following to your .coderabbit.yaml:

issue_enrichment:
  planning:
    enabled: true

You can then request a plan by commenting @coderabbitai plan on any issue.

Disable automatic issue enrichment

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

The PR must be linked to an issue assigned to the PR author.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud