You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just ran i15r on an inherited project, and it runs mostly fine. Thanks for the good work!
However, I'm not sure of why would I want to run a tool that doesn't generate any yml file.
If I don't use --no-default, I get e.g. 1000 entries like I18n.t("users.new.name", :default => 'Name'), and I still will have to manually create 1000 entries in en.yml. Even if I do that, then I'd have to manually remove (default: 'foo') from each t call, for ensuring DRY/correctness.
If I use --no-default, any app will become empty/broken until you manually create 1000 entries in en.yml.
Either option is undesirable. As I see it, this gem would be only be useful if it generates a yml file as well.
Probably overwriting en.yml would be obstrusive/error-prone. However, generating a separate yml file could allow the developer to adapt it as he wishes.
Do you think you can make this happen?
For now I will be giving it a try, in my fork.
Cheers - Victor
The text was updated successfully, but these errors were encountered:
I haven't really touched this gem for ~2 years now and I'm overwhelmed with other stuff.
I agree that creating an output yml file would make it more useful, so if you add this feature, I'll happily accept a PR and release a new gem version (if I can recall how to do that :) ).
Hi,
I just ran i15r on an inherited project, and it runs mostly fine. Thanks for the good work!
However, I'm not sure of why would I want to run a tool that doesn't generate any yml file.
--no-default
, I get e.g. 1000 entries likeI18n.t("users.new.name", :default => 'Name')
, and I still will have to manually create 1000 entries in en.yml. Even if I do that, then I'd have to manually remove (default: 'foo'
) from eacht
call, for ensuring DRY/correctness.--no-default
, any app will become empty/broken until you manually create 1000 entries in en.yml.Either option is undesirable. As I see it, this gem would be only be useful if it generates a yml file as well.
Probably overwriting en.yml would be obstrusive/error-prone. However, generating a separate yml file could allow the developer to adapt it as he wishes.
Do you think you can make this happen?
For now I will be giving it a try, in my fork.
Cheers - Victor
The text was updated successfully, but these errors were encountered: