You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
As per swagger spec, operations can be tagged with multiple tabs.
tags | [string] | A list of tags for API documentation control. Tags can be used for logical grouping of operations by resources or any other qualifier.
The current implementation displays the operations in the lateral menu grouped by tags, and when some operation (with multiple tags) is selected, all of the entries became highlighted.
I guess this is not a good UI/UX. What is the best UI/UX for this?
should we repeat the operation?
if we repeat the operation, shouldn't we use/add the tag to the internal operation id?
should this be configured?
should we use only the first tag in the tags list for the operation?
The text was updated successfully, but these errors were encountered:
As per swagger spec, operations can be tagged with multiple tabs.
The current implementation displays the operations in the lateral menu grouped by tags, and when some operation (with multiple tags) is selected, all of the entries became highlighted.
I guess this is not a good UI/UX. What is the best UI/UX for this?
The text was updated successfully, but these errors were encountered: