Updated docs to be hosted on cljdoc.org.
explicit-deps and namespace-deps extension's start and stop functions now support 0-arity, just like the standard start/stop functions.log-fn, which is called on state changes.parallel and up-to.defstate macro now disallows defining a var that already exists and is not a defstate.defstate, and :bindings option to start. See README for details.:on-reload option for defstate.:on-cascade option for defstate.on-reload function now defaults to nil, and only overrides the states' :on-reload when set to a non-nil value.dot function, for generating a Graphviz graph of all the states.:up-to an already stopped state now will stop its started dependencies. Same for starting up to an already started state.:up-to an already started or stopped state will now not start or stop that state again.:parallel option to start and stop options. Value is number of threads to use, to start/stop independent states in parallel.:dependencies meta data in a state var, in order to influence the deduced state dependency graph.status function to main API.:up-to now uses the internal dependency graph to only start (or stop) the dependencies (or dependents) of the given var.:up-to behaviour, the "cascading stop" on a state redefinition has also improved.on-reload function to the API, replacing the :on-reload state option.:cascade mode for on-reload.:on-reload state option. It is replaced by the on-reload function.defstate mentioning removed :stop-on-reload? key.on-reload set to :lifecycle.:on-reload option. Defaults to :stop, but can be set to only redefine the :lifecycle expressions.:stop-on-reload? option. It has been replaced with the :on-reload option.alter-meta!).Can you improve this documentation?Edit on GitHub
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 |