update after copy/move #1671
Closed
update after copy/move #1671
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
|
I have not yet tested #1667 which would potentially be the better solution, but perhaps this is still a interim solution or alternative to allow fsnotify to stay an optional dependency. |
This was referenced Apr 1, 2024
|
After testing #1667 I believe the implementation of fsnotify is the better solution and since it already seems to work, I would rather close this merge request unless someone finds it still useful to have an alternative to fsnotify. |
|
Closed in favor of #1667 |
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.
As suggested here this change would add the simple updated trigger after copy/move to cover most use cases.