-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
Version: 1.4.2
Details
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
Metadata
Metadata
Assignees
Labels
No labels