Remko Popma
Remko Popma
> > That would allow you to define that positional parameter like this: > > `@Parameters(defaultValues = {}) // empty collection as default values` > > `List argDataPaths` > >...
If we do #877 then it makes sense to do this as well. What I haven’t fully thought through is the edge cases. Basically, what if there are multiple default...
I considered doing this for 4.7, but having second thoughts (and I may give up on this altogether). The problem is, that while this will be a backwards compatible change...
One idea is to add new API for multi-value defaults and leave the existing API as is for single-value defaults. Something like this: ```java Option(defaultValues = {"1", "2"}, fallbackValues =...
Related: https://github.com/remkop/picocli/issues/1743
Interesting idea. Fleshing out the spec in some more detail: * if any description, or a header/footer text contains a variable with the `${OPTION:` prefix, then * take the portion...
How do you invoke the program when you get that output?
Oh I see: If you make positional parameters required, they are required, whether a subcommand is specified or not. If you want positional parameters (or options for that matter) to...
> So the only way to fully separate those commands is to make them both sub-commands? Separate subcommands is one way, yes. The other way is to make them optional...
Hi @ashr123, have you been able to find a solution? Can this ticket be closed?