client: names in compact output when listing resources#1443
Conversation
|
Sounds good. Is there a special reason for the square brackets? I would just drop them, so the match can be copy & pasted into |
|
I went with the brackets because they indicate that the name is optional when adding as a match and for consistency to the verbose output. I don't have a strong opinion about either, should the verbose output be changed as well? |
d2a0acb to
b17f570
Compare
|
I would appreciate feedback here. |
Signed-off-by: Felix Zwettler <Felix.Zwettler@duagon.com>
b17f570 to
37d7d22
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1443 +/- ##
======================================
Coverage 46.0% 46.0%
======================================
Files 180 180
Lines 14462 14462
======================================
Hits 6654 6654
Misses 7808 7808
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Description
This adds that resources names are printed in the compact output of the
labgrid-client resourcescommand.For example, instead of:
the output becomes
which makes it easier to differentiate between resources that have the same class.
The alternative would be to enable verbose printing with
labgrid-client -v resources, but that adds a lot of other information and makes is quite hard to pick out the name quickly.At least in my experience the resource name is the only info that I need 95% of the time, so I think it would be beneficial to add it to the default output.
What do you think?