Require interceptors to return values breaks some interceptor usage

[KieraDOG]

Describe the bug

Here is how we use interceptor to extract data from response rather than duplicate the same logic .then((res) => res.data) everywhere in the project

api.interceptors.response.use((res) => res.data)

however because of the new changes from #4874,

Sensible interceptors must return either an AxiosRequestConfig or an AxiosResponse or else they break other interceptors and Axios internal logic.

The PR is to required interceptor to return data, but it ends up not only require to return data, but require to return axios response type data, thus it limited the usage of interceptors, just wanna to confirm whether this is in purpose or it is a bug

To Reproduce

// Example code here
// In Typescript, write interceptor like this:

api.interceptors.response.use((response: AxiosResponse): unknown => response.data)

// Type 'unknown' is not assignable to type 'AxiosResponse<any, any> | Promise<AxiosResponse<any, any>>'.

Expected behavior

Expected code running without type error

Environment

• Axios Version [1.1.2]
• Adapter [e.g. XHR/HTTP]

[ghost]

I'm using version 1.1.3, and Ican use it like this:

ai.interceptors.response.use(
  (response) => {
    return response.data
  },
  (error) => {
    return Promise.reject(error)
  }
)

But, when I use it like this:

interface CustomAxiosResponseData<T = unknown> {
  code: string
  data: T
  message: string
}

ai.interceptors.response.use(
  (response) => {
    const { data }: { data: CustomAxiosResponseData } = response
    return data
  },
  (error) => {
    return Promise.reject(error)
  }
)

When I switch to using version 0.27.2, it works well.
Is this right? Or is there any way to change the returned value type in a response interceptor at version 1.1.3?

[lxy2018]

I have the same problem and cannot fix it.
So, I chose to ignore this stupid bug(or feature) by using // @ts-ignore.

[alili]

api.interceptors.response.use((res) => res.data)

I think it is a very common and reasonable use that should not be completely prohibited by the framework

[KieraDOG]

Hi axios team, any update on this one?