Skip to content
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

Investigate subparsers with no arguments #17

Open
2 tasks
jmgate opened this issue Jul 10, 2023 · 0 comments
Open
2 tasks

Investigate subparsers with no arguments #17

jmgate opened this issue Jul 10, 2023 · 0 comments
Labels
Type: Task Something we need to do that doesn't fit any other type.

Comments

@jmgate
Copy link
Collaborator

jmgate commented Jul 10, 2023

Description

I suspect we may have a bug in that reverse_argparse likely doesn't correctly handle the case of a subparser with no argument, e.g., when the subcommand is simply mapped to a function. Need to

  • Develop one or more test cases to prove the point.
  • Fix the unparsing of nested parsers for such situations.
@jmgate jmgate added the Type: Task Something we need to do that doesn't fit any other type. label Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Task Something we need to do that doesn't fit any other type.
Projects
None yet
Development

No branches or pull requests

1 participant