Jesse Michel

Hi @adrianmgg and @RadixSeven, We like both of these ideas! Thank you so much for bringing up this issue. We'll try to get to this soon, but any PRs are...

Definitely worth considering. For the sake of keeping a record, this is the link to the `argparse` description: https://docs.python.org/2/library/argparse.html#argument-groups

Hi @Jane333, Thank you for the question! In our [most recent release](https://github.com/swansonk14/typed-argument-parser/releases/tag/v_1.6.0), we added subparsers! The main challenge for subparsers was to find an elegant and typing-friendly way to pass...

Explicitly setting args to the union type resolves this issue, although it's a little extra work :) ```python args: Union[Args, SubparserA] = Args().parse_args('a --bar 10'.split()) print(args.foo) # code completion works...

Hi @kyprifog, What an interesting thought! For example, ```python class SubparserA(Tap): bar: int class Args(Tap): foo: bool = False def configure(self): self.add_subparser('a', SubparserA, help='a help') # args is of type...

Hi @kyprifog, We see what you're thinking and we think it accords with some of the discussion that people have been having around saving files with nested arguments (https://github.com/swansonk14/typed-argument-parser/issues/40#issuecomment-820230448). While...

This will likely involve generating copatible json.

I don't think we need to provide skeleton code, but otherwise it's annoying.

This would be a dropdown in the parameters section?

on parameters of input layer.