Skip to content

Can we make sub tags #2129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
faizaantrialx opened this issue Apr 29, 2016 · 7 comments
Closed

Can we make sub tags #2129

faizaantrialx opened this issue Apr 29, 2016 · 7 comments

Comments

@faizaantrialx
Copy link

  1. abc
    i. xyz
    a. xyz- api call
    b. ....
    ii. pqr
    a. ....
    b. ....
    2.
@webron
Copy link
Contributor

webron commented Jun 9, 2016

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 webron closed this as completed Jun 9, 2016
@faizaantrialx
Copy link
Author

Thanks Ron

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

Closed #2129 #2129.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2129 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AH2qazNIKVdvr7SDJh-q-Hs37SDYLwQjks5qKI1xgaJpZM4ISt85
.

@kamil-kielczewski
Copy link

@webron - why?

@webron
Copy link
Contributor

webron commented Oct 4, 2017

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

@kamil-kielczewski
Copy link

kamil-kielczewski commented Oct 5, 2017

@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

@kritika020594
Copy link

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

@zer0890
Copy link

zer0890 commented Aug 2, 2018

anyone got a solution about this possibility ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants