this post was submitted on 21 Aug 2023
41 points (100.0% liked)
Programming
17326 readers
192 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Perhaps, the "fallback to English translations file at runtime" is obscuring errors.
Might be worth redefining the system to throw an error when a translation key in the chosen language isn't found. Even if that's only done in Dev, whereas the fallback happens in prod.
This will ensure a translation file has all the keys, even if the values are still default.
Some tooling for you to easily add a new key, and have it also add that to all language files as
[word]
or something. So, the English word is still used, but the square brackets shows that it's untranslated.Maybe some tooling to find all values that have the
[]
, to generate a translation to-do list.Probably a tool to create a new translation file as well, which would duplicate the English file, but apply the "this is not translated" pattern to all the values
Are warnings no thing anymore?
We ignore them.
Jenkins didn't at my last job.