Add support for Path conversion

[rkrisztian]

For conversion of parameters to Path, currently I have to add a custom converter class like this:

import java.nio.file.Path;
import java.nio.file.Paths;

import com.github.rvesse.airline.types.ConvertResult;
import com.github.rvesse.airline.types.DefaultTypeConverter;

public class MyTypeConverter extends DefaultTypeConverter {

    @Override
    public Object convert(String name, Class<?> type, String value) {
        checkArguments(name, type, value);

        ConvertResult result = tryConvertFromPath(type, value);
        if (result.wasSuccessfull()) {
            return result.getConvertedValue();
        }

        return super.convert(name, type, value);
    }

    private ConvertResult tryConvertFromPath(Class<?> type, String value) {
        if (type == Path.class) {
            try {
                return new ConvertResult(Paths.get(value));
            } catch (Throwable ex) {
                // Ignore
            }
        }
        return ConvertResult.FAILURE;
    }
}

It would be nice if this could be supported by default, as File is already supported.

Note: not urgent, for now I can just add this to my code:

CliBuilder<Runnable> builder = Cli.<Runnable>builder("my-cli")
        /* (...) */;
builder.withParser().withTypeConverter(new MyTypeConverter());
Cli<Runnable> parser = builder.build();

Note: I am probably not on the latest version yet, but if this inconveniently fluent-style-breaker withParser method has not been improved yet, please also consider making it more fluent too.

[rkrisztian]

BTW, wasSuccessful is the grammatically correct spelling, but I do not intend to annoy you. :)

[rvesse]

Thanks for the well described issue, just got back from vacation and catching up with everything.

To summarise the ask(s):

• [x] Path supported by default type converters
• [x] Correct spelling of wasSuccessfull() (I know my spelling is often questionable and a weird mix of British/American english)
• [x] Fix fluent breaking of withParser()

The first two are obvious to me but not so sure on the 3rd point. I guess you are referring to the point that once you have dropped into the parser builder you can't get back out to the parent builder. This is definitely possible in other parts of the Fluent API but not here so can certainly be improved in the future.

[rvesse]

This is fixed for the forthcoming 2.9.0 release, you can test out the fixes now by using 2.9.0-SNAPSHOT which is available from the Sonatype OSS repository per https://central.sonatype.org/publish/publish-guide/#accessing-repositories

Changes made to address this issue:

• Path conversion added to DefaultTypeConverter so supported by default
• When calling withParser() on a CliBuilder you will now be able to call parent() on the resulting ParserBuilder to return control to the parent CliBuilder
• ConvertResult now has a correctly spelled wasSuccessful() method with the old method deprecated