-
Notifications
You must be signed in to change notification settings - Fork 72
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
Better defaults for boolean flags #245
Comments
@sushantmimani hey! I would like to work on this issue, and if you could provide more information, that would be great. Thanks in advance. |
Hi @aserputov! Sure. Using
What we want it to look like is:
One way to do it would be to change |
Please note that this is targeted at v3.0, so your branch will need to be branched off from the |
Sounds good to me. I would like to try it. Thank you. |
Sounds good! I've assigned this issue to you. |
* Upgrade click to latest * Perform some pathing magic in tests to ensure it matches output * Update CLI help output for docs * Add a changelog entry about the click upgrade * Fix PR # for click update * Another shot at fixing Windows tests * Match the path resolution to the latest version of click * Move the output_dir calculation inside the context manager * Tests become much simpler when you read their output properly. * Remove the unused import to appease pylint
Fixed in #292 |
🐛 Bug Report
Boolean flags such as
--compact / --no-compact
withDefault: False
is very confusing.To Reproduce
tartufo -h
Expected Behavior
Should show
Default: --no-compact
for--compact / --no-compact
and similar for other boolean flagsThe text was updated successfully, but these errors were encountered: