Support atomic update#5
Closed
mauricioszabo wants to merge 3 commits into
Closed
Conversation
Merged
|
Fixed in #6! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For automated updates of files, most tools support atomic updates - it essentially creates a new file, fills it with the contents, and rename this new file to the one being "changed".
Pathwatcher emits a
did-renameon this case, but if we're watching a file with a namefoo.txt, we don't want to know that it was "renamed" tofoo.txt- we want adid-change. This PR implements this.I tested on my local copy of Pulsar, and the errors I was experiencing (tools that provoke an atomic update not changing the editor) are now fixed.