re: Do you use Axios or Fetch? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: There's one thing i find annoying when working with axios (the only module im using right now). So i have a stack wich consists of a react web app...
 

I just came into 2 things that should interest you (and me as well!) :

transformResponse

This is a configuration option in axios that can let us fix this behavior by returning the plain server response:

axios.get("/users", {
  transformResponse: [
    function(data) {
      return data.data;
    }
  ]
});

I find it a bit ugly to have an array of functions...

Interceptors response

Might be a more elegant way to fix it. Plus, you do not have to add it in your configuration for every request, it is done once and for all.

axios.interceptors.response.use(function (response) {
  return response.data;
});

I will try it and if it works, I might start using it again in my projects :)

 

Thanks for your advice. That's a nice way of doing it.
I already use interceptors for listening for the 401 response status.

Although i said that's something annoying the verbosity of axios is at the same time where axios shines. We can take as an advantage the verbosity of the response and use it to enrich our logs

I've been reading about Axios interceptors and it seems like a cool way to address not only HTTP errors but async problems that can pop up

You're right! You can also use request interceptors to add custom headers like an authorization token in every single request, removing the need to write repetitive code

code of conduct - report abuse