Gmail drafts.create upload always sends application/octet-stream instead of message/rfc822

[rodrigoescandon]

Bug Description

When using gws gmail users drafts create --upload <file.eml>, the uploaded file's MIME type is always set to application/octet-stream, causing the Gmail API to reject it with:

Media type 'application/octet-stream' is not supported.

The Gmail API requires message/rfc822 for draft/message uploads.

Root Cause

In src/executor.rs, build_multipart_body() reads the MIME type from the request body's mimeType field (lines 740-745):

let media_mime = metadata
    .as_ref()
    .and_then(|m| m.get("mimeType"))
    .and_then(|v| v.as_str())
    .unwrap_or("application/octet-stream");

This works for Drive uploads where mimeType is a valid body field (e.g., --json '{"name": "file.pdf", "mimeType": "application/pdf"}').

However, for Gmail uploads, the body schema only allows {"message": {...}, "id": "..."} — there is no mimeType field. Schema validation rejects any attempt to add one:

$ gws gmail users drafts create --params '{"userId": "me"}' \
  --json '{"message": {"threadId": "..."}, "mimeType": "message/rfc822"}' \
  --upload message.eml

Error: Request body failed schema validation:
- mimeType: Unknown property. Valid properties: ["id", "message"]

So the MIME type always falls back to application/octet-stream, making Gmail uploads impossible.

Suggested Fix

When mimeType is not present in the body metadata, the CLI could:

1. Infer from file extension: .eml → message/rfc822, .pdf → application/pdf, etc.
2. Use API-specific defaults: Gmail endpoints could default to message/rfc822 instead of application/octet-stream.
3. Add a --upload-type flag: Let users specify the MIME type explicitly (e.g., --upload-type message/rfc822).

Steps to Reproduce

1. Create a valid RFC 2822 email file (e.g., message.eml)
2. Run:

   gws gmail users drafts create \
     --params '{"userId": "me"}' \
     --json '{"message": {"threadId": "abc123"}}' \
     --upload message.eml
   

3. Observe error: Media type 'application/octet-stream' is not supported.

Environment

• gws version: 0.6.0
• OS: macOS (Darwin, aarch64)

Affected APIs

This likely affects all Google APIs that require specific upload MIME types and don't have mimeType in their body schema (Gmail being the most notable).

[rodrigoescandon]

Closing as duplicate of #247, which covers this same issue more comprehensively (both the --upload wrong content type and the --json argument length limit).

A fix exists in a fork: NeekChaw@800cee5 (we haven't tested it ourselves).

[chrisvariety]

NeekChaw@800cee5 doesn't work without a patch like:

#!/usr/bin/env bash
# Fixup for NeekChaw/cli@800cee5 — adds missing upload_type (None) arg
# to execute_method calls that were missed in the patch.
# Run from the root of the gws-patched repo.

set -euo pipefail

files=(
  src/helpers/gmail/send.rs
  src/helpers/calendar.rs
  src/helpers/chat.rs
  src/helpers/drive.rs
  src/helpers/script.rs
)

for f in "${files[@]}"; do
  if [[ ! -f "$f" ]]; then
    echo "SKIP $f (not found)"
    continue
  fi
  # Insert None, on the line before matches.get_flag("dry-run")
  # preserving the original indentation
  sed -i '/matches\.get_flag("dry-run")/i\                    None,' "$f"
  echo "FIXED $f"
done

(works great with that patch though, at least for --json #247