Skip to content

Regenerate GraphQL types for optional S3 photo description#32

Merged
dfalling merged 1 commit into
mainfrom
add-element-photos-2
Jun 4, 2026
Merged

Regenerate GraphQL types for optional S3 photo description#32
dfalling merged 1 commit into
mainfrom
add-element-photos-2

Conversation

@dfalling
Copy link
Copy Markdown
Owner

@dfalling dfalling commented Jun 4, 2026

Summary

  • The backend now defaults a photo's description to "" for S3 uploads instead of requiring it. Previously every device upload was rejected with description: can't be blank, surfacing as "Could not add photo."
  • This regenerates the committed GraphQL types against the updated schema so the client's {type: S3, storageKey} input is valid as-is — no client-side placeholder description needed.

Verified the full pick → downsample → signed URL → S3 PUT → createPhoto flow succeeds against the updated backend. Pure types change; tsc, lint, and tests pass.

🤖 Generated with Claude Code

The backend now defaults a photo's description to "" for S3 uploads
instead of requiring it, which was rejecting every device upload with
"description: can't be blank". This syncs the committed types to that
schema so the client sends the now-valid {type, storageKey} input.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@dfalling dfalling merged commit a4aee86 into main Jun 4, 2026
2 checks passed
@dfalling dfalling deleted the add-element-photos-2 branch June 4, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant