-
Notifications
You must be signed in to change notification settings - Fork 332
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
Include chain-id in hermes query clients output #995
Conversation
Can we use a struct here instead of a tuple, to give names to the data?
|
A few comments:
|
@romac @ancazamfir thank you for the review! Most comments should be addressed. |
thanks, could you please update the description? |
Done! |
Not sure if we should introduce
|
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 good! A few comments around help, debugs, etc.
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 good, thanks Adi!
* Added option to include chain ids. Client ids sorted by counter. * Changelog * Address comments * Removed useless gumdrop derive attributes. * Better info log message * Better names for output struct. Using ChainId instead of String. * Lowered log level to debug * Succint help messages. * Moved ClientId::suffix() into cosmos.rs
Closes: #992
Description
Three improvements for
hermes query clients
:The option
-o, --omit-chain-ids
can disable this behavior and print only the client identifiers.hermes query clients
is now sorted by the suffix of client ids-s, --src-chain-id
hermes query clients ibc-0 -s network5 May 26 17:11:12.313 INFO ibc_relayer_cli::commands::query::clients: printing identifiers of all clients hosted on chain ibc-0 which target chain network5 Success: [ ClientId( "07-tendermint-6", ), ]
For contributor use:
docs/
) and code comments.Files changed
in the Github PR explorer.