Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Behavior in operations with multiple tags #148

Open
cguedes opened this issue Sep 23, 2016 · 1 comment
Open

Behavior in operations with multiple tags #148

cguedes opened this issue Sep 23, 2016 · 1 comment

Comments

@cguedes
Copy link
Contributor

cguedes commented Sep 23, 2016

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.

image

I guess this is not a good UI/UX. What is the best UI/UX for this?

  1. should we repeat the operation?
  2. if we repeat the operation, shouldn't we use/add the tag to the internal operation id?
  3. should this be configured?
  4. should we use only the first tag in the tags list for the operation?
@danielbcorreia
Copy link
Contributor

danielbcorreia commented Nov 17, 2016

  1. Yes
  2. No
  3. Yes, by default it should select all the operations that match
  4. No

We need to define the behavior when we choose to select only one operation.

@danielbcorreia danielbcorreia added this to the API Explorer 1.0.0 milestone Nov 17, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants