I have mixed feelings. If someone is using the gem and there are a lot of database hits, this is slowing the loading time of the view. Once the translations are done, the values are stored in memory, and then no longer is a problem.
So I understand the desire to hide this queries that may clutter the log on development until the translations are done, but we can trick ourselves in believing that is OK to have untranslated translations, because this will hide the queries...
I am not doing this right now, but the discussion can be reopened here.
I have mixed feelings. If someone is using the gem and there are a lot of database hits, this is slowing the loading time of the view. Once the translations are done, the values are stored in memory, and then no longer is a problem.
So I understand the desire to hide this queries that may clutter the log on development until the translations are done, but we can trick ourselves in believing that is OK to have untranslated translations, because this will hide the queries...
I am not doing this right now, but the discussion can be reopened here.