Move loading of the translation language list from initial state to OCS API call
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
When looking at intitial state optimizations @nickvergessen suggested to move the list of languages that text provides to the frontend from the current intitial state value passing to using the OCS API endpoint and fetch it on demand.
On some AI translation provider there are just tons of mutations of languages added which adds up in size of the initial state which we only need once showing text or even the translation dialog.
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 files or tests are named. Start by locating where the language list is added to the initial state and where the OCS API endpoint is defined or consumed; then trace how the translation dialog requests languages. Done means the list is fetched on demand through the OCS API rather than included in the initial state, with the existing translation flow still receiving the available languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100