Closed grayside closed 9 years ago
On second thought, newer might be a decent way to roll as it should be picking up on the same changes watch detected, and with less likelihood of timing issues muddling which files are going to be checked. Like #151, this brings us back to https://github.com/SaschaGalley/grunt-phpcs/issues/23 because grunt-phpcs is currently unfriendly to newer.
This points out how to configure an event that feeds your grunt tasks with the changed files. We'd want to use the "smart" approach. https://github.com/gruntjs/grunt-contrib-watch#compiling-files-as-needed
I've also rolled a quick experiment in creating a validate:newer option. This isn't effective for watch, but referencing as related work.