🧹 [code health improvement] Use logger instead of console.warn in useThemeColor.ts

[is0692vs]

🎯 What: Replaced direct console.warn usage with the application's centralized logger.warn in src/hooks/useThemeColor.ts. Updated corresponding unit tests in src/hooks/__tests__/useThemeColor.test.ts to spy on logger.warn instead of console.warn.
💡 Why: Using a centralized logger improves consistency across the codebase and makes it easier to eventually integrate external logging services (like Sentry or Axiom) without modifying individual components or hooks.
✅ Verification: Ran formatting (npm run format), linting (npm run lint), and the full test suite (npm run test). Verified all tests in useThemeColor.test.ts pass and no regressions were introduced.
✨ Result: Improved maintainability and consistency by adopting the centralized logging pattern, with tests successfully updated and passing.

---

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

Greptile Summary

このPRは src/hooks/useThemeColor.ts における console.warn の直接呼び出しを、アプリケーション共通の logger.warn に置き換えるリファクタリングです。対応するテストファイルも logger オブジェクトへのスパイに更新されています。

• useThemeColor.ts の .catch ブロックで console.warn を logger.warn に変更し、@/lib/logger をインポート追加
• useThemeColor.test.ts で vi.spyOn(console, "warn") を vi.spyOn(logger, "warn") に置き換え、ロガーの呼び出し検証も更新

Confidence Score: 5/5

変更は安全にマージ可能です。console.warn を共通 logger.warn に置き換えるだけの1行変更で、動作に影響はありません。

logger はシングルトンのオブジェクトエクスポートであるため、テストで vi.spyOn(logger, "warn") が正しく機能します。フックとテストが同じモジュールキャッシュ上の logger オブジェクトを参照するため、スパイは意図通りに動作します。afterEach で vi.restoreAllMocks() が呼ばれており、スパイのクリーンアップも適切です。

特に注意が必要なファイルはありません。

Important Files Changed

Filename	Overview
src/hooks/useThemeColor.ts	console.warn を logger.warn に置き換え、@/lib/logger のインポートを追加。変更は1行のみで影響範囲は最小限
src/hooks/tests/useThemeColor.test.ts	vi.spyOn(console, "warn") を vi.spyOn(logger, "warn") に更新。logger はシングルトンオブジェクトのため、フックと同じ参照を共有しておりスパイが正しく機能する

Sequence Diagram

sequenceDiagram
    participant Hook as useThemeColor.ts
    participant Logger as logger (lib/logger.ts)
    participant Console as console

    Hook->>Logger: logger.warn("Failed to extract color...", e)
    Logger->>Console: console.warn(message, ...args)

Loading

_{Reviews (1): Last reviewed commit: "Refactor useThemeColor.ts to use custom ..." | 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		Jun 12, 2026 6:55am

[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, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 4 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e76243b6-1f94-42f3-beba-df23e1accaeb

📥 Commits

Reviewing files that changed from the base of the PR and between a475ecb and 422a482.

📒 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 jules-5592110124318949272-8ce03ced

---

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

[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. The reviewer suggests adding an explicit return type to the mock implementation of logger.warn in the tests to maintain type safety.

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]

To maintain type safety and adhere to the repository's TypeScript guidelines, please provide an explicit return type for 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!