status-im
/
re-frame
mirror of https://github.com/status-im/re-frame.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

README tweak

This commit is contained in:
Mike Thompson 2017-10-21 10:23:09 +11:00
parent fac8c8af91
commit 02c809621c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -84,7 +84,7 @@ So, it will come as no surprise, then, to know that re-frame has a
data oriented design. Events are data. Effects are data. DOM is data.
The functions which transform data are registered and looked up via
data. Interceptors (data) are preferred over middleware (higher
order functions). Etc.
order functions). Etc.
**Data - that's the way we roll.**
@ -94,7 +94,7 @@ order functions). Etc.
Architecturally, re-frame implements "a perpetual loop".
To build an app, you hang pure functions on certain parts of this loop,
and re-frame looks after the `conveyance of data`
and re-frame looks after the **conveyance of data**
around the loop, into and out of the transforming functions you
provide - hence a tag line of "Derived Values, Flowing".