Closed brunobrgs closed 3 years ago
Thinking out loud: would there be any value in having experiments.XX.yml files, that would not go into OneSky but allow us to centrally manage experiment translations without bothering translators?
Great option, covers the case when experiment might be extended to second language. From recent experience, changing hardcoded default values in multiple places is not fun 😢
Thinking out loud: would there be any value in having
experiments.XX.yml
files, that would not go into OneSky but allow us to centrally manage experiment translations without bothering translators?
This seems preferable to me over the default:
approach and would also enable us to share the file with the translators for the language that we need translated for the experiment. The keys could then be moved from the experiments.en.yml
to the main translation file when the experiment was going to be rolled out.
Thinking out loud: would there be any value in having
experiments.XX.yml
files, that would not go into OneSky but allow us to centrally manage experiment translations without bothering translators?This seems preferable to me over the
default:
approach and would also enable us to share the file with the translators for the language that we need translated for the experiment. The keys could then be moved from theexperiments.en.yml
to the main translation file when the experiment was going to be rolled out.
Yeah I really like this idea as well 👍
Thinking out loud: would there be any value in having
experiments.XX.yml
files\
Nice, this sounds like a bonafide silver bullet to me 👏
Follow up: https://github.com/cookpad/global-web/pull/21917