Type safe way to access subparser arguments?

[aucampia]

As far as I can tell from your tests you access subparser arguments on the main parser class instead of the subparsers class, is this really how you expect people to do it?

typed-argument-parser/tests/test_subparser.py

Lines 180 to 184 in eb55a9b

	args = Args().parse_args('b --blaz'.split())
	self.assertFalse(args.foo)
	self.assertFalse(hasattr(args, 'baz'))
	self.assertFalse(hasattr(args, 'biz'))
	self.assertTrue(args.blaz)

Is there a reason this is not documented?

Would it not be better to just say that this library does not support subparsers, because the current support really seems more of a nusiance than anything else. I think if I knew up front that the support for subcommands is in the state that it is I would not have tried using it and it would have saved me a lot of time.

[oscarkey]

See #69

[swansonk14]

Hi @aucampia,

Thank you for bringing up this issue! Tap implements subparsers this way because we match how Python's built-in argparse library handles subparsers: https://docs.python.org/3/library/argparse.html#argparse.ArgumentParser.add_subparsers

We agree that this is not ideal and have thought about alternatives. Please feel free to give us suggestions in this document or in this issue.

Best,
Jesse and Kyle