[Feature Request]: composer-lockfile style translations lockfile #37
Description
Is your feature request related to a problem?
Locking specific translation versions increases control over what translations are used and allows reproducible translation strings.
Verifying installed translations on an individual file-level also ensures the integrity of installed language files.
Describe the desired solution
It would be better if the translation download treats a translation lockfile like a composer lockfile.
The translation lockfile is then not git-ignored but rather added to the project, with the exact versions of the translation files to be downloaded and used for the project.
During translations install the translation downloader should then verify the presence of required version for each individual translation file and replace/remove translation files where this isn't the case - in the same way as composer treats its lockfiles.
Describe the alternatives that you have considered
Alternatively all translation files would have to be added to the project, but those are external dependencies. like their WordPress core/plugin/theme counterparts.
Additional context
Code of Conduct
- I agree to follow this project's Code of Conduct