Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Adding CLI support for Postman import

See original GitHub issue

Following up with #1004, this is a ticket for https://github.com/intuit/karate/projects/3#card-22529475: adding Postman import to Karate.

Like @ptrthomas mentioned, adding a CLI flag to switch on the behavior is simple. Where, though, should the (very little) logic for this functionality live? Inside com.intuit.karate.cli.Main, or should another CLI “utility” class?

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

3reactions

ptrthomascommented, Dec 28, 2019

@babusekaran good question, to be honest I have not explored picocli subcommands yet. I leave it to @Celeo - either one is fine for me. IMO the file extension should be a good enough indicator of the type of import - in case we support more than postman in the future

2reactions

ptrthomascommented, Dec 27, 2019

@Celeo yes I had missed it, it struck me later that a postman import is one of those things that makes more sense for the fat-jar, since anyone who is working with the maven jar would have been doing it via code like you were. so I would actually prioritize the karate-netty CLI.

but the reason I think it makes sense in both places is because the VS Code plugin is really catching on and the debug CLI -d is an example where it is useful for both Maven / Gradle and fat-jar users.