Would not it be easier to leave CommandLine as is, change parameter to repeatable and split it in loadOptions()?

@dg Probably yes. The -o value:file/path syntax seems ok? So, drop CommandLine::ENUM (this is the only one place) and parse it manually. Or add CommandLine::NORMALIZER like:

CommandLine::NORMALIZER => function ($arg) {
    list($value, $path) = explode(':', $arg, 2);
    if (...) throw ...
};

I'll try how it will look like.

@dg What about such approach (last commit)?

I tried to find if there is any pattern how should these parameters look, but it seems that this is pole neorané … not standardized. Sometimes it is used this way:

vendor/bin/tester -o console -o tap -file output.tap -o junit -file output.xml -o log -file output.log

Which looks logical, but little bit weird. So syntax is fine for me.

In fact ENUM is used by Tester, try tester --colors x before and after.

In fact ENUM is used by Tester, try tester --colors x before and after.

Ups, I was rash. I have to find a way how to preserve console|tap|junit|log|none at one place and do not collide with ENUM implementation. Or replace ENUM implementation by something similarly easy.

Closing in favour of #329