-
Notifications
You must be signed in to change notification settings - Fork 182
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
Pretty indent --info JSON output (see below for details) #558
Conversation
Changes to make --info much more human readable (while still keeping machine readabilty for anyone foolish enough to be parsing the existing output as text) * change message_to_json to optionally not strip the multiline JSON * use multiline=True for the two places we are printing to the console * make the node list JSON indented
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #558 +/- ##
==========================================
+ Coverage 61.94% 61.96% +0.01%
==========================================
Files 14 14
Lines 2917 2918 +1
==========================================
+ Hits 1807 1808 +1
Misses 1110 1110
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Looks straightforward to me!
Could the output of --info be formatted as valid JSON? Previously, I could extract the desired data using |
Would have been so much simpler to produce pure JSON, which others could then read with a standard Python library and produce output in any format they chose. :-( |
Changes to make --info much more human readable (while still keeping machine readabilty for anyone foolish enough to be parsing the existing output as text)
Old output looked like:
New output looks like