-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
feat(cli): parse subcommand #724
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #724 +/- ##
=============================================
+ Coverage 61.75% 62.05% +0.29%
- Complexity 720 724 +4
=============================================
Files 177 181 +4
Lines 3655 3697 +42
Branches 594 596 +2
=============================================
+ Hits 2257 2294 +37
- Misses 1100 1104 +4
- Partials 298 299 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
private val marathonfile by option("--marathonfile", "-m", help="Marathonfile file path") | ||
.file() | ||
.default(File("Marathonfile")) | ||
private val parseOutputFile by option("--output", "-o", help="Output for the result of Parse command execution") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add an option for format with only yaml
for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Malinskiy I've added few words that the output format is yaml. Do we need to support other formats?
YAML output format of the PARSE command Co-authored-by: Anton Malinskiy <anton@malinskiy.com>
No description provided.