-
Notifications
You must be signed in to change notification settings - Fork 65
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
add tip for the JSON output #266
Conversation
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.
Awesome, we had missed realizing this problem. Thanks for helping us improve the documentation!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #266 +/- ##
=======================================
Coverage 87.60% 87.60%
=======================================
Files 63 63
Lines 7916 7916
=======================================
Hits 6935 6935
Misses 799 799
Partials 182 182 ☔ View full report in Codecov by Sentry. |
@sonalmahajan15 seems some issue with the golden test |
@madneal , yes, something seems to be wrong. We'll look into it and merge the PR. |
Yeah, I think we'll have to wait for golang/go#61324 to have an importable checker API to use. |
I'm updating your branch since we recently fixed the CI issue, and we'll need those changes in order for CI to pass :) |
Thanks @madneal for the contributions! |
This PR provides a tip when output as JSON due to the current default
pretty-print
flagCurrent Issue
For the orginal json flag provided by checker.go, it's impossible to get
analysisflags.JSON
from nilaway. There is a conflict bettwen thepretty-print
andjson
output currently due to the codenilaway/nilaway.go
Line 43 in e902884
As the default
conf.PrettyPrint
is true, so the output will be messy when try to output as json.