With both present, and that is because in OAS3, it is not possible to override the "default" content-type anymore.
#SWAGGER APIPARAM GENERATOR#
However, even setting text/event-stream in the yaml/json spec file, the generator will still generate: Now, I've also noticed that the generated response is: The project will not start without attempting to inject this bean, so I'm having to comment this out in the generated code. Before Field Expansion: After Field Expansion: There are several ways to use Swagger AlternateTypeRules. It also includes ApiParam annotation values and is configurable through SpringDataWebProperties settings. I've tried mocking it as well as creating a no-op bean, since, in the servlet context, this is completely unused. Heres my expansion on the previous two examples. However, in the default web servlet context, the bean ServerWebExchange does not exist. One can have a project that is mostly rest-endpoints in servlet spring-mvc/boot web context, and have some select controllers return a webflux react Mono/Flux response. The default in spring is : servlet web context, if both servlet context (eg the so called spring-mvc) and a reactive libraries are found on the classpath it will default to picking Servlet web context. Can not import ApiParam or ApiModelProperty annotation eventough Swagger is added as a Maven dependency. For my controller classes using Tag, Operation and. I would like to use annotation based configuration for Swagger. Package for swagger 3 annotations is -> -> -> -> -> -> = true) or = true) or -> -> there's still an issue with the generation = true) final ServerWebExchange exchangeĪnd that is that: you can't assume that the project is running in a Reactor web context. I am working on a project where we document our backends API with Swagger.
Replace swagger 2 annotations with swagger 3 annotations (it is already included with springdoc-openapi-ui dependency).
Is there a way to configure that in my pom.xml as to use the newer annotation ? I analyzed the options reported above and came to the following conclusions.
#SWAGGER APIPARAM UPDATE#
I used to expose my paths and json spec to customer through springfox, and I want to update that as to expose an openApi spec file.įollowing the guide for migration found I see the annotation used by openApiCode are still the "swagger2" one Describe the solution you'd like I've migrated my API from swagger codeGen and swagger2 to openApi codeGen and openApi. Is your feature request related to a problem? Please describe.
0 kommentar(er)
