Set responseType
to buffer for HTTP requests
#994
Merged
+9
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, making requests to the camera's HTTP API works like this:
Unfortunately, passing
Buffer
toget
as a type parameter only sets the response'sdata
type toBuffer
at the type level. It doesn't change the behavior ofget
at runtime, which actually still returns astring
because theresponseType
option defaults to'text'
. This happens to kinda work anyway because.toString()
and.length
are available and work the same on bothstring
andBuffer
values, but taking a snapshot returns corrupted data, becausegot
tries to decode the binary JPEG/BMP data as UTF-8 text. SettingresponseType
to'buffer'
corrects this.Checklist