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

Invalid argument type for --config_file when using click==8.1.7 #12

Open
aropan opened this issue Jun 3, 2024 · 0 comments · May be fixed by #13
Open

Invalid argument type for --config_file when using click==8.1.7 #12

aropan opened this issue Jun 3, 2024 · 0 comments · May be fixed by #13

Comments

@aropan
Copy link

aropan commented Jun 3, 2024

When using click==8.1.7 the --config_file argument have a BOOLEAN type, which causes an error when trying to pass --config_file argument:

> coverage-lcov --config_file PATH/TO/.coveragerc
Usage: coverage-lcov [OPTIONS]
Try 'coverage-lcov --help' for help.

Error: Invalid value for '--config_file': 'PATH/TO/.coveragerc' is not a valid boolean.
Usage: coverage-lcov [OPTIONS]

Options:
  --data_file_path TEXT    Path to .coverage file
  --output_file_path TEXT  lcov.info output file path
  --config_file BOOLEAN    Path to .coveragerc file
  --relative_path          Use relative path in LCOV output
  --preview                Preview LCOV output
  --help                   Show this message and exit.

The --config_file argument should have a TEXT type instead, as it did for click==7.1.2, where it works correctly:

> coverage-lcov --help
Usage: coverage-lcov [OPTIONS]

Options:
  --data_file_path TEXT    Path to .coverage file
  --output_file_path TEXT  lcov.info output file path
  --config_file TEXT       Path to .coveragerc file
  --relative_path          Use relative path in LCOV output
  --preview                Preview LCOV output
  --help                   Show this message and exit.
@aropan aropan linked a pull request Jun 3, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant