-
Notifications
You must be signed in to change notification settings - Fork 116
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
Option groups, à la command groups #270
Comments
Not at the moment, I only added command groups recently and haven't generalised it. There's this #231 PR up, but I haven't had the time to go through and offer all my thoughts. |
Thanks for the status update! Let me know if there's any way I can help. This is something I would love to use downstream. :) |
Just adding my voice in favour of this feature. :) Sadly #231 was closed :( |
georgefst
added a commit
to georgefst/monpad
that referenced
this issue
Sep 22, 2023
Inspired by pcapriotti/optparse-applicative#484. This is actually pretty neat, even if the help text is slightly odd. This is probably the best interface we can have without some form of "default command" as discussed there, or option groups (pcapriotti/optparse-applicative#270).
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can group commands with the
commandGroup
option. Can we do the same with options? I have rather a lot of them and would like to separate them with whitespace and headings.Hopefully this is already possible and I just missed it in the docs.
Thank you!
The text was updated successfully, but these errors were encountered: