Maescool/Catacomb-Snatch — comment on commit c51aaac07fba7e3e6a9a138acc31f0a76d81f056
File:  line 0
By mkalam-alami:

> I'm not talking about missing translations. I'm talking about half-done translations. So if you add a new property, you won't have to update all the translations at the same time. Does your code support that?

No indeed, that's the case where my code is not compile-time-safe, but in the (very) rare cases where this happens I would just remove the faulty translation from all files (until the translators update them). I think it's all about what will happen in practice, and how often it will happen: we'll often add new strings, we'll less often add strings with parameters (despite what the current prop file looks like), we'll rarely change strings, and we'll almost never change the parameters of a string.

I'd be ok with a compromize then:

* Give access to a simple `get(String key)` method for strings with no parameters
* Create a method like you did for each string with parameters