-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
fix: query txs command adds output flag #9540
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9540 +/- ##
=======================================
Coverage 60.58% 60.59%
=======================================
Files 589 589
Lines 37228 37217 -11
=======================================
- Hits 22556 22550 -6
+ Misses 12728 12723 -5
Partials 1944 1944
|
@@ -198,8 +198,7 @@ $ %s query txs --%s 'message.sender=cosmos1...&message.action=withdraw_delegator | |||
}, | |||
} | |||
|
|||
cmd.Flags().StringP(flags.FlagNode, "n", "tcp://localhost:26657", "Node to connect to") | |||
cmd.Flags().String(flags.FlagKeyringBackend, flags.DefaultKeyringBackend, "Select keyring's backend (os|file|kwallet|pass|test)") |
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.
Technically speaking removing --keyring-backend
is a client-breaking change, so should wait RC before getting merged.
However, I agree with @chengwenxi that this flag is non-sensical here, and I'm pretty sure no-one uses it. So I'm actually okay to merge this PR. Any strong opinions @robert-zaremba and @ryanchristo ?
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.
I think it would be safe to merge. Not sure how one would use it in this situation anyways.
Description
Query txs
command addsoutput
flag, to make it consistent with other query commands.Delete unused flag
keyring-backend
.Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change