Add TypeScript compiler validation tests for GrowthTrendChart

[atul-upadhyay-7]

Description

The GrowthTrendChart component in components/dashboard/GrowthTrendChart.tsx had no type-level test coverage. Its props interface (GrowthTrendChartProps with activityA, activityB, labelA, labelB) and the nested ActivityItem shape were untested against TypeScript compiler validation or runtime schema constraints, making it possible for type regressions to slip through during API or prop changes.

No test file existed for the component at components/dashboard/GrowthTrendChart.type-compiler.test.tsx. The component defines a non-exported GrowthTrendChartProps interface and relies on structural typing. Without dedicated type-compiler tests, there was no automated guard ensuring the stability of these type constraints.

Fixes #2552

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.

What changed

• Created components/dashboard/GrowthTrendChart.type-compiler.test.tsx with 5 test cases:
  • Case 1: Baseline type assertion for each prop field (string, number, array shapes)
  • Case 2: Static compile-time blocking of invalid ActivityItem shapes (wrong types, extra optional fields)
  • Case 3: Structural compatibility check for minimal and extended props objects
  • Case 4: Zod schema rejection of out-of-bounds activity data with flattened error reporting
  • Case 5: Valid payload parsing with type-level integrity verification

How to verify

git fetch origin
git checkout test/growth-trend-chart-type-compiler
npm run test -- components/dashboard/GrowthTrendChart.type-compiler.test.tsx

All 5 tests should pass.

[github-actions]

👋 Hey @atul-upadhyay-7, it looks like you didn't use our PR template!

The section ## Description is missing from your PR description.

Please update your PR description to include all required sections so we can review this properly:

• ## Description — What does this PR do? Which issue does it fix?
• ## Pillar — Which contribution pillar does this fall under?
• ## Checklist — Have you ticked off the quality checklist?

You can find the full template in CONTRIBUTING.md. Just edit your PR description and the needs-details label will be removed automatically. 🙌

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new type-compiler oriented test suite for GrowthTrendChart to validate prop typing expectations and Zod schema behavior for activity data.

Changes:

• Introduces Vitest expectTypeOf checks for GrowthTrendChart prop and item structural typing.
• Adds Zod .strict() runtime validation tests covering invalid and valid activity records.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[atul-upadhyay-7]

@Aamod007 could you review this

[Aamod007]

LGTM! The type validation and zod schema checks are rigorous.