Support json exporting for list bootstrapped (bugfix)#2501
Conversation
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #2501 +/- ##
==========================================
- Coverage 58.93% 58.93% -0.01%
==========================================
Files 476 476
Lines 48035 48037 +2
Branches 8576 8577 +1
==========================================
Hits 28309 28309
- Misses 18835 18836 +1
- Partials 891 892 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fernando79513
left a comment
There was a problem hiding this comment.
Thanks for the explanation.
I still think mixing the custom syntax that accepts whatever and json in the same command is a bit weird.
If you had a typo in the json field, you will have a bunch of typos and no error, where usually you may expect a type error:
$ checkbox-cli list-bootstrapped --format jsn smoke
jsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsnjsn
But if we plan to get rid of this in the future, I think its okay
Description
json exporting is super useful, as it can be piped easily into other tools like
jqor loaded to do post processing without writing a parser.Resolved issues
N/A
Documentation
Added to option help
Tests
Test it via