Open sathishvj opened 9 years ago
Maybe the watch function is a good place to allow file changes to settle down. A millisecond parameter might work.
My assumption here is that it is something to do with timing because it works ok on a fast machine but not so on a slow one. However, if that assumption is wrong, then I suppose the fix suggestions are also off.
use godo server --verbose
to print files
I'll look at the Debounce logic
will be fixed as part of #24 and v2 refactor
I'm currently facing an issue where the Task is getting repeatedly kicked off a large number of times. I'm assuming it's because one of the tasks I'm doing is a 'go generate' which creates more go files. Is there a way for us to print out the files that changed and therefore kicked off the task?
Or maybe there should be a way for godo to bunch up a few changes and only then kick off a task. (Debounce for some reason does not work.)