My first observation is that in most of the apps I've worked on keys are composed by constructs such as `t :"something_#{from_the_context}"`, which I assume this tool will miss. I'd much rather see a tool that tracked i18n hits in a k/v store, and used that in addition to the static analysis.
Don't let this discourage you, your work looks great (props on the correctly tabulated output!) - but it would never work for me in what I think is a reasonable usecase :(
Such keys are supported to a certain extent (e.g they won't be reported as unused). A runtime tool that tracks runtime misses to the store is a part of ruby i18n gem and many other environments already. I have found such keys to constitute a minority in most projects I've worked on.
Comments
My first observation is that in most of the apps I've worked on keys are composed by constructs such as `t :"something_#{from_the_context}"`, which I assume this tool will miss. I'd much rather see a tool that tracked i18n hits in a k/v store, and used that in addition to the static analysis.
Don't let this discourage you, your work looks great (props on the correctly tabulated output!) - but it would never work for me in what I think is a reasonable usecase :(
Such keys are supported to a certain extent (e.g they won't be reported as unused). A runtime tool that tracks runtime misses to the store is a part of ruby i18n gem and many other environments already. I have found such keys to constitute a minority in most projects I've worked on.