Gaiacli tx send/sign doesn't respect the -o flag #3249
Comments
jackzampolin
changed the title
This was referenced Jan 10, 2019
|
I suspect this is not a launch blocker - @jackzampolin can we update labels accordingly then? |
|
@alessio this would not block launch, but a through review of the CLI and updating of commands to respect standard flags is something I would really like to see prelaunch |
5 tasks
alessio
pushed a commit
that referenced
this issue
Jan 23, 2019
gaiad tendermint show-{address,validator} now take --machine-parseable/-m
for machine parseable output.
Closes: #3249
cwgoes
pushed a commit
that referenced
this issue
Jan 24, 2019
* remove --json flag from all commands and CLIContext
gaiad tendermint show-{address,validator} now take --machine-parseable/-m
for machine parseable output.
Closes: #3249
* Revert machine-parseable thing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary of Bug
gaiacli tx sendhas a separate--jsonflag to output a JSON response. In the rest of the SDK we use the--outputflag to induce this behavior. We should switch to using that flag in the tx send command.Steps to Reproduce
For Admin Use
The text was updated successfully, but these errors were encountered: