📌 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
🔒 Security notes
No security impact.
📋 Guidelines
- Minimum 95% test coverage
- Clear documentation
- Timeframe: 96 hours
📌 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
ecosystems.*namespace tosrc/shared/i18n/messages.ts.EcosystemsPage.tsx(andEcosystemDetailPage.tsxif it shares the gap) withuseTranslation()lookups.🛠️ Suggested execution
messages.tswith TSDoc comments matching the existing style.useTranslation()into both components.✅ Acceptance criteria
namespace.keyand TSDoc conventions.🔒 Security notes
No security impact.
📋 Guidelines