New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No top level `:flags` config leads to sub-command population errors #5

Open

bnert opened this issue Dec 21, 2023 · 0 comments

Labels

bug

Collaborator

bnert commented Dec 21, 2023

Example:

(ns example.core
  (:require
    [packard.core :as commander]))

(def cmds
  {:usage "thing"
   :commands
   {:sub-cmd {:usage "thing sub-cmd [opts]"
              :flags {:verbose? ["v" "verbose" {:as :bool}]}}})

(defn -main [& args]
  (commander/exec cmds args))

When the above is invoked like $ clj -M -m example.core sub-cmd help, the output will not fill in flags.

However, if the above is modified to:

(ns example.core
  (:require
    [packard.core :as commander]))

(def cmds
  {:usage "thing"
   :flags {}
   :commands
   {:sub-cmd {:usage "thing sub-cmd [opts]"
              :flags {:verbose? ["v" "verbose" {:as :bool}]}}})

(defn -main [& args]
  (commander/exec cmds args))

It works as expected.

The text was updated successfully, but these errors were encountered:

bnert added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment