fix: updated loading spinner colour to use the standard blue

[Klakurka]

Test plan

Open any of the pages and see the spinner loading animation is the standard blue instead of green.

Summary by CodeRabbit

• Refactor
  • Optimized the Loading component's color handling by removing unnecessary state management, improving performance and code maintainability.

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

[coderabbitai]

Walkthrough

The Loading component in components/Loading/index.tsx was refactored to remove internal state management for accent color and its associated effect. The color prop now directly uses the provided value or falls back to the CSS variable var(--accent-color).

Changes

Cohort / File(s)	Summary
Loading component simplification components/Loading/index.tsx	Removed internal accentColor state and useEffect fallback logic; simplified DotLoader color prop to use provided color or CSS variable directly; removed useState and useEffect imports

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Single-file refactoring removing state and effect hooks
• Straightforward simplification of color fallback logic
• No changes to public API signatures or exported interfaces

Possibly related PRs

• feat: main pages loading spinner #1083 — Original PR that introduced the Loading component; this PR reverses the internal state management approach in favor of CSS variable fallback.

Suggested labels

enhancement (UI/UX/feature)

Suggested reviewers

• lissavxo
• chedieck

Poem

🐰 A Loading component springs so light,
No state to weigh it down in flight,
CSS variables now take the call,
Simpler code, elegant for all! ✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. Required sections like 'Related to #' issue link and 'Description' are missing; only the 'Test plan' section is provided.	Add the missing 'Related to #' issue reference and a 'Description' section explaining why the change was made and what problem it solves.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: updating the loading spinner color to use standard blue instead of green, which matches the actual code modifications.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/loading-color

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a1a64e6 and fd9fdc5.

📒 Files selected for processing (1)

• components/Loading/index.tsx (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Run Tests

🔇 Additional comments (2)

components/Loading/index.tsx (2)

1-1: LGTM! Good simplification.

Removing unused useState and useEffect imports simplifies the component by eliminating unnecessary state management.

---

14-14: The CSS variable is properly defined and set to blue.

The --accent-color variable is defined in styles/variables.css as #669cfe (a blue color) in both light and dark modes, so the fallback in line 14 works as intended.

---

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