Please test using this command, it will fail

"script.php subcommand --data=thedata --limit=30 --batch=10 --index=theindex argument1 argument2"

The parser only parse data, limit, and batch, and ignoring the rest (index, argument1, argument2 is not parsed

If number begins with -, it is treated as an option. Current workaround: use something like: -o " -1" because -o "-1" will not work.

If I have multiple short options in my command and I pass them like -mv I'll just get the first one as a passed option. Using -l -v works.

Also, using -vm4 does the same, while it should give me the v option as boolean, and m as 4. Doing -m4v gives me m without the value as well, and nothing else.

The library doesn't appear to support arguments such as

command --option="foo bar baz"

This becomes

['"foo', 'bar', 'baz"']

...rather than

['foo bar baz']

Is this something that you are planning to/want to implement?

The customer validator you could set on an Option wasn't triggered during option parsing, this required you to call $option->validate($option->value)) manually, which is cumbersome and counterintuitive.

Sidenote: I noticed PHPUnit wasn't included as a dependency in composer.json, any reason for that? It's hard to run the unit tests that way ;-)

Read-me mentions ability to mix with normal arguments here:

https://github.com/c9s/GetOptionKit#supported-option-formats

However I can't find a way to implement this:

myapp [ -s <system_id> ] file.txt

I was expecting than parser would remove all arguments from parameter leaving normal arguments inside, but it's not happening.

Hi. There was an issue with checking required value:

1. Write in your php script $GetOptionKit->add('t|test:', 'required value');
2. Run it as follows: ./script --test
3. There is no exception on parsing args.
4. There, I fixed it!)

P.S. If I've misunderstood concept of 'option requires a value.', I'm sorry.

Hi! I really like the library you've created for parsing CLI arguments, but I'm running into an issue. I'm probably just using it wrong, but maybe you can clarify.

I'm trying to add a validator to an option, to make sure the option is an existing and readable file. I was assuming it would work something like this:

$specs
    ->add('c|candidates:', 'Candidates file')
    ->validator(function($option) {
        return file_exists($option) && is_readable($option);
    });

But it doesn't. The validate function is used nowhere in the entire library (according to PHPStorm), so I figured I needed to trigger it myself, but doing this seems unnecessarily complicated:

$option->validate($option->value)

If it should actually automatically validate, I'll be more than happy to create a PR and change it, but I wanted to check first if this is not just the intended behaviour.

Coming from a getopt I expect that calling this:

shell> php example.php -fvalue -h

and using parse() would give me something like:

array(2) {
  ["f"]=>
  string(5) "value"
  ["h"]=>
  bool(false)
}

However parse() responds with spec definitions strings:

$result = $parser->parse($argv);
echo 's is '.$result['f']."\n";

While it's handy for a demo, it's unclear how to actually get the value. My final working snippet looks like this:

$specs = new \GetOptionKit\OptionCollection;
$specs->add('f:', 'value of f' );
$parser = new \GetOptionKit\OptionParser($specs);
$result = $parser->parse($argv)->toArray();
echo 'f is '.$result['f']."\n";

but it took some poking in the code to arrive at this.

Documentation is inconsistent about 'number' vs 'Number': https://github.com/c9s/GetOptionKit/search?utf8=✓&q=isa

$specs->add('s|system', 'Select system by ID' )->isa('Number');

Orange-Dream:tools rw$ php importer.php -s 123 -s, --system= Select system by ID

PHP Fatal error: Uncaught GetOptionKit\InvalidOptionValue: Invalid value for -s, --system. Requires a type Number. in /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/Option.php:264 Stack trace: #0 /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/Option.php(297): GetOptionKit\Option->_preprocessValue(true) #1 /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/OptionParser.php(48): GetOptionKit\Option->setValue(true) #2 /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/OptionParser.php(172): GetOptionKit\OptionParser->consumeOptionToken(Object(GetOptionKit\Option), Object(GetOptionKit\Argument), Object(GetOptionKit\Argument)) #3 /Users/rw/Sites/smbo/old/tools/importer.php(32): GetOptionKit\OptionParser->parse(Array) #4 {main}

thrown in /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/Option.php on line 264

Fatal error: Uncaught GetOptionKit\InvalidOptionValue: Invalid value for -s, --system. Requires a type Number. in /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/Option.php on line 264

GetOptionKit\InvalidOptionValue: Invalid value for -s, --system. Requires a type Number. in /Users/rw/Sites/smbo/old/vendor/corneltek/getoptionkit/src/Option.php on line 264

When defining a "single" option (e.g. foo:=string), that option's argument will be consumed and not returned with the remaining arguments from getArguments(), but a "multiple" option (e.g. bar+=string) does not consume its argument and leaves it with the rest of the arguments returned by getArguments().

$specs = new \GetOptionKit\OptionCollection();
$specs->add('test1+=string', 'Test 1');
$specs->add('test2:=string', 'Test 2');

$parser = new \GetOptionKit\OptionParser($specs);

$result = $parser->parse(explode(' ', '--test1 opt1 --test2 opt2 arg1 arg2'));

$result->getArguments(); // => ["opt1", "arg1", "arg2"]

Ideally, at least to the best of my knowledge, the arguments to a "multiple" option should be consumed and removed from the list returned by getArguments() so only ["arg1", "arg2"] would be returned in the above example.

Firstly, after skipping over dozen of alternatives, i was very happy to find this project - seems like what i was looking for!

Unfortunately, i could not find a way to install it with composer: composer require c9s/GetOptionKit

exits with the following error:

Package c9s/GetOptionKit is abandoned, you should avoid using it. Use corneltek/getoptionkit instead.

But trying to do that and typing

composer require corneltek/getoptionkit

results in the same message. Moreover, it seems like there is no "getoptionkit" repo under https://github.com/corneltek/

So, i'd like to know whether is this project considered as completely abandoned and so the suggestion would be to not use it in new projects? Or are there any plans to publish a replacement for it or a successor?

Hi. I just tried to update from 2.0.3 to 2.0.9 and noticed, that you removed a public method:

Call to undefined method GetOptionKit\OptionCollection::printOptions()

Could you please maintain a changelog for breaking changes like this?) I see, that new behavior is reflected in example.php, and i like the new OptionPrinter, but it would be nice to have a brief changelog, at least a one line at release comment)