Add precision flag (and config) to control output percentage precision#2991
Merged
ferd merged 1 commit intoerlang:mainfrom Feb 12, 2026
Merged
Add precision flag (and config) to control output percentage precision#2991ferd merged 1 commit intoerlang:mainfrom
ferd merged 1 commit intoerlang:mainfrom
Conversation
fregate
force-pushed
the
coverage_precision_opt
branch
from
139b4c3 to
780c875
Compare
ferd
reviewed
Feb 6, 2026
Collaborator
ferd
left a comment
ferd
left a comment
There was a problem hiding this comment.
Left a bunch of comments, mostly minor things.
Let me know what you think, we'll see how to drive this forward.
fregate
force-pushed
the
coverage_precision_opt
branch
2 times, most recently
from
870836e to
02f45a2
Compare
fregate
force-pushed
the
coverage_precision_opt
branch
from
02f45a2 to
07ba473
Compare
fregate
commented
Feb 9, 2026
ferd
approved these changes
Feb 9, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In big codebases, coverage in integers not precise as sometimes CI needs to show increasing or decreasing coverage.
So in this PR I introduce new flag (config option)
precision, which can control output precision (0..3 digits after point).-p [0..3]or--precision=[0..3]All given numbers are clamped to fit into 0..3 range.
If user provide
0or not providing this flag all numbers renders as truncated to integer (for backward compability).Maximum in 3 digits width was choose for simplify commit (do not recalculate table column width with
verboseflag ouput) and with a look at other coverage systems (for example for C/C++).