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
Round MSI scores #1190
Round MSI scores #1190
Conversation
theofidry
commented
Mar 20, 2020
•
edited
edited
- Better min-score and min-covered-score validation
- Round min-score & min-covered-score values
- Round calculated MSI & covered code MSI
IIRC the original proposal explicitly left the whole precision intact arguing that for sufficiently large project leaving only two digits past the decimal point might not be enough. |
I'm fine with increasing it by one more digit for example, but having 10 of them is ridiculous :) |
How do you think if we'd detect the precision as provided by a user, then display them as such? |
exactly. Not sure why we reverting it here. What's the point? You see this only on CI, and only when it fails. |
3 reasons:
I thought about it, but there is the risk that people just use What about having a more sensible rounding, like 3 digits? I doubt it makes sense to have more. If you have such a large codebase, you probably are not running it on the whole codebase anyway |
Cool. Then we display it with no digits past decimal point, right? Here's the original issue: #694 |
#694 describes a different problem though: rounding without any digit past the decimal point at all whereas this PR is rounding with 2 digits past the decimal point How about we try to get the precision from the user but default to 2? |
As in |
Updated :) |