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

Typos

Browse Source
This commit is contained in:
Mike Thompson 2016-12-19 10:53:04 +11:00
parent 45a7be2552
commit 28df881056
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/SubscriptionsCleanup.md
View File

@ -15,7 +15,7 @@ structure, ready for use in hiccup generation.
### Just Look
Here be the horror:
Here be the horrors:
```clj
(defn clock
[]
@ -88,7 +88,7 @@ Then, we can re-write like this:
{:style {:color (listen [:time-color])}}
(listen [:time-str])])
```
At the cost of your own function, `listen`, the code is now slightly less noisy
At the cost of writing your own function, `listen`, the code is now less noisy
AND there's less chance of us forgetting an `@` (which can lead to odd problems).
### Say It Again
@ -128,25 +128,24 @@ Although to make that testing easier you may do this:
(reg-sub
:sorted-items
(fn [_ _] (subscribe [:items]))
item-sorter
item-sorter)
```
Now it is easy to test `item-sorter` independently (assuming it was a bit more complicated).
### And There's Another Benefit
re-frame de-duplicates signal graph nodes.
If, for example, two views wanted to `(subscribe [:sorted-items])` only the one node
(in the signal) graph would be created. Only one node would be doing that
(in the signal graph) would be created. Only one node would be doing that
potentially expensive sorting operation (when items changed) and values from
it would be flowing through to both views.
That sort of efficiency can't happen if this views themselves are doing the `sort`.
### de-duplication
### de-duplication
As I described above, two, or more, concurrent subscriptions for the same query will source
reactive updates from the one executing handler - from the one node in the signal graph.
@ -156,12 +155,9 @@ are the same if their query vectors test `=` to each other.
So, these two subscriptions are *not* "the same": `[:some-event 42]` `[:some-event "blah"]`. Even
though they involve the same event id, `:some-event`, the query vectors do not test `=`.
though they involve the same event id, `:some-event`, the query vectors do not test `=`.
This feature shakes out nicely because re-frame has a data oriented design.
***
Previous: [Infographic](SubscriptionInfographic.md)