Reference to how this should work in swagger-ui:
https://swagger.io/docs/specification/2-0/grouping-operations-with-tags/
On Wednesday, January 24, 2018 at 12:19:12 PM UTC-8, taddygrrr wrote:
>
> When annotating a Java API like this:
>
> @RestController
> public class SomeController {
>
> @ApiOperation(value="Operation Name", tags=*"Query Interfaces"*,
> notes="Operation
> Note")
>
> @GetMapping(value = "/operation", produces = { APPLICATION_JSON })
> @ResponseBody
> ResponseEntity<SomeResponse> getResponse(
>
> @ApiParam(value="someId", required = false) @RequestParam(value =
> "someId", required=false) String someId)
>
> {
>
> return new ResponseEntity<SomeResponse>(...);
>
> }
>
>
>
> Swagger-UI creates an API Group called "Query Interfaces" and places the
> GET /operation API in it.
> Since upgrading my version of Swagger-UI early January, it also creates an
> empty "SomeController" API group.
> If I put @ApiIgnore on the controller, I lose all APIs in it.
>
> How do I make the empty "SomeController" go away without losing the GET
> /operation API?
> This appears to be a new bug introduced in the last few months.
>
--
You received this message because you are subscribed to the Google Groups
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
