Allow requests with the same name (but different HTTP methods)

[SergiyKolesnikov]

I have checked the following:

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

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

[crestoff]

@SergiyKolesnikov great idea!

[Susccy]

I second this. Unique request names make sense, but only if the name is calculated as a combination of method type + name.

So having

• GET method
• POST method

should be allowed, but

• POST method
• POST method

should not be allowed.