Only do a back up for bigger changes or if a different field is edited #3004
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes the BackupManager a little more intelligent. It fixes a bug that I've only noticed locally and discussed with @tobiasdiez in chat. There's no issue for it, but the fix comes directly here.
If you have save actions configured (say LatexToUnicode) and the backup triggers too early (say after 5 characters) then the BackupManager interrupts you if you add a longer command in the entry edior (say
\alpha
). With this PR, the BackupManager is no longer triggered every five characters, but only if there are changes of more than one character (a user pastes text into the entry editor) or if the user edits a different field than before. This seems way more reasonable to me and is as it has been before (only backups when a user changes the field, edits a group, etc.)gradle localizationUpdate
?