Add postman import spec - #106
Conversation
9bce787 to
b0d4d84
Compare
|
Thanks for this very important feature! I'm on a break at the moment but will try to take this for a spin within the next couple of weeks. |
f386be9 to
7f172f2
Compare
7f172f2 to
e0cb6a5
Compare
|
Pushed a fix for a crash I got when I downloaded a sample Postman collection - Also from testing it seems like the directory structure is not being respected? |
Sorry been quite busy lately, will work on this when I get time |
|
Hello, guys. Any predictions for closing this pull request? This is a very good feature for switching easily to posting :D |
Ah, sorry about the delay, was working 2 jobs and recently my main job wasn't doing well financially so I resigned and busy doing interview preparations again as well as doing my side job. Will probably be able to fix this up when I have free time, probably in a month. It is only missing a test, so if someone can help add it in, would be appreciated. |
fix: Update test fix: Remove full file path
bdec523 to
869e791
Compare
|
@darrenburns Hey Darren, I fixed up the test and also fixed up the import spec function some more with the latest changes. Let me know what you think, thanks and sorry for the delay |
chore: Fix format chore(doc): Remove Importing from Postman section in README
30b5db1 to
f3b6b3b
Compare
|
Thanks for this. I'll try to review it tomorrow. |
|
Sorry for the delay - I fixed up a few issues I found in this PR (the collection was being saved twice in 2 different locations, as was the README). Should be able to merge and release this soon (likely this week). |
This PR focuses on having the Postman Collection import functionality. The following is how one can use this functionality:
Flags
-t/--typeopenapi,postman-o/--outputspec_fileis located.Usage:
I wrote a test for it but I am not sure how to include it in the test workflow, the test passes when I run
NOTE: I have tested it with Postman API Collection and my company's postman collection, seems to all work.