usebruno / bruno

Opensource IDE For Exploring and Testing Api's (lightweight alternative to postman/insomnia)
https://www.usebruno.com/
MIT License
25.4k stars 1.16k forks source link

Large Postman Imports are Incomplete #955

Closed solsticesurfer closed 2 months ago

solsticesurfer commented 10 months ago

What I was trying to do

Import a large Postman collection into Bruno

What was supposed to happen

All folders and requests should have been imported

What happened

Out of 24 folders and 191 requests, only 21 folders and 169 requests were imported. No errors were reported to indicate that the full collection could not be imported. Import file size was ~200KB

The failure was caused by two folders that have the same name at the same folder level in Postman. Postman stores collections as data, whereas Bruno stores collections as a file structure. Since you cannot have two folders at the same directory level with the same name, the import of that second folder fails. However, this is done without any notification to the user.

There should be a check during the import of a folder to ensure that the folder does not exist. If it does, either notify the user or, possibly better, add a number to the end of the folder so that the import can be successfully continued. The user should be notified of this so that they can then go in and clean up the second folder as needed.

gonzark commented 10 months ago

Facing the same issues.

I want to import a Postman collection that has 3 folders in it:

I'm only seeing the V1 folder after importing it into Bruno

Thanks!

hinnerkoetting commented 5 months ago

I just had the same issue. It seems to happen if there are nested folders in the collection. In my case my postman-collection looked like this:

5 - Folder
  5.1 Sub-Folder
    5.2.1 Sub-Request1
    ...
  5.0.1 Request1

I could work around this issue by copying requests from the sub-folder to the top-level folder and then deleting the sub-folder.

sanjai0py commented 2 months ago

Closing this issue as the PR fixing the bug had already been merged and released in v1.3.0