Hi, I have some question about how File Watchers behave in different situations:
- a some files are modified, the watcher is currently processing command of the first edited file, what does it do next?
I understand that every changed file is queued, and for each one of the command is run sequentially
my command is general (e.g. "compile /folder"), so it's not meant to be run for every watched file, does the behaviour above change in this case?
From what I understand no, if it's a long process it's still going to be ran for every file changed after the command was run, even if it's the same file of course.
root files: not sure of what type of static analysis is done to determine dependencies, what is supported? what isn't?
"To run the File Watcher only against root files, select the Track only root files checkbox."
All files are watched, but the command gets called on the root file instead, if the appropriate macros are used.
"Clear the checkbox to run the File Watcher against the file from which it is invoked and against all the files in which this file is recursively included within the specified scope."
The command is executed from the edited file upwards, for every file in the chain, for every file changed. Even if the command is general
- "Output paths to refresh [...] Based on these settings, WebStorm recognizes the files generated through compilation."
I've seen that with this info, the watcher is able to ignore the output and not go in a loop if the output matches the files watched. The option is called "refresh", so I've been using it to "refresh" (from the disk?) folders too, something like "build/", or "build/*.*"? or "build"? Are all ok? Are folders ok? I can't really tell if they are working or not