You can also consider the approach that's been taken for cancelling a fetch promise: it's based on a "signal" that's being created by an AbortController object:
constctrl=newAbortController()constsignal=ctrl.signalfetch(someUrl,{signal}).catch(error=>{console.log(error.name)})// Later on...ctrl.abort()// Then it logs 'AbortError'
You can extend your sleep function to accept a signal option and listen to an abort event. Although it does seem a little overkill for something like this...
Cofounded Host Collective (DiscountASP.net). Cofounded Player Axis (Social Gaming). Computer Scientist and Technology Evangelist with 20+ years of experience with JavaScript!
This is interesting. I'll have to create some test project with the .cancel and an AbortController. Maybe I'll create a debounce to compare the differences.
Definitely something to think about.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, that could work! 🙌
You can also consider the approach that's been taken for cancelling a
fetch
promise: it's based on a "signal" that's being created by anAbortController
object:You can extend your
sleep
function to accept asignal
option and listen to anabort
event. Although it does seem a little overkill for something like this...This is interesting. I'll have to create some test project with the
.cancel
and anAbortController
. Maybe I'll create adebounce
to compare the differences.Definitely something to think about.