-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't execute save on files which actually aren't changed #125
Comments
|
Does the commit above fix the issue? |
No, it doesn't seem to:
I specified the commit in the Gemfile like this:
|
By the way, when a key is added, it still seems to save all the files, but when none is added, no file is saved. Does this help?
|
How about now (be2b068)? Another option would be to load the file as a tree and compare the trees, but this should work as well. |
Perfect! It's working. Thank you. |
I'd love to automatically do an
i18n-tasks add-missing -v 'TRANSLATE: %{value}'
whenever I add a new key in a view.One approach for this is to use Guard Shell, which can execute a shell command automatically when file modifications are detected:
This works pretty well, but the downside at the moment is, that the
i18n-tasks add-missing
command seems to save all yml files after inspecting them, also when the file doesn't change. This makes Guard get many new "files modified" signals: one for each yml file.Here is the output of Guard:
Is there a reason why i18n-tasks does a "save" action to all yml files? Can it be disabled?
The text was updated successfully, but these errors were encountered: