i18n: extract strings — activity & mappings
Open
Beginner friendly
Nobody has claimed this yet.
internationalization
- Dominant language
- Go
- Stars
- 432
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Part of the frontend internationalization effort (see Epic). Depends on the infra issue.
Files
src/frontend/src/components/activity/ActivityView.tsxsrc/frontend/src/components/mappings/MappingsView.tsx
Notes
- These have count-driven text — implement i18next pluralization rather than string concatenation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/frontend/src/components/activity/ActivityView.tsx and src/frontend/src/components/mappings/MappingsView.tsx, then review the linked frontend internationalization epic and infrastructure dependency. Extract the activity and mappings strings and use i18next pluralization for count-driven text rather than concatenation; done when both views use localized strings with correct count forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, internationalization
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100