-
Notifications
You must be signed in to change notification settings - Fork 485
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
Swagger + URI Versioning #1495
Comments
This should work as expected. Please provide a minimum reproduction repository. |
@kamilmysliwiec Because I got the same issue, I add a POC to describe the problem. I made a simple POC here:
|
|
Nice, it works if I do that. Please write a note into the documentation about this requirement. |
I'm submitting a...
Current behavior
Using the new versioning featuring, specifically the URI option, Swagger fails to detect whether the controller has a version associated with it or not. When I'm on the Swagger UI, my endpoints return with 404's as none of the endpoints are using the versioned URI. When executing an option in Swagger, it tests with
api.com/test
when it should be testing withapi.com/v1/test
for example.Expected behavior
Swagger UI should seamlessly work with the new Versioning feature, or even a dropdown per endpoint to select different versions of the API could be added.
Minimal reproduction of the problem with instructions
NestJS + Swagger/OpenAPI setup with controllers using URI versioning.
What is the motivation / use case for changing the behavior?
Seamless integration between Swagger and the new versioning feature.
Environment
The text was updated successfully, but these errors were encountered: