swansonk14

Hi @zamirkhan, thanks for the question! I remember I ran into an issue like this with `p_tqdm` a long time ago and actually stopped using/developing `p_tqdm` for a little while...

Hi @Effervex, Thank you for raising this issue! We think this is a good idea and propose to implement it by adding a flag to [`load`](https://github.com/swansonk14/typed-argument-parser/blob/main/tap/tap.py#L645) and [`from_dict`](https://github.com/swansonk14/typed-argument-parser/blob/main/tap/tap.py#L597) and modifying...

Hi @ari-s, We have implemented a similar idea to your desired feature as of `Tap` version 1.8.0: https://github.com/swansonk14/typed-argument-parser/releases/tag/v_1.8.0. We call it `tapify` and while it's not a decorator, it does...

Hi @cjmcgill, We agree that this is a great idea! We hope to tackle this soon. Best, Jesse and Kyle P.S. https://github.com/swansonk14/typed-argument-parser/issues/89 happy one year anniversary

Hi @juliangilbey, We agree that it would be really nice to have a single name that does not conflict with `tap.py`. However, we think that keeping backwards compatibility and the...

Hi @TibiIius, This has now been fixed in https://github.com/swansonk14/typed-argument-parser/pull/148. Thank you again for raising this issue! Best, JK

Ensure that the arguments in the help string are in the same order as they are in the function.

Hi @qubidt, This seems like a great extension of `tapify`! We hope to tackle this soon but would appreciate any PRs. Thanks, Jesse and Kyle

Hi @user202729, Thank you for suggesting this feature! We agree that this would be a nice addition. We would welcome a PR from you or anyone else interested in implementing...

Hi @Cnoor0171, Thank you for the suggestion! We agree that source code parsing is not ideal, but we still think that comment-based help strings provide the cleanest user experience and...