Expose Axios client/module from the HttpService

[ryanswart]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

The HttpService hides does not provide core Axios capabilities such as interceptors / transformers.

Expected behavior

Full access to Axios capabilities, by exposing the Axios instance used by the HttpModule. We could possibly also create new Axios clients for each HttpService instantiated, which will provide more granular control.

What is the motivation / use case for changing the behavior?

My primary use case is for debugging Axios requests, which is currently painful, as in a chain of requests, the logs do not specify where a request has failed. Adding an interceptor to the Axios instance would easily provide visibility into what is being requested and identify where the system is failing.

I'd be happy to pick this up if it makes sense

[cojack]

@ryanswart Hmmm why not just

import * as axios from 'axios'?

[ryanswart]

@cojack The HttpService doesn't end up using the global axios instance when I try it like that - ie. interceptors & defaults don't work. (and I want to use the module for the testing benefits it provides)

[kamilmysliwiec]

The reference to the underlying axios package will be available through axiosRef property from the HttpService in the upcoming release.

[ryanswart]

Great thanks! Should I close the issue?

[kamilmysliwiec]

Added in v5.1.0

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.