-
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
AutoCLI Enhancements #18310
Labels
Comments
20 tasks
12 tasks
12 tasks
1 task
12 tasks
12 tasks
12 tasks
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AutoCLI can replace almost all Cosmos SDK commands. However, there are still some that are staying in the SDK because using AutoCLI will give a worse UX. In order to fix that, the following features must be implemented:
Commands can now use flags and positional arguments. Some commands may have a better UX if the arguments were entered in a prompt. We should support prompt as an autocliNeeds a hack when initializing the command. AutoCLI provides a good api to do that manually since Move prompt to client/v2 #17222RpcCommandOptions
Authority gated commands are currently supported, but do not give a great UX as it will by default just broadcast the message. This is unpractical for commands that are expected to be governance/group proposals. We should add an option to
RpcCommandOptions
commands to signal a command is supposed to be a proposal and have AutoCLI request the necessary proposal fields as well and broadcast a proposal instead of the message directly.Currently, an inner message in a proto, must be passed as a json in an autocli argument/flag. We should support a syntax that allows to define an inner message field as a positional argument or flag:
cosmos-sdk/x/circuit/autocli.go
Line 49 in 862e233
The text was updated successfully, but these errors were encountered: