ishell VS urfave/cli

I want to build a command line tool with context-sensitive completion. This is important because it allows interactive exploration of the options -- both of the application and of the current data model -- available to the user.

So far this is what I've found.

https://github.com/desertbit/grumble

https://github.com/spf13/cobra

https://github.com/urfave/cli

https://github.com/abiosoft/ishell

I would like to know people's experiences and recommendations in building such an app in go.

Maybe something like: https://github.com/abiosoft/ishell

Your question is a little unclear. For any serious command prompt, it becomes almost required to build one from scratch as libraries tend to have too many constraints that prevent advanced use cases.

Can you use a framework like urfavecli https://github.com/urfave/cli? This will auto-update every time it detects a new version from your CLI's GitHub repository

I use https://github.com/urfave/cli for local development over cli parameter inside docker over envs

....\Softwares\go\src\prysm\cmd\prysmctl\checkpointsync\cmd.go:3:8: cannot find package "github.com/urfave/cli/v2" in any of:

urfave/cli - A simple, fast, and fun package for building command line apps in Go;

and probably something else will be added in the future. The final kind of launch command would like to see such djob [options] - command. Command is the command (with arguments to run). -- should separate the arguments of the utility from the arguments of the program to run. There are several excellent solutions for working with command-line arguments, such as spf13/cobra or urfave/cli. But they’re good for building an interface out of a lot of commands, and for one (as in my example) they’re redundant. So I used the flag library. I have defined the following structure with arguments:

There are alternatives available for Cobra as well i.e. mitchellh/cli, go-flags, urfave/cli etc.

https://github.com/urfave/cli - A Golang package used to structure the CLI.