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
Current situation: in the left-hand side navigation all the menu items are listed based on endpoints and request types, but it is the summary which is shown next to the request type.
Example: GET A test summary here
Question: is it an acceptable change to add the endpoint path to the left-hand side nav's menu items and to move the summary into a next line?
Example:
GET /some/endpoint
A test summary here
If so, I am happy to create a PR.
The text was updated successfully, but these errors were encountered:
How do you feel about having this behind an option? Having a large API could make the navigation a little unwieldy to navigate, but I agree that sometimes it's easier to just look POST /pets than Add a Pet
Current situation: in the left-hand side navigation all the menu items are listed based on endpoints and request types, but it is the summary which is shown next to the request type.
Example:
GET A test summary here
Question: is it an acceptable change to add the endpoint path to the left-hand side nav's menu items and to move the summary into a next line?
Example:
If so, I am happy to create a PR.
The text was updated successfully, but these errors were encountered: