Skip to content

[UI/UX] - Improve readability of multiple parameters by grouping them into sections #6661

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
oopm opened this issue Nov 27, 2020 · 0 comments · Fixed by #6745
Closed

[UI/UX] - Improve readability of multiple parameters by grouping them into sections #6661

oopm opened this issue Nov 27, 2020 · 0 comments · Fixed by #6745

Comments

@oopm
Copy link

oopm commented Nov 27, 2020

Explanation

You can create 4 types of parameters

  • query parameters
  • uri parameters
  • header parameters
  • cookies parameters

Today, on the UI, The parameters of a request is resolved by having two columns: Name and description. In the name the data is organized in the following way: the name of the parameter, its schema type and what kind of parameter it is. And the parameters are organized in the order of which they are captured on the editor.
If you have only a couple of parameters this is pretty much fine, however as soon as you as have for example 8 header parameters + 4 uri parameters + 12 query parameters and 6 cookie parameters and for some reason the writer of the api didn't organize them by type, then it is pretty hard to know which parameter belongs to what kind.

Describe the solution you'd like

It would be great if on the UI the parameters could be grouped by type no matter which order they where captured on the editor and into sections, so that you can see straight at a glance, that those are header parameteres and those are query params.

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

Successfully merging a pull request may close this issue.

2 participants