Skip to content
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

Is it worth to print stack trace with help usage? #57

Closed
sviridov-alexey opened this issue Feb 19, 2021 · 1 comment
Closed

Is it worth to print stack trace with help usage? #57

sviridov-alexey opened this issue Feb 19, 2021 · 1 comment

Comments

@sviridov-alexey
Copy link
Contributor

I believe stack trace is not very usable information for end-user. But on other hand it affect usability of program

Exception in thread "main" java.lang.IllegalStateException: Value for argument project-key should be always provided in command line.
Usage: hosting versions options_list
Arguments: 
    project-key -> key of project which site will belong to { String }
    site-name -> hosted site name { String }
Options: 
    --offset, -o [0] -> start line { Int }
    --page-size, -s [40] -> number lines to show { Int }
    --help, -h -> Usage info 

        at kotlinx.cli.ArgParser.printError(ArgParser.kt:348)
        at kotlinx.cli.ArgParser.parse(ArgParser.kt:637)
        at kotlinx.cli.ArgParser.parse(ArgParser.kt:642)
        at kotlinx.cli.ArgParser.parse(ArgParser.kt:642)
        at kotlinx.cli.ArgParser.parse(ArgParser.kt:523)
        at circlet.cli.MainKt.main(main.kt:20)
@LepilkinaElena
Copy link

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants