Closed dec1 closed 10 months ago
Hi, you can ignore unwanted parts with the ignoredRouteSelectors in the plugin config. Check which RouteSelector the authentication-block adds and add that to the list.
Thank you very much . I have since discovered the unwanted portions of the route were coming from "transparent" children injected in our security code.
createChild(object : RouteSelector() {
override fun evaluate(context: RoutingResolveContext, segmentIndex: Int): RouteSelectorEvaluation {
return RouteSelectorEvaluation.Transparent
}
just in case you might consider including them in generated api spec to be unwanted (since they dont affect the routing decisions)
Hello.
I can generate an openapispec fine with your library, when i dont use authentication.
for example a route such as
is published and can be verified by tests that backend implementation is fine
wheni add authentication (keycloak with jwt) by surrunding the routes in
the routes gets published with superflous
the complete route is now
how can i get rid of this in openapi spec (json and swager-ui) ?
Note: Ive tried initializing swagger as: install(SwaggerUI) {
and the route code like: