You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, tapify always gets the script description for -h from the docstring of the input.
When the input is a class, its docstring usually doesn't tell you what the script is going to do. The class usually represents data that's inputted to a function/method.
The user should be able to pass in a description manually through a new kwarg in tapify, description, which defaults to the current behavior: get the description from the input's docstring.
I'll submit a PR for this in a few days or weeks in case no else gets to it
The text was updated successfully, but these errors were encountered:
Currently,
tapify
always gets the script description for-h
from the docstring of the input.When the input is a class, its docstring usually doesn't tell you what the script is going to do. The class usually represents data that's inputted to a function/method.
The user should be able to pass in a description manually through a new kwarg in
tapify
,description
, which defaults to the current behavior: get the description from the input's docstring.I'll submit a PR for this in a few days or weeks in case no else gets to it
The text was updated successfully, but these errors were encountered: