-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Introduce tags hierarchy #1507
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
Comments
See also #1367 |
Hi @prozac631, If I understood correctly, open api provides a way to tag in operation level. Hope we can group operations by using operation level tagging. Thanks, |
Hi @ymohdriz Yes, we can use grouping for operations, but it would be nice if we could group operations inside of group of operations. Let me make it more clear. For example, you have operations and their paths have the following template: And in the same time you have a set operations that can be performed with these entities, for example: And in this case we can create a tag |
I support the request for sub-tags. I want to be able to group (or at least sort) the methods under each of my endpoints, and as far as I can tell, that's not possible right now. |
See also #1642. The path is already a physical group, why do you need an indirection for it? And as far as I understand it, you can add multiple tags to a given operation. |
I really need subtags. My current tags are getting far too cluttered. |
@jukeblimp32 not sure if this is helpful but have you looked into the |
I support the request for sub-tags or tag hyerarchy. The reason is simple: if I have a single endpoint where I built public and private APIs I would like to group them into these 2 categories. |
Tag Hierarchy doesn't seem to be supported yet? I support this request to add sub-tags. |
Adding sub-tags is ab obvious advantage. Remember, there is no search and filter option for the apidocs, so this tagging system is all we can provide to devs. |
I support this, and furthermore support closing this issue as a duplicate of #1367 so that we can keep the conversation in one place. Adding my comments over there. |
Closing as recommended as a duplicate of #1367 - please continue the conversation there! |
Hello.
My proposal is to add an ability to create tags hierarchy, for example:
It'll help to group operations in case of generic REST API.
The text was updated successfully, but these errors were encountered: