What a generated project's REPL helpers show: which modules are running, and the command palette that project actually has.
Pure. The shell namespace of the same name reads the running system, asks Jetty for its port, and prints.
What a generated project's REPL helpers show: which modules are running, and the command palette that project actually has. Pure. The shell namespace of the same name reads the running system, asks Jetty for its port, and prints.
What a generated project has.
Deliberately not this monorepo's guidance/command-groups: that one lists
(lint), (check-all), (scaffold!) and the ai/* helpers, none of which exist
in a generated project's dev/user.clj. A palette that names commands the
project does not have is the defect BOU-319 fixes, one layer down.
What a generated project has. Deliberately not this monorepo's `guidance/command-groups`: that one lists (lint), (check-all), (scaffold!) and the ai/* helpers, none of which exist in a generated project's dev/user.clj. A palette that names commands the project does not have is the defect BOU-319 fixes, one layer down.
(commands-text)The command palette of a generated project, as a string.
The command palette of a generated project, as a string.
(module-names system-or-config)Names of the application modules present in system-or-config, sorted.
Takes the keys, not a blocklist of known plumbing: a generated project wires
twenty Integrant keys and one of them is the module the user scaffolded. The
first version of this listed all twenty minus a handful, so (status) on a
fresh project reported twelve "modules", eleven of them the user module in
pieces (BOU-319).
Names of the application modules present in `system-or-config`, sorted. Takes the keys, not a blocklist of known plumbing: a generated project wires twenty Integrant keys and one of them is the module the user scaffolded. The first version of this listed all twenty minus a handful, so `(status)` on a fresh project reported twelve "modules", eleven of them the user module in pieces (BOU-319).
(status-text {:keys [system base-url]})The startup dashboard, or nil when nothing is running.
The admin URL comes off the running system, not the config: ig-config
never emits a :wagoe/admin key — the admin module arrives as
:wagoe/admin-service and :wagoe/admin-routes — so reading a base path
from the config yields nothing, and a guessed URL that 404s is worse than
none. :wagoe/admin-routes carries the :web-prefix the router actually
mounted, which is the question answered without guessing. Absent when the
admin module is not running, and then the line is not printed (BOU-394).
The startup dashboard, or nil when nothing is running. The admin URL comes off the running system, not the config: `ig-config` never emits a `:wagoe/admin` key — the admin module arrives as `:wagoe/admin-service` and `:wagoe/admin-routes` — so reading a base path from the config yields nothing, and a guessed URL that 404s is worse than none. `:wagoe/admin-routes` carries the `:web-prefix` the router actually mounted, which is the question answered without guessing. Absent when the admin module is not running, and then the line is not printed (BOU-394).
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |