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

Handling option --parse #154

Closed
redchair123 opened this issue Jun 24, 2013 · 4 comments
Closed

Handling option --parse #154

redchair123 opened this issue Jun 24, 2013 · 4 comments

Comments

@redchair123
Copy link

Is it possible to process the --parse flag?

@jamlfy
Copy link

jamlfy commented Sep 16, 2013

Parse for what? Because if we make commands friendly, touch know that?

@thethomaseffect
Copy link
Collaborator

Closing since OP has had a year to explain what they actual mean

@redchair123
Copy link
Author

@thethomaseffect @alejonext sorry I didn't notice the request (plus it came from September 15, not July 20, so it technically wasn't a year)

What I meant was that how do you configure commander to handle the flag --parse? For example:

var program = require('commander');
program.option('-p, --parse', 'parse');
program.parse(process.argv);
/* how do i get the value here? */

@thethomaseffect
Copy link
Collaborator

There's a couple of issues open related to options sharing the same namespace as commander's internals. We're waiting on getting a pull request updated before merging, please see #35

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

No branches or pull requests

3 participants