How to tell which subparser was called? about typed-argument-parser HOT 6 CLOSED

Ah, perfect, yes that's exactly what I was looking for! I didn't realize I could use the argparse keyword but that makes a lot sense. Thanks very much!

from typed-argument-parser.

@mo22 could you define those Command and Subcommands classes for us? Trying to come up with something that plays a little better with the Pyright linter.

from typed-argument-parser.

Hi @anniecherk,

Thank you for the carefully worked example. If I understand it correctly, this has been solved for argparse and as a wrapper for argparse, Tap supports the same functionality. Here's a worked example:

class SubparserA(Tap):
     bar: int  # bar help
 
class SubparserB(Tap):
     baz: Literal['X', 'Y', 'Z']  # baz help
 
class Args(Tap):
     foo: bool = False  # foo help

     def configure(self):
         self.add_subparsers(help='sub-command help', dest="subparser_name")
         self.add_subparser('a', SubparserA, help='a help')
         self.add_subparser('b', SubparserB, help='b help')
         
args = Args().parse_args(['a', '--bar', '1'])

print(args.subparser_name)  # The result is "a"

Let me know if this resolves the issue :).

from typed-argument-parser.

Glad it worked out! Happy tapping!

from typed-argument-parser.

Hey, great project! I did something similar a while back and solved the subparser issue by using something like this:

    class Args(Command):
        verbose = Argument(bool)
        cmd = Subcommands(Union[
            ArgsListZones,
            ArgsGetNameservers,
            ArgsDeleteZone,
            ArgsExportZone,
            ArgsImportZone,
            ArgsImportYml,
            ArgsPurgeYml,
        ])

this way the selected command could be checked by python idioms and would also have the correct typings

from typed-argument-parser.

also a @tap.Positional decorator might make configure not needed so often

from typed-argument-parser.