I have checked the following:
Describe the feature you want to add
For REST resources that support multiple HTTP methods, it may be convenient and more readable to give the requests the same name (e.g., the name of the resource). The requests can still be differentiated by the corresponding method.
Implementing this feature will also make it easier to import collections from other API clients that have this feature too. As described in the issue #799.
Bruno stores requests in .bru files having the same name as the requests. To prevent name collisions the names of these files can be prefixed with the corresponding HTTP methods. I tried prefixing files like that by hand and it worked as can be seen in the screenshot.
Mockups or Images of the feature
I have checked the following:
Describe the feature you want to add
For REST resources that support multiple HTTP methods, it may be convenient and more readable to give the requests the same name (e.g., the name of the resource). The requests can still be differentiated by the corresponding method.
Implementing this feature will also make it easier to import collections from other API clients that have this feature too. As described in the issue #799.
Bruno stores requests in .bru files having the same name as the requests. To prevent name collisions the names of these files can be prefixed with the corresponding HTTP methods. I tried prefixing files like that by hand and it worked as can be seen in the screenshot.
Mockups or Images of the feature