You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, I have a root command with sub-command run. And sub command run have a nested sub-command test.
Suppose that my command line called foo. The problem is if I use foo set, it will print the error message unknown command "set" for "foo". But if I use a wrong command like foo run set, it will just print the usage rather than unknown sub command "set" for "run".
My question is how can I get the nested sub-command unknown message gracefully just like command?
The Cobra project currently lacks enough contributors to adequately respond to all issues. This bot triages issues and PRs according to the following rules:
After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed.
You can:
Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening
For example, I have a root command with sub-command
run
. And sub commandrun
have a nested sub-commandtest
.Suppose that my command line called
foo
. The problem is if I usefoo set
, it will print the error messageunknown command "set" for "foo"
. But if I use a wrong command likefoo run set
, it will just print the usage rather thanunknown sub command "set" for "run"
.My question is how can I get the nested sub-command unknown message gracefully just like command?
#706
The text was updated successfully, but these errors were encountered: