-
Notifications
You must be signed in to change notification settings - Fork 69
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
Adding endpoints to an OpenAPI specification #222
Comments
Hi! Unfortunately not out of the box. You can work around this by adding the definitions from https://raw.githubusercontent.com/tus/tus-resumable-upload-protocol/main/OpenAPI/openapi3.yaml to your code. Install packages:
Setup a document filter:
Hook it all up in Program/Startup:
|
Hi @smatsson, Thank you for being so helpful! I've played around with OpenAPI and finally received an acceptable result based on your suggestion. Thanks again! |
Hello there.
There is a question related to OpenAPI/Swagger.
I have seen the issue #95, but I wonder if the tusdotnet library supports adding exposed endpoints to an OpenAPI specification?
For example, my service looks like this:
I'd like to have something like:
The text was updated successfully, but these errors were encountered: