-
Notifications
You must be signed in to change notification settings - Fork 117
[feat] Change default JSON report file pattern #1480
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1480 +/- ##
=======================================
Coverage 91.72% 91.72%
=======================================
Files 82 82
Lines 12924 12924
=======================================
Hits 11854 11854
Misses 1070 1070 Continue to review full report at Codecov.
|
vkarak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing that's not very nice is that the configuration option must be enabled in order for the --report-file command-line option to have an effect, which is a bit strange. As a user I would expect to get a report if I pass that option. One solution could be to automatically enable reporting if this option is passed. The downside of this is that it will break somehow the consistency of command line options mapping to configuration options. Another decision to make is what should be the default behaviour: generate or not the report. I kind of tend to not generate, but I'm not sure. This decision will also guide us to what would be the best solution to the problem I just described.
Apart from this, we will need to update the documentation.
|
Tested with:
|
vkarak
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm now
Will fix #1476