feat: Split name and field_name on Arg object. #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #46.
At current moment,
name
field is relatively inaccessible except for the "manual construction" usecase. It's otherwise able to be specified. Thus using such a valuable, generic name seemed unncessary. Thusname
->field_name
.Withname
freed up, "name" seems like a decent name for the equivalent ofmetavar
in argparse. I supposename
could be confused with short/long?I looked at Clap which uses value_name, which i rather like, and which seems to me to pair well with
field_name
. certainly better than metavar