Replace hardcoded "Repository Views" stat in maintainers DashboardTab with real data or removal

[Jagadeeshftw]

📌 Description

DashboardTab (src/features/maintainers/components/dashboard/DashboardTab.tsx) renders a "Repository Views" stat hardcoded to 0 with a -100% change, and silently keeps showing skeletons when the stats API errors.

💡 Why it matters: A fake -100% stat and a stuck skeleton mislead maintainers about their repo health.

🧩 Requirements and context

• Wire "Repository Views" to real data, or remove the card until the metric exists.
• Replace the silent-skeleton-on-error behavior with an error state plus retry.
• Add an empty/CTA state when no project is selected.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b fix/dashboardtab-stats

2. Implement changes

• Write/modify the relevant source: src/features/maintainers/components/dashboard/DashboardTab.tsx
• Write comprehensive tests: src/features/maintainers/components/dashboard/DashboardTab.test.tsx
• Add documentation: inline TSDoc
• Include TSDoc doc comments
• Validate security assumptions: validate stat values

3. Test and commit

• Run tests:

npm run test

• Cover edge cases: stats error, no project selected
• Include test output and security notes in the PR description.

Example commit message

fix(maintainers): real repository-views stat + error state

✅ Acceptance criteria

• No hardcoded 0 / -100% stat
• Error state with retry replaces stuck skeleton
• Empty/no-project state present
• Tests cover error + empty

🔒 Security notes

Validate numeric stats before display.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[444notdotun]

Hi,

With 4 years of hands-on experience across backend, frontend, and smart contract development, I'm confident I can complete this task quickly and to a high standard. I've reviewed the requirements in detail and fully understand what's needed.

My focus is on writing clean, efficient, and maintainable code backed by thorough testing and industry best practices. I'll ensure the solution is production-ready and delivered on time.

I expect to have my PR ready in less than 10 hours.

[444notdotun]

Hi,

With 4 years of hands-on experience across backend, frontend, and smart contract development, I'm confident I can complete this task quickly and to a high standard. I've reviewed the requirements in detail and fully understand what's needed.

My focus is on writing clean, efficient, and maintainable code backed by thorough testing and industry best practices. I'll ensure the solution is production-ready and delivered on time.

I expect to have my PR ready in less than 10 hours.

[444notdotun]

Hi,

With 4 years of hands-on experience across backend, frontend, and smart contract development, I'm confident I can complete this task quickly and to a high standard. I've reviewed the requirements in detail and fully understand what's needed.

My focus is on writing clean, efficient, and maintainable code backed by thorough testing and industry best practices. I'll ensure the solution is production-ready and delivered on time.

I expect to have my PR ready in less than 10 hours.

[leocagli]

This is right up my alley — please assign me!