Combine l10n js files of one language
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: language/translations (l10n/i18n)
performance 🚀
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
- currently 10% of all requests (13 out of 126 requests in the files app) are l10n files
- we should combine all l10n files of a language of all enabled apps (this doesn't change that often)
- maybe use the #3988
cc @rullzer @ChristophWurst @nickvergessen Does this sound good?
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 issue #3988 and the current localization-file request handling for the files app. Confirm how enabled apps expose language files, then define completion as serving one combined localization file per language while preserving translations and reducing the separate requests described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- localization, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100