-
Notifications
You must be signed in to change notification settings - Fork 843
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
Subcommands should show help with no args #809
Milestone
Comments
Can now use |
I will propose a pull request that I think fixes this. |
mpilgrem
added a commit
to mpilgrem/stack
that referenced
this issue
Jul 20, 2022
For example, before the change, `stack ls` yields only: ~~~ Missing: COMMAND Usage: stack.exe ls COMMAND [--setup-info-yaml URL] [--snapshot-location-base URL] [--help] List command. (Supports snapshots, dependencies and stack's styles) ~~~ After the change, `stack ls` yields the more informative: ~~~ Usage: stack.exe ls COMMAND [--setup-info-yaml URL] [--snapshot-location-base URL] [--help] List command. (Supports snapshots, dependencies and stack's styles) Available options: --setup-info-yaml URL Alternate URL or relative / absolute path for stack dependencies --snapshot-location-base URL The base location of LTS/Nightly snapshots --help Show this help text Available commands: snapshots View local snapshot (default option) dependencies View the dependencies stack-colors View stack's output styles stack-colours View stack's output styles (alias for 'stack-colors') Run 'stack --help' for global options that apply to all subcommands. ~~~ Also deletes the case: ~~~haskell Failure _ | null args -> withArgs ["--help"] (execParser parser) ~~~ as `stack` (without more) is now handled without it. Tested by building and using Stack, including using Stack with scripts and `stack script`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This subcommand currently isn't too helpful:
Running
stack
by itself producesstack --help
, but seems that subcommands still have this issue.The text was updated successfully, but these errors were encountered: