-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Better key output #886
Better key output #886
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #886 +/- ##
========================================
Coverage 67.01% 67.01%
========================================
Files 68 68
Lines 3614 3614
========================================
Hits 2422 2422
Misses 1008 1008
Partials 184 184 |
updated docs for new key work
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.
Tested ACK
I like the output
flag, we should make that standard on any command that should be both human & machine readable - which should be all commands?
If tabular outputs are common, we could use a library - e.g. https://github.com/olekukonko/tablewriter - instead of manual '\t' characters.
@cwgoes thanks! Side comment - unless a library is doing something otherwise pretty unique and important its better for use to not add an extra import and add some more code internally - the big risk is that malicious code gets added to another library and is somehow able to infiltrate / introduce security holes in the cosmos codebase without anyone noticing - I think something as basic as the use of \t shouldn't require an import |
Could be mitigated by version pinning libraries (we'll never need to update the tabulation library) - but agreed in general. |
We're supposed to migrate to Bech32Cosmos. #263 |
Better key output:
gaiacli keys show foo
gaiacli keys show foo --output=json