(add-post-event-callback f)
(add-post-event-callback id f)
Registers a function f
to be called after each event is processed
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 processed `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 mranderson047.re-frame.v0v10v2.re-frame and returns a function which, when later called, will restore mranderson047.re-frame.v0v10v2.re-frame to that checkpointed state.
Checkpoint includes app-db, all registered handlers and all subscriptions.
Checkpoints the state of mranderson047.re-frame.v0v10v2.re-frame and returns a function which, when later called, will restore mranderson047.re-frame.v0v10v2.re-frame to that checkpointed state. Checkpoint includes app-db, all registered handlers and all subscriptions.
(reg-event-ctx id handler)
(reg-event-ctx id interceptors handler)
Register the given event handler
(function) for the given id
. Optionally, provide
an interceptors
chain.
id
is typically a namespaced keyword (but can be anything)
handler
is a function: (context-map event-vector) -> context-map
This form of registration is almost never used.
Register the given event `handler` (function) for the given `id`. Optionally, provide an `interceptors` chain. `id` is typically a namespaced keyword (but can be anything) `handler` is a function: (context-map event-vector) -> context-map This form of registration is almost never used.
(reg-event-db id handler)
(reg-event-db id interceptors handler)
Register the given event handler
(function) for the given id
. Optionally, provide
an interceptors
chain.
id
is typically a namespaced keyword (but can be anything)
handler
is a function: (db event) -> db
interceptors
is a collection of interceptors. Will be flattened and nils removed.
handler
is wrapped in its own interceptor and added to the end of the interceptor
chain, so that, in the end, only a chain is registered.
Special effects and coeffects interceptors are added to the front of this
chain.
Register the given event `handler` (function) for the given `id`. Optionally, provide an `interceptors` chain. `id` is typically a namespaced keyword (but can be anything) `handler` is a function: (db event) -> db `interceptors` is a collection of interceptors. Will be flattened and nils removed. `handler` is wrapped in its own interceptor and added to the end of the interceptor chain, so that, in the end, only a chain is registered. Special effects and coeffects interceptors are added to the front of this chain.
(reg-event-fx id handler)
(reg-event-fx id interceptors handler)
Register the given event handler
(function) for the given id
. Optionally, provide
an interceptors
chain.
id
is typically a namespaced keyword (but can be anything)
handler
is a function: (coeffects-map event-vector) -> effects-map
interceptors
is a collection of interceptors. Will be flattened and nils removed.
handler
is wrapped in its own interceptor and added to the end of the interceptor
chain, so that, in the end, only a chain is registered.
Special effects and coeffects interceptors are added to the front of the
interceptor chain. These interceptors inject the value of app-db into coeffects,
and, later, action effects.
Register the given event `handler` (function) for the given `id`. Optionally, provide an `interceptors` chain. `id` is typically a namespaced keyword (but can be anything) `handler` is a function: (coeffects-map event-vector) -> effects-map `interceptors` is a collection of interceptors. Will be flattened and nils removed. `handler` is wrapped in its own interceptor and added to the end of the interceptor chain, so that, in the end, only a chain is registered. Special effects and coeffects interceptors are added to the front of the interceptor chain. These interceptors inject the value of app-db into coeffects, and, later, action effects.
(reg-sub-raw query-id handler-fn)
This is a low level, advanced function. You should probably be using reg-sub instead. Docs in https://github.com/Day8/re-frame/blob/master/docs/SubscriptionFlow.md
This is a low level, advanced function. You should probably be using reg-sub instead. Docs in https://github.com/Day8/re-frame/blob/master/docs/SubscriptionFlow.md
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close