storage: make size and etag fields optional #326
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These fields are marked as `omitempty` in the Google Cloud Storage's Go SDK. As a result, when an object with size == 0 is encoded using the Go SDK's *storage.Object representation it cannot be parsed by this crate. Fix this by defaulting the size and etag fields to zero/the empty string, respectively.
|
Thank you for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These fields are marked as
omitemptyin the Google Cloud Storage'sGo SDK. As a result, when an object with size == 0 is encoded using
the Go SDK's *storage.Object representation it cannot be parsed by
this crate.
Fix this by defaulting the size and etag fields to
zero/the empty string, respectively.