-
Notifications
You must be signed in to change notification settings - Fork 123
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
Add option to allow coercion of array items #132
Conversation
@iilei this is awesome \o/ could I bother you to rebase? Also, I apologize for the slow turnaround; it's hard to keep on top of open-source and all the exciting things happening at npm, Inc at the same time these days. A good place to chat with me is here, if my turn around is ever slow. A few folks who build node tooling are attempting to pull together a community around the needs of the developer tools community. |
Rebase in progress |
22efc7b
to
2bc2bd4
Compare
@iilei 👍 let me know when this is ready to land; I'm going to make this a BREAKING CHANGE, FYI; since I think it's a change to yargs' contract (albeit a good one). |
eb42a2a
to
348b99c
Compare
@bcoe from my point of view it can be merged 👍 |
@iilei likewise, try this out with |
I am currently investigating on an issue if there is a combination of multiple arrays, configured differently. Please let me take some time to get this sorted out. |
Could someone explain how this option can be used with this: yargs.option('items', {
alias: 'i',
type: 'array',
default: []
}) To coerce the array items to strings, even if something like |
Fixes #6