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
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.
The text was updated successfully, but these errors were encountered:
Explanation
You can create 4 types of 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.
The text was updated successfully, but these errors were encountered: