-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Help suggests order of arguments that halp
does not accept.
#30
Comments
I think you're confusing
So your query |
In that case I think the other guidance is off/inconsistent because in the line above
is the only explanation of also full output for context:
|
I get the confusion. I just checked and in
Maybe moving to a "subcommand" name everywhere would clear things up @orhun ? Side note:
I couldn't find out where you got this output from |
That's just the output of |
I know, I worded that very wrongly haha. What I meant is I can't figure out where in the codebase this output is programmed. I assume it's being auto-generated somewhere seeing I can't find it with |
Ah I see, looks to me like the typical |
I see the issue here. That help/usage text should be somehow "overridable" via clap options I think. Needs a bit of digging. |
Updated the help text in f849305 |
Describe the bug
When run with
--help
or without aCMD
the help suggests the syntaxhalp [OPTIONS] [CMD] <COMMAND>
.But running
halp anycmd plz
which follows that order errors withTo reproduce
Expected behavior
Either the help should not list the arguments in the wrong order (I think that's the proper solution) or it should accept the suggested syntax.
Software information
And likely irrelevant but here you go:
The text was updated successfully, but these errors were encountered: