donut.system — party.donut/system 0.0.167

alias-component clj/s

(alias-component component-id)

creates a component that just provides an instance defined elsewhere in the system

assoc-many clj/s

(assoc-many m assocs)

(assoc-many m prefix assocs)

(assoc-many {} {[:foo :bar] :bux}) => {:foo {:bar :bux}

Component clj/s

component-id clj/s

(component-id ref)

component? clj/s

ComponentGroup clj/s

Components are grouped. This theoretically helps if publishing a component library. It also helps when creating multiple instances of the same collection of components because components are allowed to have local refs. See TODO for more details.

ComponentGroupName clj/s

ComponentGroups clj/s

ComponentId clj/s

ComponentLike clj/s

Component-like data shows up in ::defs, ::resolved-defs, and ::instances. None of these are the component per se, but they are the way the component manifests in that context.

ComponentName clj/s

ComponentSelection clj/s

config-collect-group-path clj/s

specter path that retains a component's group name

default-signals clj/s

which graph to follow to apply signal

DonutRef clj/s

DonutSystem clj/s

Graph clj/s

Graphs are used to specify component dependency order and signal application order.

group-ref-exception clj/s

(group-ref-exception _system
                     referencing-component-id
                     referenced-component-group-name)

group-ref? clj/s

(group-ref? ref)

init-system clj/s

(init-system maybe-system signal-name component-keys)

local-ref clj/s

(local-ref k)

LocalRef clj/s

named-system clj/s multimethod

A way to name different system, e.g. :test, :dev, :prod, etc.

OrderGraphs clj/s

Topsorted and reverse-topsorted graphs are generated once when a system is initialized and assoc'c into the system. These graphs are used when applying signals.

Ref clj/s

ref clj/s

(ref k)

ref-exception clj/s

(ref-exception _system referencing-component-id referenced-component-id)

ref-key clj/s

ref-type clj/s

ref? clj/s

RefKey clj/s

required-component clj/s

Communicates that a component needs to be provided.

resolved clj/s

(resolved {:keys [:donut.system/component-id :donut.system/resolved-defs]})

resume clj/s

(resume system)

signal clj/s

(signal system signal-name & [component-keys])

SignalConfig clj/s

The set of signals your system can respond to is configurable. To apply a signal, the system needs to know in what order components should be traversed.

start clj/s

(start config-name)

(start config-name custom-config)

(start config-name custom-config component-ids)

stop clj/s

(stop system)

stop-failed-system clj/s

(stop-failed-system)

Will attempt to stop a system that threw an exception when starting

strk clj/s

(strk & xs)

Like str but with keywords

subsystem-component clj/s

(subsystem-component subsystem & [imports])

Decorates a subsystem so that it can respond to signals when embedded in a parent component.

suspend clj/s

(suspend system)

system clj/s

(system sconf)

(system sconf component-def-overrides)

specify a system or a system named registered with config, and optionally provide overrides

system? clj/s

validate-instance-with-malli clj/s

(validate-instance-with-malli {:keys [:donut.system/instance ->validation
                                      :donut.system/system]})

helper function for validating component instances with malli if a schema is present.