Improved handling of file & folder renaming/moving #402
Conversation
This file contains 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
Using a file's ino value as an identifier that remains the same after moving
…o file-move-detection-improvements
…o file-move-detection-improvements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Chokidar is kind of awkward when it comes to moving/renaming files and folders, it emits an
addandremoveevent instead of amoveorrenameevent as you'd expect.I came across some workarounds in here: paulmillr/chokidar#303 (comment)
Apparently every file has an
inofield which remains the same after renaming/moving. In this PR I use that to detect whether we already detected the file before when anaddevent is emitted, so we don't add it as a new file