Support AbortController signal

[acseh]

Hi,
is it possible to support AbortController signal?
Example:

const controller = new AbortController()

client.setConfig({
  ...
  signal: controller.signal,
  ...
})

const timeoutId = window.setTimeout(() => controller.abort(), 15000)
client.setFinally(() => clearTimeout(timeoutId))

Support setFinally function for callback after:

try {
    const response = await fetch(targetUrl, {
      credentials: config.credentials || "same-origin",
      method: config.method.toUpperCase(),
      body: JSON.stringify(config.data),
      signal: config.signal,
      headers: config.headers
    });
  } finally {
// call here setFinally callback
  }

[stijnvanhulle]

@acseh This could be resolved by using the following snippet:

Generated code:

export async function findPetsByStatus(
  { step_id }: { step_id: FindPetsByStatusPathParams['step_id'] },
  config: Partial<RequestConfig> & { client?: typeof fetch } = {},
) {
  const { client: request = fetch, ...requestConfig } = config

  const res = await request<FindPetsByStatusQueryResponse, ResponseErrorConfig<FindPetsByStatus400>, unknown>({
    method: 'GET',
    url: getFindPetsByStatusUrl({ step_id }).url.toString(),
    ...requestConfig,
  })
  return { ...res, data: findPetsByStatusQueryResponseSchema.parse(res.data) }
}

Use with abortController

const controller = new AbortController();

findPetsByStatus({step_id: "2"}, {signal: controller.signal })

controller.abort()

[VasekProchazka]

I have a similar issue.

I would like to add the AbortController on configuration level in client.setConfig() method as a part of my api contract library. I would like to avoid handle each case wih pretty much same code ..