Repository navigation
feat: file upload routes (POST /files, GET /files/{id}) - #13
Merged
Merged
Conversation
…d}) and add files.upload Regenerated from the production spec: the files routes and the photo_ids documentation. files.register and files.get wrap them; files.upload registers a file and PUTs its bytes (no API key on the PUT, retried like any call). Not released by this change.
This file contains hidden or 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
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.
Regenerated from the production spec (backend 2.143.0, API-037):
POST /api/public/v1/filesandGET /api/public/v1/files/{id}.client.files.register/getwrap the generated routes;client.files.upload(data, filename, content_type)registers the file and PUTs its bytes (no API key on the PUT, retried on 429/5xx); the id goes inphoto_ids.Tests: 45 passed.
🤖 Generated with Claude Code