-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
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
feat: add post endpoints #2124
feat: add post endpoints #2124
Conversation
@tschaffter I'm having several issues, but the first one to address is described in this issue When using this branch, the The current requestBody looks like:
I've also tried |
@andrewelamb This is the first time I encounter this use case. I checked first that Swagger UI had a widget to upload files, which it does according to the screenshot in this PR. I tried your request body in Swagger Editor by modifying the default pet store API: openapi: 3.0.3
info:
title: Swagger Petstore - OpenAPI 3.0
version: 1.0.11
externalDocs:
description: Find out more about Swagger
url: http://swagger.io
servers:
- url: https://petstore3.swagger.io/api/v3
paths:
/pet:
post:
tags:
- pet
summary: Add a new pet to the store
description: Add a new pet to the store
operationId: addPet
requestBody:
description: .csv file
content:
application/csv:
schema:
type: string
format: binary
required: true
responses:
'200':
description: Successful operation
Did you click on the "Try it out" button? The upload button does not show up in the Swagger Editor until you do. Before clicking on the button: After clicking: Otherwise, there may be an issue with the Python package in the project that generate the Swagger UI. |
@tschaffter You are correct, clicking the "try it out button" did make that appear. Thanks for looking at this! |
This pr add the POST endpoints from the current API:
/model/submit
split into/submitManifestJson
and/submitManifestCsv
/model/validate
split into/validateManifestJson
and/validateManifestCsv
Fixes fds-901
Fixes fds-902