-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
File encoding with drive API broken #1151
Comments
Greetings! Can you share the exact API you're trying to call? Or the docs that call out you can specify the file encoding? Just want to make sure I'm reading the right thing :) |
Sure thing @JustinBeckwith ! So basically what were using is Google Drive API for downloading a single file.
In the documentation on request level options of the client, it says:
Passing the encoding in request options used to work at least before I digged into So I think that in order to resolve this, and continue supporting response encoding option, In the meanwhile, this can be resolved (at least on our end) in the application logic by returning array buffer from the request and handling the encoding in the application logic itself instead relying on the library. E.g.
|
Since we last took a look here, we switched our underlying transport layer from Are you still having issues here? |
I think this can be considered resolved. |
Google Drive API allows specifying file encoding for the response data. Underneath it's overriding Axios options, like the documentation states.
However, with the current latest Axios release (0.18.0), which this library is using, this is not implemented. This axios/axios#869 PR has that feature implemented, but it's not part of the released package. Also, it seems that even with these changes included, the Google Node Client implementation regarding file encoding doesn't work in the documented way (how it used to work prior to the switch to Axios from Request).
The text was updated successfully, but these errors were encountered: