- ->interceptor
- add-post-event-callback
- add-state-defaults
- after
- assoc-coeffect
- assoc-effect
- clear-cofx
- clear-event
- clear-fx
- clear-sub
- clear-subscription-cache!
- console
- debug
- dispatch
- dispatch-sync
- empty-db?
- enqueue
- enrich
- get-coeffect
- get-effect
- inject-cofx
- make-restore-fn
- new-state
- new-state-wo-event-queue
- on-changes
- path
- purge-event-queue
- reg-cofx
- reg-event-ctx
- reg-event-db
- reg-event-fx
- reg-fx
- reg-sub
- reg-sub-raw
- remove-post-event-callback
- set-loggers!
- state?
- subscribe
- trim-v
re-frame-lib.core
add-post-event-callbackclj/s
(add-post-event-callback state f)(add-post-event-callback state 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:
- 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.
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.
add-state-defaultsclj/s
(add-state-defaults state)Adds to the re-frame state some builtin handlers, like coeffects, effects, etc.
Adds to the re-frame state some builtin handlers, like coeffects, effects, etc.
empty-db?clj/s
(empty-db? st)Checks if the app-db atom is empty. Useful for figwheel.
Checks if the app-db atom is empty. Useful for figwheel.
make-restore-fnclj/s
(make-restore-fn state)Checkpoints the state of re-frame and returns a function which, when later called with current-state, 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 with current-state, will restore re-frame to that checkpointed state. Checkpoint includes app-db, all registered handlers and all subscriptions.
new-stateclj/s
(new-state)Creates a new re-frame state. This is the one to use.
Once created, you can create subscriptions and events handlers using the ->
threading macro:
(defonce state (-> (new-state) subs/reg-some-subs events/reg-some-events)))
or you can reload the handlers (if (empty-db? state) (swap! astate #(-> % subs/reg-some-subs events/reg-some-events)))
Creates a new re-frame `state`. This is the one to use.
Once created, you can create subscriptions and events handlers using the ->
threading macro:
(defonce state
(-> (new-state)
subs/reg-some-subs
events/reg-some-events)))
or you can reload the handlers
(if (empty-db? state)
(swap! astate #(-> % subs/reg-some-subs events/reg-some-events))) purge-event-queueclj/s
(purge-event-queue state)Remove all events queued for processing
Remove all events queued for processing
reg-event-ctxclj/s
(reg-event-ctx state id handler)(reg-event-ctx state 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-dbclj/s
(reg-event-db state id handler)(reg-event-db state 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-fxclj/s
(reg-event-fx state id handler)(reg-event-fx state 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-rawclj/s
(reg-sub-raw state 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