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

Command.opts() values are always undefined #626

Closed
carragom opened this issue Apr 30, 2017 · 2 comments
Closed

Command.opts() values are always undefined #626

carragom opened this issue Apr 30, 2017 · 2 comments

Comments

@carragom
Copy link

Hi there,

Got an issue with the opts() method. According to the docs it should return an Object with option names as keys. But the values always seem to be undefined. From what I can see, these values get loaded here but I don't really see how this[key] could ever return anything other than undefined. Am I missing something here?

@carragom
Copy link
Author

carragom commented May 1, 2017

Further checking, this seems to be related to default value assignment. These values get set here which according to the comment explicitly set boolean flags only when negated by --no-*. I guess the question then is, how to set a default false value for a boolean flag that is not negated with --no-*.

@shadowspawn
Copy link
Collaborator

I have this noted as an example of issues with how "boolean" options are handled.

This issue has not had any activity in over six months. It isn't likely to get acted on due to this report.

Feel free to open a new issue if it comes up again, with new information and renewed interest.

Thank you for your contributions.

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

2 participants