I would expect that only two files could cause the task to fire: the shouldFire file and the second shouldFire file under the shouldFireDir directory.
However, the task is fired if a directory is created in either the repo's root directory, or under the shouldFireDir directory. For example, if I mkdir blah in the root directory, this task fires. Note that this issue only occurs if you create a directory: touching a file does not cause the task to incorrectly fire.
Either this is incorrect or I do not understand how the files matching syntax works.
Test case repository: https://github.com/SCdF/grunt-contrib-watch-watches-dirs-by-mistake
Basically, given the following watch config:
I would expect that only two files could cause the task to fire: the
shouldFire
file and the secondshouldFire
file under theshouldFireDir
directory.However, the task is fired if a directory is created in either the repo's root directory, or under the
shouldFireDir
directory. For example, if Imkdir blah
in the root directory, this task fires. Note that this issue only occurs if you create a directory:touch
ing a file does not cause the task to incorrectly fire.Either this is incorrect or I do not understand how the
files
matching syntax works.