Repository navigation
|
Is there a way to configure Is this currently supported? |
Replies: 1 comment
|
In 1.169.3, For a server-function call, you can pass it at the call site: const controller = new AbortController()
const result = await myServerFn({
// data: ...,
signal: controller.signal,
})
// Call controller.abort() from your cancellation handler.That's supported by If you want to configure the outgoing RPC request centrally, client function middleware supports For request middleware, the incoming signal is |
In 1.169.3,
next({ signal })isn't part of the supported middleware API. The types for that release don't expose asignaloption onnext.For a server-function call, you can pass it at the call site:
That's supported by
FetcherBaseOptions.If you want to configure the outgoing RPC request centrally, client function middleware supports
next({ fetch: customFetch }). You can customize the fetch options there; preserve any existing signal if you're combining it with a timeout. See the middleware documentation.F…