Update auto-generated l10n ids
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 233
- Forks
- 61
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
In https://github.com/mdn/fred/pull/452 we added auto-generated ids to all inline strings. Some of these are fine, some of these could be better.
It probably makes most sense to go component-by-component updating them.
If we implement https://github.com/mdn/fred/issues/1363, there needs to be no rush here, and we can simply update components as we get to them, or when we receive feedback from localisers on them.
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 by reviewing PR 452 to understand the generated l10n IDs and issue 1363 to see whether the proposed approach changes this work. Then choose a component whose IDs need improvement; the work is done when that component's IDs have been updated and verified against its inline strings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- localization
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100