Throws error when cancelled about debounce-async

[szchenghuang]

You are handling it fine. The caller is notified with the 'canceled' string. If it becomes a bit superfluous when it throws, you can make a string comparison in the catch clause and simply ignore the case with a noop.

[bradley-varol]

I have a use case where I don't want to handle errors with catch() so I'd love an argument to allow me to disable this feature. I'd like to be able to essentially force shouldCancel to always be false.

[szchenghuang]

It rejects in order to tell which are ignored, and to notify the caller. If it resolves with nothing for the ignored, the caller needs to make a comparison between the resolved values in order to tell which is ignored and which is not. It becomes trickier.

[roemhildtg]

Okay, I think that makes sense, maybe I'm just handling it incorrectly. Here's my situation:

const debouncedAjax = debounce((params) => {
    return $.ajax('/api/items', params);
});

// else where in code
// function called whenever params change...this is debounced so if multiple params change quickly
// we don't call the ajax function each time
const result = debouncedAjax(params);

result.then(() => { alert('success!'); })
    .catch(e => { alert(e.message); }); // alerts "cancelled" every time....how do I prevent this?