Setting Default Headers After Create about apisauce

[skellock]

Now supported with 0.3.0 just released.

api.setHeader('Authorization', 'new stuff')
api.setHeaders({ 'X-Fun': 1, 'X-More-Fun': 69 })

More details in #20

[duketwo]

+1, how to modify the header with the current build per request?

[skellock]

It's the third parameter.

api.post('/users', {name: 'duke'}, {headers: {'x-hello': 'world'}})

I'll document this better.

[gaboelnuevo]

+1 for this enhancement

I need to do something like this:

api.post('/users/login', {
"email": "[email protected]",
"password": "bar"
}).then((response) => api.overrideConfig({
headers: {'Authorization': response.data.token}
})
);

[GantMan]

Hah, I should have dug through issues, I just solved this on my side. Agreed, exposing axiosInstance is not nice.

[GantMan]

Also worth noting, axios docs has
instance.defaults.headers.common['Authorization'] as a possibility in their latest. But this doesn't work with the version associated in latest apisauce.

Since we have to touch/know axios, to update headers, it's a good idea to at least update it for the time being.

[skellock]

I expose axios exactly for this reason. I didn't want to trap Axios' abilities behind our API.

Common features like this exactly what apisauce should do for us, you're right.

I will bump the version this weekend!

Thanks dude!

[GantMan]

Sweeeeet! yeah, having it exposed is good for work-arounds.

[ningo-agilityio]

I already used setHeader but it was refreshed after browser refresh.

[ryanlntn]

@ningo-agilityio That would be expected behavior as any in memory object state would be reset on a browser refresh. You'll need to store any tokens you might want to hold on to in a persistent store like local storage and restore them in a document.onreadystatechange callback. For example:

document.onreadystatechange = () => {
  if (document.readyState === 'complete') {
    const token = localStorage.getItem('authToken')
    api.setHeader('Authorization', token)
  }
}