allow accumulate to work with single or no result

[EdJoPaTo]

some debounced functions does not need to return something or return a conclusion of what happened

[EdJoPaTo]

Is there something preventing this to be merged?

What can I do?

[bjoerge]

Thank you for taking the time to make a PR for this, @EdJoPaTo. I like the idea!
The proposed implementation can however lead to quite surprising behavior in cases where the "single value" you want to return is actually an array value. As an example, consider if instead of .some you were to use .filter here:

debounce-promise/test/index.js

Line 161 in 8d7bd85

.some(o => o > 10)

A better solution would be to add an option that explicitly tells the debounce-function to treat the wrapped function as a single-value returning function.

[EdJoPaTo]

You are right, I did not thought of the single value response "array".

My main point for doing this was the undefined response. Debounced workers will often have no response at all. Other single values were just the superset of this.

Having a clear interface to the method is also better than "magic" changing the interface based on the return value. I think the best variant is to allow falsy like undefined returns which returns undefined to every caller or expect the full array like the current implementation.

As you suggested an extra option could be allowing single values responses the same for every caller. But im not sure if thats really needed. The idea is there, it can be implemented when it's needed I think.