Question: AngularJS $http API compatibility?

For my hy-res hypermedia client library, which also has a thin AngularJS wrapper angular-hy-res, most of the library expects an $http-like API for making and consuming requests. For the most part, I can interchange axios (e.g. in my integration tests for the hy-res core library) and $http in the angular-hy-res case without problem.

The only area where I have hit a true API incompatibility is with the handling of the headers in either the resolved promises, or the parameters for things like transformRequest. You can see an example here.

Question: Is axios’ goal to be as API compatible with $http as possible? If so, would you consider changes to the headers instances to match AngularJS?

[petejohanson]

It is not only internal. See:

• https://github.com/angular/angular.js/blob/master/src/ng/http.js#L1268 - passed as headers field of response promise.
• https://github.com/angular/angular.js/blob/master/src/ng/http.js#L918 - passed into transformation function.

You can see this in the docs here: https://docs.angularjs.org/api/ng/service/$http under the Usage of $http(config) for transformRequest, transformResponse, and the return value.

Those are in fact the two cases where the API differs between $http and axios.

[patrickliechty]

I will look into moxios thanks. Ya I don’t think it has to work just the same as $http