fix: add client response type inference when options.throw is true

[ledouxm]

Hello !
I had an issue with the return type of the better-fetch client when using { throw: true } :

const api = createClient<AppRouter>({
  throw: true,
});


const api2 = createClient<AppRouter>({
  throw: false,
});

const resp1 = await api("/is-first-connection", {});
const resp2 = await api2("/is-first-connection", {});

type AreResponsesEqual = typeof resp1 extends typeof resp2 ? true : false;
//   ^? type AreResponsesEqual = true

So I've used function overloading to fix it.

If you think of a better way of achieving this, please let me know :)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Iulian-Dragomirescu]

This issue still persists in version 2.0.2

When using:

const res = await apiClient("/v1/quiz/categories"); the returned type is inferred as: res.data?.ok (and the data is also correctly under res.data)

However, when using:

const res = await apiClient("/v1/quiz/categories", { throw: true }); the inferred type is still: res.data?.ok
but the actual data is returned as: res.ok

So the type is not correctly inferred when throw is set to true