wordpress-mobile / wordpress-mobile/release-toolkit
Idea: Add link to GlotPress when a string fails localization linting
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 31
- Forks
- 10
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 2
Description
In the context of removing friction and giving clarity to product devs running releases, it occurred to me that GlotPress validation errors can be cryptic to the non-initiated.
Example, I just run into this
[15:56:01]: Inconsistencies found between 'en' and 'ro':
`reader.navigation.filter.tag.singular` expected placeholders for [Int] but found [] instead.
I could be useful to add something like:
[15:56:01]: Inconsistencies found between 'en' and 'ro':
`reader.navigation.filter.tag.singular` expected placeholders for [Int] but found [] instead.
You can see the string in GlotPress at https://translate.wordpress.org/projects/apps/ios/dev/ro/default/?filters%5Bterm%5D=reader.navigation.filter.tag.singular . From there, either suggest a fix or reach out to the translator via the .org Slack or Matrix.
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
No file or test is named in the issue. Start by locating the Ruby release-toolkit entry point that formats GlotPress localization linting errors, then trace how the string key is available. Done means the diagnostic includes a usable GlotPress link for the failing string and existing relevant checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- localization
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100