Skip to content

Add i18n coverage for src/features/dashboard/pages/EcosystemsPage.tsx #461

Description

@Jagadeeshftw

📌 Description

src/features/dashboard/pages/EcosystemsPage.tsx likely still has hardcoded English strings, following the same gap pattern recently fixed for MaintainersPage. Extracting these keeps the app consistent as more locales are added.

🧩 Requirements and context

  • Add an ecosystems.* namespace to src/shared/i18n/messages.ts.
  • Replace hardcoded strings in EcosystemsPage.tsx (and EcosystemDetailPage.tsx if it shares the gap) with useTranslation() lookups.
  • Add/update tests asserting the page renders via the catalog.

🛠️ Suggested execution

  • Enumerate current hardcoded strings in both files.
  • Add corresponding keys to messages.ts with TSDoc comments matching the existing style.
  • Wire useTranslation() into both components.

✅ Acceptance criteria

  • No hardcoded user-facing strings remain in either page.
  • New keys follow the existing namespace.key and TSDoc conventions.
  • No behavior change to routing or data-loading.

🔒 Security notes

No security impact.

📋 Guidelines

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

Metadata

Metadata

Assignees

Labels

GrantFox OSSGrantFox open-source programMaybe RewardedGrantFox: potentially rewarded contributionOfficial Campaign | FWC26GrantFox official campaign issuefrontendFrontend / UI work

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions