(add-post-event-callback f)
(add-post-event-callback id f)
Registers a function f
to be called after each event is procecessed
f
will be called with two arguments:
event
: a vector. The event just processed.queue
: a PersistentQueue, possibly empty, of events yet to be processed.This is useful in advanced cases like:
'id' is typically a keyword. Supplied at "add time" so it can subsequently be used at "remove time" to get rid of the right callback.
Registers a function `f` to be called after each event is procecessed `f` will be called with two arguments: - `event`: a vector. The event just processed. - `queue`: a PersistentQueue, possibly empty, of events yet to be processed. This is useful in advanced cases like: - you are implementing a complex bootstrap pipeline - you want to create your own handling infrastructure, with perhaps multiple handlers for the one event, etc. Hook in here. - libraries providing 'isomorphic javascript' rendering on Nodejs or Nashorn. 'id' is typically a keyword. Supplied at "add time" so it can subsequently be used at "remove time" to get rid of the right callback.
(make-restore-fn)
Checkpoints the state of re-frame and returns a function which, when later called, will restore re-frame to that checkpointed state.
Checkpoint includes app-db, all registered handlers and all subscriptions.
Checkpoints the state of re-frame and returns a function which, when later called, will restore re-frame to that checkpointed state. Checkpoint includes app-db, all registered handlers and all subscriptions.
(reg-event-db id db-handler)
(reg-event-db id interceptors db-handler)
Register the given id
, typically a keyword, with the combination of
db-handler
and an interceptor chain.
db-handler
is a function: (db event) -> db
interceptors
is a collection of interceptors, possibly nested (needs flattenting).
db-handler
is wrapped in an interceptor and added to the end of the chain, so in the end
there is only a chain.
The necessary effects and coeffects handler are added to the front of the
interceptor chain. These interceptors ensure that app-db is available and updated.
Register the given `id`, typically a keyword, with the combination of `db-handler` and an interceptor chain. `db-handler` is a function: (db event) -> db `interceptors` is a collection of interceptors, possibly nested (needs flattenting). `db-handler` is wrapped in an interceptor and added to the end of the chain, so in the end there is only a chain. The necessary effects and coeffects handler are added to the front of the interceptor chain. These interceptors ensure that app-db is available and updated.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close