-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(deps): use gaxios
for HTTP requests instead of axios
#593
refactor(deps): use gaxios
for HTTP requests instead of axios
#593
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
THIS IS EXCITING.
@@ -950,11 +951,12 @@ it('should not retry requests with streaming data', done => { | |||
const scope = nock('http://example.com').post('/').reply(401); | |||
client.credentials = { | |||
access_token: 'initial-access-token', | |||
refresh_token: 'refresh-token-placeholder' | |||
refresh_token: 'refresh-token-placeholder', | |||
expiry_date: (new Date()).getTime() + 500000 |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
gaxios
for HTTP requests instead of axios
Tested with several of the client libs as well. BigQuery, Bigtable, Compute, DNS, Logging, Storage to name a fewveral. |
And it worked!? |
Yep! And the proxy test script I've been using. |
This switches from Axios to Gaxios. Hopefully nobody notices.