Skip to content
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

Show request paths in GUI #2486

Open
1 task done
brki opened this issue Jun 19, 2024 · 0 comments · May be fixed by #2520
Open
1 task done

Show request paths in GUI #2486

brki opened this issue Jun 19, 2024 · 0 comments · May be fixed by #2520
Labels
enhancement New feature or request

Comments

@brki
Copy link

brki commented Jun 19, 2024

I have checked the following:

  • I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add

Proposal: Have a per-collection option to show the the request path instead of the request name in the GUI.

Bruno currently uses the summary field to name requests when importing from an OpenAPI specification file.

When searching for an endpoint in a long list, it is often easier if we can see the path instead of (or in addition to?), the summary.

e.g. it can be easier to visually scan the list of requests and find

(POST) /v1/compute/section-a/object-type-b,

as opposed to a free text field from the OpenAPI summary field like

(POST) Compute all the derived attributes of the selected object-type-b

Mockups or Images of the feature

collection 1
  GET /v1/foo/bar
  POST /v1/foo/bar
collection 2
  GET get a foo bar
  POST create a foo bar
@brki brki added the enhancement New feature or request label Jun 19, 2024
@david-narbona david-narbona linked a pull request Jun 27, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant