Add OpenAPI specification for /upload endpoint. #1032
Merged
Conversation
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
|
@microsoft-github-policy-service agree |
dluc
approved these changes
Mar 22, 2025
|
Big Thanks @FabianSchurig 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi @dluc
Currently the specification of the
/uploadendpoint is not automatically generated.My change manually adds the specification to
service/Service.AspNetCore/WebAPIEndpoints.cswhich enables the SwaggerUI to provide a Try it out option with the upload feature and setting the request body.Important
Furthermore, I will need the generated change of the
swagger.jsonto automatically generate the python client withopenapi-python-generatorin a follow up PR. The client will be auto generated based on the OpenAPI spec.Here an example of how it is looks like and works:
