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

fix typos in re-frame interceptors;

Browse Source
This commit is contained in:
Matthew Jaoudi 2016-12-16 23:25:46 -08:00
parent 609299ca71
commit 3442726a54
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/Interceptors.md
View File

@ -296,7 +296,7 @@ Earlier, in the "Handlers Are Interceptors Too" section, I explained that `event
are wrapped in an Interceptor and placed on the end of an Interceptor chain. Remember the
whole `[std1 std2 in1 in2 h]` thing?
We're now look at the `h` bit. How does an event handler get wrapped to be an Interceptor.
We'll now look at the `h` bit. How does an event handler get wrapped to be an Interceptor?
Reminder - there's two kinds of handler:
- the `-db` variety registered by `reg-event-db`
@ -367,9 +367,9 @@ In the next Tutorial, we'll look at (side) Effects in more depth. Later again,
## Appendix
### The Builtin Interceptors
### The Built-in Interceptors
re-frame comes with some builtin Interceptors:
re-frame comes with some built-in Interceptors:
- __debug__: log each event as it is processed. Shows incremental [`clojure.data/diff`](https://clojuredocs.org/clojure.data/diff) reports.
- __trim-v__: a convenience. More readable handlers.