status-im/re-frame
2
0
Fork 0
mirror of https://github.com/status-im/re-frame.git synced 2025-02-24 07:48:14 +00:00
Code Issues Projects Releases Wiki Activity

Minimal typos

Browse Source
This commit is contained in:
Henrik Mohr 2016-09-07 15:16:57 +02:00 committed by GitHub
parent 1475a2ef1b
commit e2bd2ca83b
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/Interceptors.md
View File

@ -89,8 +89,7 @@ concept, right there.
### Show Me ### Show Me
At the time when you register an event handler, you can provide an At the time when you register an event handler, you can provide a chain of interceptors too.
chain of interceptors too.
Using a 3-arity registration function: Using a 3-arity registration function:
```clj ```clj
@ -108,7 +107,7 @@ Using a 3-arity registration function:
You might see that registration above as associating `:some-id` with two things: (1) a chain of 2 interceptors `[in1 in2]` You might see that registration above as associating `:some-id` with two things: (1) a chain of 2 interceptors `[in1 in2]`
and (2) a handler. and (2) a handler.
Except, the handler is turned into an interceptor too. (We'll see how shortly) Except, the handler is turned into an interceptor too (we'll see how shortly).
So `:some-id` is only associated with one thing: a 3-chain of interceptors, So `:some-id` is only associated with one thing: a 3-chain of interceptors,
with the handler wrapped in an interceptor, called say `h`, and put on the end of the other two: `[in1 in2 h]`. with the handler wrapped in an interceptor, called say `h`, and put on the end of the other two: `[in1 in2 h]`.
@ -136,8 +135,7 @@ Each interceptor has this form:
:after (fn [context] ...)} ;; `identity` would be a noop :after (fn [context] ...)} ;; `identity` would be a noop
``` ```
That's essentially a map of two functions. Now imagine a vector of these maps - that's an That's essentially a map of two functions. Now imagine a vector of these maps - that's an interceptor chain.
an interceptor chain.
Above we imagined an interceptor chain of `[std1 std2 in1 in2 h]`. Now we know that this is really Above we imagined an interceptor chain of `[std1 std2 in1 in2 h]`. Now we know that this is really
a vector of 5 maps: `[{...} {...} {...} {...} {...}]` where each of the 5 maps have a vector of 5 maps: `[{...} {...} {...} {...} {...}]` where each of the 5 maps have
@ -232,14 +230,14 @@ We'd have to write this handler:
(reg-event-db (reg-event-db
:delete-item :delete-item
(fn (fn
[db [_ key-to-delete]] ;; <---- Arrgggghhh underscore [db [_ key-to-delete]] ;; <---- Arrgggghhh underscore
(dissoc db key-to-delete))) (dissoc db key-to-delete)))
``` ```
Do you see it there? In the event destructuring!!! Almost mocking us with that Do you see it there? In the event destructuring!!! Almost mocking us with that
passive aggressive, understated thing it has going on!! Co-workers passive aggressive, understated thing it has going on!! Co-workers
have said I'm "being overly sensitive", perhaps even pixel-ist, but have said I'm "being overly sensitive", perhaps even pixel-ist, but
you can see it, right? Of course you can. you can see it, right? Of course you can.
What a relief it would be to not have it there, but how? We'll write an interceptor: `trim-event` What a relief it would be to not have it there, but how? We'll write an interceptor: `trim-event`
@ -298,7 +296,7 @@ I'll now show how to wrap the `-db` variety.
Reminder: here's what a `-db` handler looks like: Reminder: here's what a `-db` handler looks like:
```clj ```clj
(fn [db event] ;; takes two params (fn [db event] ;; takes two params
(assoc db :flag true)) ;; returns a new db (assoc db :flag true)) ;; returns a new db
``` ```
@ -341,7 +339,7 @@ __1.__ When you register an event handler, you can supply a collection of interc
``` ```
__2.__ When you are registering an event handler, you are associating an event id with a chain of interceptors including: __2.__ When you are registering an event handler, you are associating an event id with a chain of interceptors including:
- the ones your supply (optional) - the ones you supply (optional)
- an extra one on the end, which wraps the handler itself - an extra one on the end, which wraps the handler itself
- a couple at the beginning of the chain, put there by the `reg-event-db` or `reg-event-fx`. - a couple at the beginning of the chain, put there by the `reg-event-db` or `reg-event-fx`.