Open pacak opened 1 year ago
- document that adjacent block must start with a flag?
Is this related to the bugs experienced with a subcommand with overlapping flags (short names)?: https://github.com/pacak/bpaf/issues/325
Is this related to the bugs experienced with a subcommand with overlapping flags (short names)?:
I don't think so. Current logic to restrict scope to adjacent values is something like this:
This works if first item in the parser wants to consume let's say -p
, but it doesn't work if it wants let's say -x 3
- -x
part will be available, 3
- won't be and argument parser checks that both name and value are present. It works this way because some unrelated reasons.
Without
p
this fails since adjacent detects left most item with magic...