Skip to content
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

Mention .option in README #57

Merged
merged 1 commit into from
Feb 6, 2015
Merged

Mention .option in README #57

merged 1 commit into from
Feb 6, 2015

Conversation

eush77
Copy link
Contributor

@eush77 eush77 commented Oct 13, 2014

No description provided.

@bcoe
Copy link
Member

bcoe commented Feb 6, 2015

@eush77 I don't know how I feel about adding a top-level section-header for an alias, what do you think of instead adding a note at the end of the section, something like:

can be aliases as option.

@eush77
Copy link
Contributor Author

eush77 commented Feb 6, 2015

@bcoe I just wanted to be consistent with how aliases are documented now.
Take a look at https://github.com/chevex/yargs#demandkey-msg--boolean.

@bcoe
Copy link
Member

bcoe commented Feb 6, 2015

@eush77 +1 for consistency 👍

bcoe added a commit that referenced this pull request Feb 6, 2015
@bcoe bcoe merged commit 86fd383 into yargs:master Feb 6, 2015
@eush77 eush77 deleted the option-readme branch February 6, 2015 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants