🧹 Refactor useThemeColor to use custom logger

[is0692vs]

🎯 What: Replaced the native console.warn call with the custom logger.warn in src/hooks/useThemeColor.ts, and updated the respective unit tests in src/hooks/__tests__/useThemeColor.test.ts to mock and assert against the new logger import.
💡 Why: To improve codebase consistency and ensure all application logs flow through the centralized logger utility, which makes future logging enhancements (e.g., shipping logs to external services) easier to implement globally.
✅ Verification: Ran the specific unit test suite (npm run test -- src/hooks/__tests__/useThemeColor.test.ts) and the full test suite (npm run test) to ensure tests continue to pass and no regressions were introduced.
✨ Result: The useThemeColor hook now consistently uses the centralized logger for error reporting.

---

PR created automatically by Jules for task 8508368564898338069 started by @is0692vs

Greptile Summary

This PR moves theme-color warning output through the shared logger.

• useThemeColor now imports logger and calls logger.warn on avatar color extraction errors.
• The hook test now spies on logger.warn instead of console.warn.
• The error-path assertion still checks that the original error object is logged.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• The logger wrapper forwards warning arguments to console.warn without changing the fallback behavior.
• The updated test spies on the same logger object used by the hook.

Important Files Changed

Filename	Overview
src/hooks/useThemeColor.ts	Replaces the catch-path console.warn call with logger.warn while preserving the same message and error argument.
src/hooks/tests/useThemeColor.test.ts	Updates the warning spy and assertion to target the shared logger used by the hook.

_{Reviews (1): Last reviewed commit: "Refactor useThemeColor to use custom log..." | Re-trigger Greptile}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ignored		Jul 17, 2026 6:39am

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

@is0692vs, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 190365be-f433-4ab8-8ab0-5be9684a457b

📥 Commits

Reviewing files that changed from the base of the PR and between 0a9a1e0 and 9296d36.

📒 Files selected for processing (2)

• src/hooks/__tests__/useThemeColor.test.ts
• src/hooks/useThemeColor.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor-use-theme-color-logger-8508368564898338069

---

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.}

[gemini-code-assist]

Code Review

This pull request replaces standard console.warn calls with a custom logger.warn utility in both the useThemeColor hook and its corresponding test suite. Feedback on the changes suggests adding an explicit ": void" return type to the mock implementation of logger.warn in the test file to maintain type safety and readability.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

According to the repository's general rules, mock implementations in TypeScript should have explicit return types to maintain type safety and readability. Please add an explicit : void return type to the mock implementation.

Suggested change

	vi.spyOn(logger, "warn").mockImplementation(() => {});
	vi.spyOn(logger, "warn").mockImplementation((): void => {});

References

1. In TypeScript, ensure functions and mock implementations have explicit return types and use async functions for mocks returning Promises to maintain type safety and readability.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[is0692vs]

Duplicate of #485 for the same useThemeColor logger migration; retaining the clean 5/5 variant #485.