Which library owns each framework module, and which modules a config
switches on. Pure data, here rather than in wagoe-platform so migrations
can skip switched-off modules without depending on it (BOU-934).
wagoe.platform.shell.modules re-exports all three.
Which library owns each framework module, and which modules a config switches on. Pure data, here rather than in wagoe-platform so migrations can skip switched-off modules without depending on it (BOU-934). `wagoe.platform.shell.modules` re-exports all three.
Modules every application gets whether or not its config mentions them.
Both fall back to a working default — the logging email sender, an English-only catalogue — and the HTTP handler takes a ref to i18n's middleware unconditionally, so leaving them out is not an option an application has. They are modules rather than core components because the wiring lives in their own library, and platform depends on neither.
Modules every application gets whether or not its config mentions them. Both fall back to a working default — the logging email sender, an English-only catalogue — and the HTTP handler takes a ref to i18n's middleware unconditionally, so leaving them out is not an option an application has. They are modules rather than core components because the wiring lives in their own library, and platform depends on neither.
(enabled-libraries active)(enabled-libraries active extra)The libraries whose framework modules active switches on, or extra
enables in code, as names ("geo", "workflow"). Always-on ones included.
The libraries whose framework modules `active` switches on, or `extra`
enables in code, as names ("geo", "workflow"). Always-on ones included.:active key -> the library that owns it.
The wiring namespace is derived (wagoe.<lib>.shell.module-wiring) rather
than listed, so a new module is one entry. Four keys predate the convention
and cannot be derived from their own name; they are spelled out.
These are keyword-to-string pairs, not namespace loads: neither platform nor platform-sql depends on these libraries.
`:active` key -> the library that owns it. The wiring namespace is derived (`wagoe.<lib>.shell.module-wiring`) rather than listed, so a new module is one entry. Four keys predate the convention and cannot be derived from their own name; they are spelled out. These are keyword-to-string pairs, not namespace loads: neither platform nor platform-sql depends on these libraries.
(module-entries active extra)The framework modules active switches on, as [key lib] pairs.
extra names modules an application enables in code rather than in config;
projects generated before BOU-667 enable user this way.
The framework modules `active` switches on, as [key lib] pairs. `extra` names modules an application enables in code rather than in config; projects generated before BOU-667 enable user this way.
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 |