Attempt to re-register file watcher on file "removal" #106
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.
Fixes #104
Some editors may remove the original file as a part of saving. This causes the file watcher to stop sending notifications
We can work around this by simply attempting to re-register the watcher on the file after a very short delay
Actually removing the file hits a panic with context that the file couldn't be read along with with filepath. This matches the current behavior of
main
and should provide enough information for people to realize what happened