We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The OpenAPI document does not have request body for post and put requests for object endpoint. It only has path and header parameters.
https://supabase.github.io/storage/api.json
"/object/{bucketName}/{wildcard}": { "post": { "summary": "Upload a new object", "tags": ["object"], "parameters": [ { "schema": { "type": "string" }, "example": "avatars", "in": "path", "name": "bucketName", "required": true }, { "schema": { "type": "string" }, "example": "folder/cat.png", "in": "path", "name": "*", "required": true }, { "schema": { "type": "string" }, "example": "Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24ifQ.625_WdcF3KHqz5amU0x2X5WWHP-OEs_4qj0ssLNHzTs", "in": "header", "name": "authorization", "required": true } ], "responses": { "200": { "description": "Successful response", }
In one of the SDKs I see that the body should be multipart form body? What are the required and optional fields?
The endpoints should have requestBody property with the appropriate content type and fields.
requestBody
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug report
Describe the bug
The OpenAPI document does not have request body for post and put requests for object endpoint. It only has path and header parameters.
To Reproduce
https://supabase.github.io/storage/api.json
Expected behavior
In one of the SDKs I see that the body should be multipart form body? What are the required and optional fields?
The endpoints should have
requestBody
property with the appropriate content type and fields.The text was updated successfully, but these errors were encountered: