Add --precision option to report command #982
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks, I'll take a look. Don't forget that you can put settings into tox.ini, setup.cfg, or pyproject.toml files also. |
|
Thanks, I finished it up in 916a0c9 |
|
This is now released as part of coverage 5.2. |
This was referenced Jul 6, 2020
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a
--precision <N>CLI option tocoverage report, so you don't have to write a.coveragercfile if you only want to adjust the precision.Note: I did a few ad-hoc tests and those ran fine, but I couldn't get the test suite to pass. Since I didn't want to spend too much time on this I decided to submit the PR as-is. Hopefully you can fix the failing tests easily, but otherwise I won't be too embarrassed if this gets rejected.