We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I need the generated java code include both response body and headers.
I know there is return-response option to return javax.ws.rs.core.Response but that class is not generic and requires casting all the time.
return-response
javax.ws.rs.core.Response
Is there anything similar to spring ResponseEntity<T> in quarkus?
ResponseEntity<T>
The text was updated successfully, but these errors were encountered:
Something like this? https://stackoverflow.com/questions/74646006/theres-a-alternative-for-responseentity-in-quarkus
Sorry, something went wrong.
Yes. Is there any way to generate RestResponse<T> instead of javax.ws.rs.core.Response ?
RestResponse<T>
No, but you can send a PR proposal extending this use case: https://docs.quarkiverse.io/quarkus-openapi-generator/dev/client.html#returning-response-objects
So, one can have:
quarkus.openapi-generator.codegen.spec.my_openapi_yaml.return-response=RestResponse
or
quarkus.openapi-generator.codegen.spec.my_openapi_yaml.return-response=Response
But still fallback to
quarkus.openapi-generator.codegen.spec.my_openapi_yaml.return-response=true
To not break anything.
No branches or pull requests
I need the generated java code include both response body and headers.
I know there is
return-response
option to returnjavax.ws.rs.core.Response
but that class is not generic and requires casting all the time.Is there anything similar to spring
ResponseEntity<T>
in quarkus?The text was updated successfully, but these errors were encountered: