It’s not supported by the spec so the tooling doesn’t support this either.

> On Jan 22, 2017, at 9:58 PM, kani mozhi <[email protected]> wrote:
> 
> I just started working on Swagger api 2.0 recently.I am looking for some ways 
> to organize the API documentation.
> Currently am using @Api(tags = {"Heading1"}) annotation to tag each api.
> Now the documentation looks like
> Tasks
> --------->Heading1
>           -------->Desc1
>           --------->Desc2
> ---------->Heading2
>           --------->Desc3
>           --------->Desc4
> 
> But i am looking for adding some subheadings i the doc ,so that it looks like 
> 
> 
> --------->Heading1
>           -------->Desc1
>           --------->SubHeading1
>                         --------->Desc2
> ---------->Heading2
>           --------->SubHeading1
>                      --------->Desc3  
>           --------->SubHeading1
>                      --------->Desc4
> 
> How do i achieve this ?
> 
> -- 
> 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] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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.

Reply via email to