-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add postman import spec #106
base: main
Are you sure you want to change the base?
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
fix: Update test fix: Remove full file path
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 |
This PR focuses on having the Postman Collection import functionality. The following is how one can use this functionality:
Flags
-t/--type
openapi
,postman
-o/--output
spec_file
is 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.