You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, creating AbortControllers is not cheap, and so should only be done when the user demands it. Subsequently, the only way for handling this is to increase API surface and provide support for abortable observations:
constdata=observeAbortable(async($,singal)=>{returnawaitfetch('https://my.api/?q='+$(input),{ signal })})
The observe() function can decide to include the signal or not based on the number of arguments provided in the expression, but this should be further investigated as it might be a bit clunky:
constdata=observe(async($,singal)=>{returnawaitfetch('https://my.api/?q='+$(input),{ signal })})
The text was updated successfully, but these errors were encountered:
Right now, the syntax for supporting abort controllers is a bit clunky:
However, creating AbortControllers is not cheap, and so should only be done when the user demands it. Subsequently, the only way for handling this is to increase API surface and provide support for abortable observations:
The
observe()
function can decide to include the signal or not based on the number of arguments provided in the expression, but this should be further investigated as it might be a bit clunky:The text was updated successfully, but these errors were encountered: