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
timeout param does not currently trigger an AbortController signal in client side code, only applies in the <await> tag of server side code.
Expected Behavior
timeout param passed into micro-frame used on browser side should cause the fetch to be aborted, if no value is passed then the default 30s should apply.
Actual Behavior
micro-frame never times out, even if you specify a timeout value.
Possible Fix
A default AbortController is created, but it seems to only be used for onDestroy and onUpdate aborts, and does not make use of the timeout value (or 30s default). A setTimout or some other method could be used to trigger an AbortSignal.abort() if the time is reached
The text was updated successfully, but these errors were encountered:
Version: 1.4.2
Details
timeout
param does not currently trigger anAbortController
signal in client side code, only applies in the<await>
tag of server side code.Expected Behavior
timeout
param passed intomicro-frame
used on browser side should cause the fetch to be aborted, if no value is passed then the default 30s should apply.Actual Behavior
micro-frame
never times out, even if you specify atimeout
value.Possible Fix
A default
AbortController
is created, but it seems to only be used foronDestroy
andonUpdate
aborts, and does not make use of thetimeout
value (or 30s default). A setTimout or some other method could be used to trigger anAbortSignal.abort()
if the time is reachedThe text was updated successfully, but these errors were encountered: