No localized strings now when setting language to 'ja-HIRA'
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 641
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 57
Description
It seems that something isn't fully connected with the addition of "ja-HIRA". Not seeing any strings at all in the response payload when ja-hira is selected. The response should at least have the default preload of "ja":
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 reproducing the response when the language is set to ja-hira, then trace the localization path that selects the language and its preload strings. Done means the response includes the default preload strings from ja when ja-HIRA is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- localization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100