Swagger-ui: Can we make sub tags

Created on 29 Apr 2016 · 7Comments · Source: swagger-api/swagger-ui

abc
i. xyz
a. xyz- api call
b. ....
ii. pqr
a. ....
b. ....
2.

Nice to have feature

Source

faizaantrialx

👍7

Most helpful comment

@webron - yes you have right, how ever it is very practical feature (especially for large APIs) and may be "incorporated" into to specification in future (here I put my proposal ) . How ever my proposition (i think) will be simpler than @faizaantrialx : we can use following convention in tags names (using dots to nesting subtags):

users.client     # and use this tag to client GET/POST/...
users.seller     # and use this tag to seller GET/POST/...
users.admin      # and use this tag to admin GET/POST/...
books            # use this to general books GET/POST...
books.sell       # use this to GET/POST... associated with the sell
books.management # use this to GET/POST... associated with the books management

And in output web-page we will get:

user >
       client >
GET
POST
...
       seller >
GET
POST
...
       admin >
GET
POST
...

books >
GET
POST
...
       sell >
GET
POST
...
       management >
GET
POST
...

If you give me some tips where Is the code of swagger-ux wich generate view I can try to implement this feature

kamil-kielczewski on 5 Oct 2017

👍10

All 7 comments

swagger-ui doesn't support it and there's no plan to add this functionality. You can modify the code to achieve this functionality.

webron on 10 Jun 2016

Thanks Ron

On Fri, Jun 10, 2016 at 3:32 AM, Ron [email protected] wrote:

Closed #2129 https://github.com/swagger-api/swagger-ui/issues/2129.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/swagger-api/swagger-ui/issues/2129#event-687888631,
or mute the thread
https://github.com/notifications/unsubscribe/AH2qazNIKVdvr7SDJh-q-Hs37SDYLwQjks5qKI1xgaJpZM4ISt85
.

faizaantrialx on 10 Jun 2016

@webron - why?

kamil-kielczewski on 4 Oct 2017

@kamil-kielczewski because it goes beyond what the specification defines.

webron on 5 Oct 2017

users.client     # and use this tag to client GET/POST/...
users.seller     # and use this tag to seller GET/POST/...
users.admin      # and use this tag to admin GET/POST/...
books            # use this to general books GET/POST...
books.sell       # use this to GET/POST... associated with the sell
books.management # use this to GET/POST... associated with the books management

And in output web-page we will get:

user >
       client >
GET
POST
...
       seller >
GET
POST
...
       admin >
GET
POST
...

books >
GET
POST
...
       sell >
GET
POST
...
       management >
GET
POST
...

If you give me some tips where Is the code of swagger-ux wich generate view I can try to implement this feature

kamil-kielczewski on 5 Oct 2017

👍10

Is this issue yet not resolved?

How can we get the following sub tagging-

ABC

4.0
..
..
..
4.5
..
..
..

XYZ

3.3
..
..
3.4
..
..

Means an api having different version and is categorized accordingly