We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
summary
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,
(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
collection 1 GET /v1/foo/bar POST /v1/foo/bar collection 2 GET get a foo bar POST create a foo bar
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I have checked the following:
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
The text was updated successfully, but these errors were encountered: