The `:collect` feature eats all remaining arguments

[Ramblurr]

Problem

I'd like to use babashka.cli to parse a cli string where an option can be passed multiple times and likewise also having multiple positional arguments.

Example

(cli/parse-args ["--foo" "a,b" "--foo" "c" "arg1" "arg2"]
                   {:coerce     {:foo         []
                                 :positionals []}
                    :args->opts (repeat :positionals)
                    :collect    {:foo (fn [coll arg-value]
                                        (into (or coll [])
                                              (str/split arg-value #",")))}})
;; => {:opts {:foo ["a" "b" "c" "arg1" "arg2"]}}

But I would expect

{:opts {:foo ["a" "b" "c"] :positionals ["arg1" "arg2"]}}

It seems that the :collect feature is eating all of the remaining arguments:

(cli/parse-args ["--foo" "a" "arg1" "arg2"] ...)
;; => {:opts {:foo ["a" "arg1" "arg2"]}}

[borkdude]

It's a feature since the beginning of babashka.cli that you can pass multiple values without repeating the option name, so:

--foo bar baz

instead of

--foo bar --foo baz

but I can understand that you would like to sometimes disable this. We can make disabling this behavior an option. Does that sound ok?

[Ramblurr]

It's a feature since the beginning of babashka.cli that you can pass multiple values without repeating the option name,

Ah, I understand. This sort of greedy behavior cli option is new to me. I can see how that would be useful behavior in some situations.

but I can understand that you would like to sometimes disable this. We can make disabling this behavior an option. Does that sound ok?

That would work for me! ❤️ But no pressure to implement it if you don't think it belongs in babashka.cli

[borkdude]

I actually do think it belongs in babashka.cli. Babashka.cli is a bit flexible at times but sometimes you just want a more ridig CLI.