The code is basically complete. However, there are several things needed before version 1.0.0.
The API at the moment is complete & very flexible. However, it would be nice to layer some simpler APIs on top of it in order to do common things more easily. It would also be possible to expose some alternative methods for integrating the state management (i.e. how you call the update function) into the client's app.
I should think about the name of the module. There are a lot of debouncing modules, and I wouldn't want to collide with their names. So, it might be a good idea to use a namespace with this one ... for instance, use module Gizra.Debouncer rather than module Debouncer.
We'll need examples, and ideally tests. Testing will be a little interesting!
rgrempel
commented
6 years ago
The code is basically complete. However, there are several things needed before version 1.0.0.
The API at the moment is complete & very flexible. However, it would be nice to layer some simpler APIs on top of it in order to do common things more easily. It would also be possible to expose some alternative methods for integrating the state management (i.e. how you call the
updatefunction) into the client's app.I should think about the name of the module. There are a lot of debouncing modules, and I wouldn't want to collide with their names. So, it might be a good idea to use a namespace with this one ... for instance, use
module Gizra.Debouncerrather thanmodule Debouncer.We'll need examples, and ideally tests. Testing will be a little interesting!