Track translation keys

[Systho]

Is your feature request related to a problem? Please describe.

When most of the application grows, they keep legacy translation keys which are not used in the app anymore but nobody knows for sure they are not used. Looking in the codebase for the exact key won't work because sometimes we build the key programatically.
Eventually we end up with a huge translation .yml file and when trying to introduce a new language, it's very difficult to know which keys need translation and which do not. The problem is the same for any kind of global renaming of a concept.

Describe the solution you'd like
I wish that every call to I18n.t would trigger an update of the value "last usage" for the relevant key and being able to visualise which key have not been used for a long time. This use case is very similar to tracking views.

Describe alternatives you've considered

I've considered building a similar tracking on my test suite but I would need certainty that my e2e tests cover every corner of the app, which they don't.

Additional context

[danmayer]

Coverband doesn't currently support this, in theory we could add another plugin or adapter to capture it, but I am unlikely to do so any time soon.

If you wanted to make a branch that supported it I could take a look, but for a single company might be best to just start with a new gem. This old gem is out of date but is exactly what you want, a co-worker wrote this when I was at livingsocial and we used it there to clean up our translation keys.

https://github.com/livingsocial/humperdink

I believe most of the logic would still be good but the railtie and some of the methods or hooks might have changed since then. Take a look @Systho and let me know if that looks like what you want.

[juhoha]

Had the same issue a while back. A colleague made that: https://github.com/sergioisidoro/e7o

It's a similar low overhead tool you can easily plop into prod.

[danmayer]

Note the current RC release has translation key tracking....

5.2.6.rc.2 you can turn it on via the configuration file. If @juhoha or @Systho give it a good, I would love feedback from someone else running it in production.

    # enabled translation tracking
    config.track_translations = true

view of the integration: