-
Notifications
You must be signed in to change notification settings - Fork 86
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
The absence of annotation confuses openapi/swagger #896
Comments
Indeed. If the name of the variable matches the variable part of path, then it can be omitted |
We will have to add support for that in openapi. At the moment it will assume that is the body |
This is definitely a bug. There are unit tests specifically for this. |
So the problem is not that it did not create the path param, that actually worked (see below). The problem is that it also added the response body for that param, and that should be omitted.
|
mmm, I can not recreate this in our tests in SmallRye.... |
Signed-off-by:Phillip Kruger <phillip.kruger@gmail.com>
Here the test in SmallRye, seems ok #899 I am still trying to recreate this. |
Signed-off-by:Phillip Kruger <phillip.kruger@gmail.com>
With resteasy reactive, you can omit some annotations.
For example, the following endpoint is valid:
However, it confuses openapi/swagger and we can't invoke it from the Quarkus dev console:
The text was updated successfully, but these errors were encountered: