-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Storage: Blob.compose doesn't use default content_type #5834
Copy link
Copy link
Closed
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Metadata
Metadata
Assignees
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Blob.composedoes not use theself._get_content_typemethod, which means Blob.compose raises an error if thecontent_typeis not explicitly specified. This is documented behavior, but is it intended behavior? Should compose useself._get_content_typeto use the default type, or perhaps infer the type from the blobs being composed?