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

At least 1 report directory should be mandatory for parse command #1343

Closed
dkrupp opened this issue Feb 6, 2018 · 1 comment
Closed

At least 1 report directory should be mandatory for parse command #1343

dkrupp opened this issue Feb 6, 2018 · 1 comment
Assignees
Labels
CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands enhancement 🌟
Milestone

Comments

@dkrupp
Copy link
Member

dkrupp commented Feb 6, 2018

Do not accept 0 positional arguments for parse command as it can lead misleading behavior as it will not find reports as either CodeChecker analyze or CodeChekcer check has default output report directory.

So at least 1 positional arguments must be mandatory.

usage: CodeChecker parse [-h] [-t {plist}] [-e {html}] [-o OUTPUT_PATH] [-c]
                         [--suppress SUPPRESS] [--export-source-suppress]
                         [--print-steps]
                         [--verbose {info,debug,debug_analyzer}]
                         [file/folder [file/folder ...]]

Parse and pretty-print the summary and results from one or more 'codechecker-
analyze' result files.

positional arguments:
  file/folder           The analysis result files and/or folders containing
                        analysis results which should be parsed and printed.
                        (default: /home/ednikru/.codechecker/reports)
@dkrupp dkrupp changed the title remove default value of parse command At least 1 report directory should be mandatory for parse command Feb 6, 2018
@csordasmarton csordasmarton added this to the release 6.5.1 milestone Feb 6, 2018
@whisperity
Copy link
Contributor

This heavily contradicts the default behaviour of CodeChecker analyze which will use the folder under the "workspace" for output.

Why are we making it so hard for people who just want to use CodeChecker with default settings?

@csordasmarton csordasmarton added the CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands label Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI 💻 Related to the command-line interface, such as the cmd, store, etc. commands enhancement 🌟
Projects
None yet
Development

No branches or pull requests

3 participants