fix(docs): correct comment to reflect raw bytes instead of base64 #1369
+1
−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.
This PR updates the field comment for
content_bytesto correctly describe its purpose. The comment previously stated that the value was Base64-encoded, but the field type (bytes) indicates it contains raw binary data.Changes
content_bytesholds raw bytes, not Base64-encoded content.Reason for Change
The previous comment was misleading and inconsistent with the field’s type annotation. This correction improves clarity and helps prevent confusion for developers using or maintaining the code.
When base64 used instead, I was getting this error below: