Every effect step can return. The executor performs these and nothing else, so an executor
that covers a different set has drifted from the vocabulary rather than merely lagged it.
Every effect `step` can return. The executor performs these and nothing else, so an executor that covers a different set has drifted from the vocabulary rather than merely lagged it.
(installable? r response)True when response answers the in-flight read request, matched by request id alone.
True when `response` answers the in-flight read request, matched by request id alone.
(project resource)The fields a consumer may depend on, everything else is internal resource bookkeeping. The accepted envelope loses its :request/id on the way out. That id names the read-write-data that fetched the value, not the value, so two identical refetches project equal views and a consumer comparing them does not repaint.
The fields a consumer may depend on, everything else is internal resource bookkeeping. The accepted envelope loses its :request/id on the way out. That id names the read-write-data that fetched the value, not the value, so two identical refetches project equal views and a consumer comparing them does not repaint.
(step resource event)Takes a resource and event and returns (a possibly updated) resource and the effects that need to be called. Each step gets a unique resource/id
Takes a resource and event and returns (a possibly updated) resource and the effects that need to be called. Each step gets a unique resource/id
(write-request resource write-id {:keys [op id record]} query)The :write effect value for a write payload, or nil when none can be built. Reads the endpoint and the request config off the resource
The :write effect value for a write payload, or nil when none can be built. Reads the endpoint and the request config off the resource
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 |