Move watcher init to doWatcherLoop and implement -reloaddirs #2871
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.
Description
In investigating #2829 i found that the
*fsnotify.Watcher
was only passed to a single functiondoWatcherLoop
but thef.ReloadDirs
wasn't parsed until inside thedoWatcherLoop
.This PR moves the definition into
doWatcherLoop
to prevent unnecessary passing of the object, and implemented adding the-reloaddirs
flag to the watcher. To prevent over-subscribing the watcher, i made the intentional choice not to make the watch recursive (like the main folder is), instead opting to explicitly watch only the directories specified by the user.Fixes #2829
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested using the steps outlined in #2829 to confirm resolution:
Test Configuration
Checklist:
website/src/pages/changelog.mdx
with details of this PR