Import and Conversion Results in Folders with no name

[eabrouwer3]

Describe the bug
When I import my openapi spec sheet, I end up with some folders in my collection with no name. For instance, inside the user folder, I will have a few folders that should be there, and then a blank folder with a couple of the operations that should be just under the user folder. Here is a picture for reference.

When I convert the file using openapi-to-postman, the resulting file under the user directory has a schema error that pops up when I roll over it in my IDE that says Missing required property 'request'. When I convert the file manually using APIMATIC, for example, I don't get any such problems. It just works.

To Reproduce
Here's a sample postman json file that gets created upon conversion using the openapi-to-postman library: https://gist.github.com/eabrouwer3/361e20f70310e748c3918cf0ff1bec2d

I have a feeling the problem has to do with lines 13 and 40 where there is a 3rd empty path string. Is that because I have backslashes at the end of my routes and that's confusing the converter? I'm using Django on the backend, and they require there to be a backslash for the urls, or at least that's how it's set up in our system.

Here's a sample openapi json file that reproduces the problem: https://gist.github.com/eabrouwer3/fc62a214c50f6f8128a4bfdc8dd52ff5

Expected behavior
The file to be converted and imported without the above described probems. No folders with no names, and no errors when trying to put the converted postman json file to the Postman API.

App information (please complete the following information):

• Running as: Native app
• Postman Version: 6.7.1
• OS: Linux Ubuntu 18.04

Any push in the right direction would be greatly appreciated. Thanks in advance!

[eabrouwer3]

Sorry that the links stopped working. I changed my GitHub username, so the links changed. Is there any progress report on this bug @abhijitkane?

[abhijitkane]

@eabrouwer3 Will include this fix in the next Postman release. For now, removing the trailing slash from the /user/stuff/ should work.

[abhijitkane]

PR #68 should address this

[eabrouwer3]

Thanks! I'll wait for the next release and let you know if it fixes it.

[abhijitkane]

@eabrouwer3 This has been addressed in v7.2.1 of Postman.

[eabrouwer3]

Yup! Looks good to me!