a-frame.interceptor-chain.schema

Liking cljdoc? Tell your friends :D

All platforms.

Interceptor
interceptor-fn-keys
interceptor-fn-noop
InterceptorContext
InterceptorFnHistoryKey
InterceptorFnKey
InterceptorHistoryElem
InterceptorList
InterceptorSpec

Interceptor^clj/s

An Interceptor, all methods are optional but should be implemented as follows:

::intc/enter takes 1 or 2 args:
- context -> context
- context -> data -> context
::intc/leave – takes 1 or 2 args:
- context -> context
- context -> data -> context
::intc/error – takes two args
- context -> error -> context

All methods may return either promises or plain values.

An Interceptor, all methods are optional but should be implemented as
follows:

* `::intc/enter` takes 1 or 2 args:
   - context -> context
   - context -> data -> context

* `::intc/leave` – takes 1 or 2 args:
   - context -> context
   - context -> data -> context

* `::intc/error` – takes two args
   - context -> error -> context

All methods may return either promises or plain values.

source raw docstring

InterceptorSpec^clj/s

the interceptor chain is created with a list of InterceptorSpecs. each InterceptorSpec is either

simple keyword, referencing a registered interceptor which will cause ::intc/enter and ::intc/leave fns to be invoked with 1-arity, or
a map with mandatory ::intc/key. if there is data (either ::intc/enter-data or ::intc/leave-data) then ::intc/enter and ::intc/leave will be invoked with their 2-arity

providing data like this allows a pure-data (in the re-frame sense - roughly something which has no opaque objects and is serializable/deserializable) interceptor chain to be registered, which has numerous benefits

the interceptor chain is created with a list of InterceptorSpecs. each
InterceptorSpec is either
-  simple keyword, referencing a registered interceptor which will cause
   ::intc/enter and ::intc/leave fns to be invoked with 1-arity, or
- a map with mandatory `::intc/key`. if there is data
   (either `::intc/enter-data` or `::intc/leave-data`) then `::intc/enter` and `::intc/leave` will
   be invoked with their 2-arity

providing data like this allows a pure-data (in the re-frame sense - roughly
something which has no opaque objects and is serializable/deserializable)
interceptor chain to be registered, which has numerous benefits

source raw docstring