feat: debounce generate watch events

[joerdav]

Fixes: #525

[zolrath]

A couple concrete things in the test suite along with a nit!

[stefanohrmann]

I looked through your changes and I think you are debouncing every fsnotify event regardless of the Op type, that means a REMOVE with a CREATE shortly after will emit as a REMOVE event. The example for debouncing/deduping of fsnotify has a guard for only applying the debouncing/deduping to CREATE/WRITE events:

https://github.com/fsnotify/fsnotify/blob/c94b93b0602779989a9af8c023505e99055c8fe5/cmd/fsnotify/dedup.go#L80-L82

[joerdav]

@stefanohrmann Interesting, seems the example you provided REMOVE would be skipped entirely. I wonder if we dedupe by only events with the same event?

[stefanohrmann]

@stefanohrmann Interesting, seems the example you provided REMOVE would be skipped entirely. I wonder if we dedupe by only events with the same event?

Yes the example is really simple and I think a REMOVE event should clear the timer and prevent the emitting of any previous CREATE/WRITE event(s). Your current implementation does only check for a certain filename/op combination and not that another event for the same filename was already scheduled.

[a-h]

LGTM!