Devon Bagley
Devon Bagley
The only problem with this idea, is that it will make validation and other rules like `needs` a nightmare to deal with. Idk
It would be up to the user to manage error handling, at that point. Are you talking about only on new options, or when modifying an existing option? I rather...
Right. I would want some input from @nategood on the subject. Either there needs to be a sane way to invalidate the currently parsed options and re-parse (automatically) or parsing...
You must run the ```parse``` function to parse the args before you can get an options value. It happens that the array access function automatically runs the parse function. Parsing...
ConsoleKit also supports this syntax. It is fairly common in specific categories of console applications, but it is much more common to see this syntax being used in my experience...
Can this not be done using `map` or `cast` and `must`?
See #93, where if using `reduce` map is called on the values before being passed to reduce, and before any validation, and should fix the issue you were having with...
Probably, but Nate still has not made me a maintainer, so I don't manage tags, so I just keep track in my head.
At the moment our parser can not handle `-` without a short option following it. The majority of bash commands handle stdin input without the need for the dash at...
@OnkelTem Initializing `Command($tokens)` with a modified token list can be useful! That is usually how I do my sub-commands.