Best approach for handling per-request axios config in SWR mutations

[takeshiemoto]

I'm looking for advice on the best way to handle per-request axios configurations with orval-generated SWR mutations.

Current Behavior

The current orval-generated SWR mutation only allows setting global axios request config when initializing the hook. For example with the following mutator:

// mutator.ts
import axios, { type AxiosRequestConfig } from "axios";

export const customInstance = async <T>(
  config: AxiosRequestConfig,
  options?: AxiosRequestConfig,
): Promise<T> => {
  const source = axios.CancelToken.source();
  const response = await AXIOS_INSTANCE({
    ...config,
    ...options,
    cancelToken: source.token,
  });
  return response.data;
};

Request configs like onUploadProgress can only be set globally:

useFileUploadChunk({
  request: {
    onUploadProgress: (e) => { /* ... */ }
  }
});

Expected Behavior

We should be able to pass different axios configs for each trigger call, utilizing the second parameter of the mutator function:

const { trigger } = useFileUploadChunk();

// This should be possible
await trigger({
  ...
}, {
  onUploadProgress: (e) => { /* progress handling for this specific chunk */ }
});

Current Workaround

Currently using transformer to modify the generated fetcher code, but this is not ideal.

Is there a better way to handle this with the current orval implementation? What would be the recommended approach for supporting per-request configurations in SWR mutations?