Issues noticed exported collection when exported as Postman Collection

[akhot09]

I have checked the following:

• I use the newest version of bruno.
• I've searched existing issues and found nothing related to my issue.

Describe the bug

When we perform export from Bruno API client, using option as "Export" --> "Postman Collection" noticed following issues in exported file:

1. Sequence of API requests is not maintained as arranged in API client, rather its exported in alphabetical order which is not correct. As a part of chaining of requests we made need to run API call 1 first and then API call 2 due to dependency of data. If now post export - if API call 2 is documented before API call 1 then when run via Postman API client or Newman CLI, scripts will fail as sequence is not correct.
   
   As per screen shot, "ping" is first request in collection/collection folder but when we perform "Export" ---> "Postman Collection" the "ping" API request has been sequenced in last due to alphabetical order.
2. Also, "auth" JSON object/ JSON parameter is missing from exported file- (i.e. exported using option "Export" - "Postman Collection") across all API request wherein Auth is selected as "Bearer Token" for each of API request.
3. Also, all issues mentioned / captured in below ticket are also reproducible in exported file (wherein file is exported as "Postman Collection" from Bruno API client)
   Export Collection as Postman Collection #2496

.bru file to reproduce the bug

NA

Screenshots/Live demo link

NA

[Oliver-Piorun]

Sequence of API requests is not maintained as arranged in API client, rather its exported in alphabetical order which is not correct. As a part of chaining of requests we made need to run API call 1 first and then API call 2 due to dependency of data. If now post export - if API call 2 is documented before API call 1 then when run via Postman API client or Newman CLI, scripts will fail as sequence is not correct.

Can confirm. Simply saving requests will also reorder them in alphabetical order for me. It looks like v1.20.1 introduced the issue I mentioned. Your issue has to be a different one since you created the issue before v1.20.1 was released.

Greetings 😊