Investigate behavior of updating translation stats
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Right now the behavior seems incorrect. @KatieWoe pointed this out to me in her testing of https://github.com/phetsims/qa/issues/931.
I think it would be a good idea to break this problem down into smaller problems:
When does the "(pending update)" badge appear?
- If you translate a sim-specific string, does the "(pending update)" badge appear next to the sim?
- If you translate a shared string, does the "(pending update)" badge appear next to the sim and the other sims that share the string?
- If you translate a common string, do all sims that have the common string have a "(pending update)" badge?
How long does it take for the stats to update?
At this point, the only bottleneck for having perfectly up-to-date translation stats is the build server. We can get fresh sim metadata (since we bust the cache) and we can get fresh GitHub data (since we are now using Octokit).
- If you translate a sim-specific string, how long does it take for the stats to update?
- If you translate a shared string, how long does it take for the stats to update?
- If you translate a common string, how long does it take for the stats to update?
Contributor guide
No contributing guide indexed for this repository
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 reproducing the sim-specific, shared, and common-string translation scenarios described in the issue, using the behavior reported in QA issue 931 as context. Measure how long each case takes for the “pending update” badge and translation stats to change; done means the affected sims and update timing are documented and the incorrect behavior is narrowed to the relevant part of the application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- localization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100