expose prefix in dispatch error no-match and input-exhausted cases

[Sohalt]

It would be helpful to have the cmds

cli/src/babashka/cli.cljc

Line 638 in 05868bf

:dispatch cmds

also exposed in the error data for the :no-match and :input-exhausted cases, because it's helpful to know how far dispatch traversed the command tree until it encountered the error to give better error messages.

Specifically, if I have

(def cmd-table
  [{:cmds ["foo" "bar"] :fn identity}
   {:cmds ["foo" "baz"] :fn identity}])
(dispatch cmd-table ["foo" "quux"] {:error-fn identity})
;; => {:type :org.babashka/cli, :wrong-input "quux", :all-commands ("bar" "baz"), :cause :no-match, :opts {}}

if I had the prefix "foo", I could genenrate an error message that lists all valid commands with prefix "foo" (i.e. "foo bar" "foo baz").

[borkdude]

Feel free to submit a PR, I prefer this to be called :cmds since that's what it's also called in the dispatch table?

[Sohalt]

It's called :cmds in the dispatch table, but is (and was) called :dispatch in the args to the fn called by dispatch. I don't have strong opinions though.

[borkdude]

Nowhere in a public API is the name :dispatch exposed right? (I mean on master, not in a previous WIP PR)

[Sohalt]

It is (and was) exposed on master as part of the dispatch fn, first introduced here 72edb28#diff-17c5192974650f8980e4dbdaa029b04d0ee52e3f3d77afc46a1944d79448aa0bR214

[Sohalt]

Wait, looks c870e24 removed it again.
But 712fee8#diff-17c5192974650f8980e4dbdaa029b04d0ee52e3f3d77afc46a1944d79448aa0bR634 reintroduced it.
The docs listed it the entire time

cli/API.md

Line 77 in 05868bf

* `:dispatch` - the matching commands

, which is what I was looking at when implementing the dispatch-tree changes.

[borkdude]

ok, let's keep dispatch then, didn't realize we already exposed it