-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Default command does not parse flags #463
Comments
Ah, if you put the option before the command, it does work. E.g.
That's totally acceptable though possibly counter-intuitive. I'll leave this open for now in case you agree and want to make it work the other way around too, but feel free to close if not. |
Looks like a dupe of #461 I think? Nice workaround. |
Yeah, probably caused by the same "bug" (or feature). |
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. |
I have a feeling this may be an open issue somewhere, but I was unable to find it. I apologize if it is.
If you use a default command (e.g.
.command('*')
), options are not parsed for this command. So for example:The logged options object looks like it always does in a command except, if you pass
-c
or--count
, options.count is undefined.The text was updated successfully, but these errors were encountered: