Add some features from useFetch also to useAxios

Currently useFetch has execute(), but useAxios does not. This means that with useFetch you can first create useFetch, set {immediate: false}, then execute() the call later, but with useAxios it fires immediately when you call useAxios.

Abort is also missing in useAxios.

Some properties don’t make sense to add into axios such as statusText (since that’s just in the axios response).

Another thing is that the returned property names are different in useAxios and useFetch, but changing that’d be a breaking change.

Exposed logic from both logics:

useAxios

  response: Ref<AxiosResponse<T> | undefined>
  data: Ref<T | undefined>
  finished: Ref<boolean>
  loading: Ref<boolean>
  canceled: Ref<boolean>
  error: Ref<AxiosError<T> | undefined>

useFetch

  isFinished: Ref<boolean>
  statusCode: Ref<number | null>
  response: Ref<Response | null>
  error: Ref<any>
  data: Ref<T | null>
  isFetching: Ref<boolean>
  canAbort: ComputedRef<boolean>
  aborted: Ref<boolean>
  abort: Fn
  execute: () => Promise<any>

[antfu]

Would love to align those interfaces. We can make aliases and for APIs and mark some as deprecated. Then drop them in along with the next major.

[antfu]

Aligning with useFetch looks better to me