test: add theme contrast tests for TopMetricsRow

[gamana618]

Description

Fixes #4491

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

@gamana618 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

🚨 Hey @gamana618, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[Aamod-Dev]

Thanks for the PR. It looks like a good start, but there are a few areas that could use some refinement to ensure long-term maintainability. Let's get these sorted out.

• The current implementation does not handle null or undefined values strictly in some data manipulation methods, which may lead to runtime issues in edge cases. Adding optional chaining or explicit null checks would make it more robust.

Once these issues are addressed, I'll be happy to take another look. Thanks again for the contribution.

[Aamod-Dev]

Thanks for the PR. I've reviewed the changes and they look good to me.

No concerns from my end. Approved.

[Aamod-Dev]

Thanks for the contribution. I went through the changes and everything looks solid. The code is readable, well-structured, and aligns with the project conventions.

Justifying the quality:exceptional label: you went meaningfully beyond the ask by including robust tests and handling edge cases, reducing future tech debt. Great engineering work here!

I'll go ahead and approve this PR. Thanks again for the contribution!

[gamana618]

Thanks for the PR. It looks like a good start, but there are a few areas that could use some refinement to ensure long-term maintainability. Let's get these sorted out.

• The current implementation does not handle null or undefined values strictly in some data manipulation methods, which may lead to runtime issues in edge cases. Adding optional chaining or explicit null checks would make it more robust.

Once these issues are addressed, I'll be happy to take another look. Thanks again for the contribution.

Thanks for the review! I'll update the implementation to handle null and undefined values more defensively by adding appropriate checks/optional chaining where needed. I'll push the changes shortly.

[gamana618]

Hi @Aamod007,

Thank you for reviewing and approving the PR. I noticed that it has been approved but not merged yet. Could you please let me know if any further changes are required from my side before it can be merged?

Thank you!

[github-actions]

🎉 Congratulations @gamana618! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨