-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename alias
option to shortFlag
#109
Comments
Why not just "short"? |
I think |
I think the {
flags: {
unicorn: {
aliases: ['-u']
}
}
}
// same with
{
flags: {
unicorn: {
shortFlag: 'u'
}
}
} |
@LitoMore It's not. |
Good point. I agree. |
{
options: [
{
flags: ['unicorn', 'u'],
type: 'string',
default: 'love',
},
{
flags: ['force', 'f'],
type: 'boolean',
},
}
} This flattens the structure and eliminates a need entirely for a second term altogether. 'Options' is a little confusing here, admittedly, since it lives inside the Meow options object. I propose that word however, to be consistent with CLI terminology: a CLI has arguments and options. Options are specified by 'flags'. |
@BendingBender That would be a big breaking change and IMHO not for the better. I also want to make a clear distinction between an alias and a short-flag. |
I never liked the
alias
wording, which was inherited fromminimist
. I think it would be better to have a more explicit and semantic name calledshortFlag
.We could then also add a
aliases
option where users can specify actual aliases and not just limited to one:Could use some feedback on this proposal.
The text was updated successfully, but these errors were encountered: