Conversation
…tchSubtree' parameter of ReadDirectoryChanges() for getting events anywhere within the watched folder tree. The original functions, AddWatch() and Watch(), continue to behave as they did before (shallow).
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
|
This PR (HEAD: 1305fe5) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/exp/+/298249 to see it. Tip: You can toggle comments from me using the |
|
Message from Go Bot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be Please don’t reply on this GitHub thread. Visit golang.org/cl/298249. |
The package lacks the ability to watch an entire tree for changes. To address that, I added a Boolean to the system, and the AddDeepWatch() and DeepWatch() functions to enable the 'bWatchSubtree' parameter of ReadDirectoryChanges() with this Boolean. This will allow the watch to report events anywhere within the watched folder tree.
The original functions, AddWatch() and Watch(), continue to behave shallow as they did before--only watching the specified folder--so existing code will not be impacted.